Echo JS 0.11.0

"Immediate-execution is a side-effect"

How can a well-defined core behavior be considered a "side effect"?
I might concede that merily passing a function to a constructor isn't usually expected to imply that such function is immediately called (it's also why the "deferred paradigm" is usually preferred), but that's how it is.

Anyway, synchronous code can always be made asynchronous, but not the other way around (unless you're counting await as a way). The main point of promises is their resolution/rejection always happening as the next micro-task, even if they're called synchronously.

If OP is asking here, maybe it's because they need an opinionated answer, don't you think?

Ha! I wasn't expecting that.
Entertainig, although borderline useless trivia.

Honestly, the title is terribly clickbaity and OP should feel bad. Especially because it looks like a well estabilished library with 3.8k stars that doesn't need it.

But that makes me wonder: is Socket.IO so slow that can actually hurt performance in a "normal" use case? And when does it hurt?

Haha thank you for the honesty!

You acn always mark a release as "pre-release" on GitHub.

Where does this figure "50%" come from?

I see that the title is to catch the readers rather than actually to state the end of native apps, if you admit that they "still have a few capabilities that mobile apps will not have for a potentially long time".

It's not that device manufacturers have never tried the "all-web-tech" road in the past - it's an effort as old as WebOS - but there are apps which are *explicitely* thought for devices, and aren't suit to live on the web in any form. Like a file explorer, for example.

Honestly I have no idea native apps are doomed, or even will be relegated in a small niche. In my opinion, it's way too soon to tell. We still don't know if PWAs will ever catch on, among developers *and* users. Safari doesn't even support service workers at the moment.

One thing, for sure, is that we should try to develop PWAs because they *do* look cool!

In short, it makes background images centered, non-repeating and covering.
If the browser supports CSS3, that doesn't need a jQuery plugin: all you'd need is a CSS class!
The only "useful" part is the fix for IE8- for background-size... which works as expected only if it's set to `cover`. If you want something else (because it's an option you can override), you're out of luck.
Definitely a badly designed plugin.

?? Where did versions 2.1.0-2.1.3 go?
Just never tagged?