Why is javascript so popular while applications written

>>59937363

Because they're lazy ports of web-based programs and thus need to spin up most of a browser to run.

>>59938951
JavaScript developer advocates keep insisting that the user would never notice the 3 orders of magnitude that the web by its very nature makes applications slower rather than using native API techniques.

The developers are more than ready to believe this because they don't want to change, to learn new languages and technologies or even worry about performance.

The one who has to pay in the end is the end user, not the developer. Not only will the resulting application be slow and unresponsive, it will also eat hundreds of megabytes of ram for simple tasks, not have the expected native look and feel and drain the FUCK out of the battery.

File: BiodronesAfterAndromeda.jpg (83KB, 600x920px) Image search: [Google]

83KB, 600x920px

>>59938951
>be poorfag BA or art student
>want to be creative and follow 'passions'
>but don't want to be a poorfag
>don't like math
>thinking makes brain hurt
>problem.jpeg
>learn about baby's first programming language: javascript
>no need to think about types
>no need to think about data structures
>no need to build and compile
>no need to debug 100+ errors before first run
>syntax fairly close to english
>itjustwerks.mkv
>it's the language of the web for crazy looking websites
>thanks netscape
>give 0 shits that HTML/CSS was a mistake that top minds are trying to fix about the internet
>give 0 shits about runtime
>itjustwerks.pinterest
>multiply by 1,000,000
>there's more artfags than script-fags
>by pure power of numbers strong arm industry to using JS
>industry starts using JS since more people know it than special snowflakes like Haskell
>HTML/CSS/JS now tied strongly to the web
>by pure power of numbers web industry now uses JS
>still be a lazy ass artfag who gives 0 shits about the industry
>would be nice if I can just copy someone elses JS code
>start sharing code bases
>give 0 shits libraries used to be designed by PhDs or experts in algorithms
>give 0 shits libraries take a lot of work and research to develop
>make some inefficient code, push it to npm
>other JS coders also give 0 shits about efficiency
>they start using inefficient modules in npm
>by pure power of numbers, JS churns out more modules and libraries by the minute other than more efficient languages
>everyone is now using everyone's inefficient code bases for faster coding
>JS is now so big and cluttered industry needs more JS people to fix JS people's shit
>now too many people in front-end space
>backend developers and desktop app developers are in demand
>would be great if we can use JS on these spaces
>node.js and electron were designed
>thanks google
>HTML/CSS can no longer be fixed

web history 201

>>59938951
The problem with atom in particular is coffeescript, not electron. If done well, an electron app can be usable (VS Code is an example, the cursor bug was just that, a bug) but you need to make good quality programs, same pit falls can affect programs written in C++, just not to such a degree

Javascript honestly isn't that slow. Updating the DOM has poor performance though.

>>59939877
>my opinions are facts
i hope you had a fun time writing that you fucking autist

>>59940013
So absurdly slow that currently, it is in most situations (that are sufficiently complex) it is more efficient to use a virtual DOM and diffing than to mutate yourself.
That means describing what you'd like your DOM to look like for a certain state and then having a diffing algorithm compute the least amount of changes that need to be made to make your current DOM look like that.

I fucking hate the web. Waiting for 10 seconds before the application becomes interactive is becoming normal because of BS like this. And without a node.js backend for universal rendering, that's how long it takes to even render the content for the first time.

>>59939945
>VS Code is an example, the cursor bug was just that, a bug
No it wasn't. It was the end result of basing a desktop application on the shitty web DOM.

>>59940013
This.

>>59939823
So much this.

>>59940015
>by pure power of numbers, JS churns out more modules and libraries by the minute other than more efficient languages
>everyone is now using everyone's inefficient code bases for faster coding
>JS is now so big and cluttered industry needs more JS people to fix JS people's shit

are these not true about the JS ecosystem?

>>59940139
>No it wasn't. It was the end result of basing a desktop application on the shitty web DOM.
The fix is in the insider builds and should be coming out in the next update. Don't mistake me for an electron fanboy, JS is a shit language and you shouldn't be building desktop programs with it, but poor performance is still usually the fault of the developers to some degree.

Firefox is written in, among other languages, javascrript

So shut the fuck up you stupid memer. Nothhinng wrong with javascript you just hate it because it is popular fucking contrarian asshole.

>>59939877
On point.

>>59938951
Portability. Write an application using the web stack and you can be reasonably sure it will function more or less the same on Windows, Linux, Mac, iOS, Android and anything else with a modern web browser.

There are still occasional compatibility issues, but it's far closer to being truly portable than any of the alternatives. It's also (until WebAssembly starts to pick up anyway) the only language you can use client side in a browser.

>>59938951
>mfw was geeking away jerking off pointers in C for months
>got a quick 5k$ react/electron gig
>don't know es6 or react or webpack or electron, 90% time spent configuring shit for comfy dev, 10% fizzbuzz, literally copypaste shit until it works
>client happy
what can i say, webdev for life, probably gonna add some critical stuff in C, gotta install that job security