[TheOtherHobbes]

It may be the fastest way to develop UIs, but it's the slowest and least efficient way to run code.

This makes it useless for any non-trivial app that is CPU bound - including, games, audio, video, 3D, and many many more.

Just because it's easy to build a house with Lego doesn't mean it's a good idea, or that it's going to compete with professional building materials.

[deadbunny]

So they should do what?

1. Use current dev team to develop only the web version?

2. Hire X teams to develop for X platforms? (there goes your linux support)

3. Hire 2nd team to work on a cross platform native desktop client?

4. Open APIs and leave it to the wolves?

Everyone on here is acting like a few hundred meg of ram and barely 0.5% CPU usage is the end of the fucking world.

[swebs]

#4 please! The days of GAIM/Pidgin felt like the golden age of chat apps, at least as far as the user experience was concerned. Just one centralized app could manage all the disparate protocols without ads or millions of analytic scripts tracking every mouse movement. And it barely took up system resources.

Also, you'd be surprised how fast 4gb gets used up by the time the OS, the browser, and various Electron apps take their cut. I can't browse the web while having Slack and Spotify open or things start thrashing. I think it's past the point of ridiculousness when a simple chat app takes more memory than a full featured IDE like IDEA.