5 reasons why JavaScript is eating the world

I’d argue about Electron being a good desktop argument here. Let me give a little bit of background: before the Chromium blog announced killing Chrome Apps (and given popularity of the browser), there was a really easy way to get a Chrome App up and running in few steps. This started filling niche gaps here-and-there, basically giving easy way to write one-off utilities to do interesting stuff (especially with hardware access, etc.).

Now that this is gone, the only workaround is to distribute a copy of Electron with your app (which basically means shipping a copy of Chromium for each app) or use The Preferred Way, which would building a “web app”. This might be fine for a regular web app (which could have been in web form for years now), but for something more “local” (e.g. dealing with hardware, local data, working offline …) one needs to wait for adoption of standards like WebUSB, WebBluetooth, or even write their own web server and native code to handle filesystem access, etc. .

The bottom line: JavaScript for desktop doesn’t currently give a user nor developer the best experience. It’s not a lost case yet, but in my opinion it just got from “almost readily available” state to something akin to Java’s “Install JVM in order to use this product” state.

Remember that last time you voluntarily installed a 100 MB support package just to launch that stupid 100 KB application? Me neither.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.