4 ms·
Conversely, I’ve had to kill -9 some Electron-based apps lately because their myriad of helper processes were hung. It is substantially easier to debug these is
by mattgreenrocks 3y ago
Conversely, I’ve had to kill -9 some Electron-based apps lately because their myriad of helper processes were hung. It is substantially easier to debug these issues when you don’t have an entire browser engine gunking up your crash reports.
Between that, the RAM requirements, and the overall sluggishness of Electron-based apps, I’m not impressed. They’ve had what, a decade now to get their house in order?
It’s Java on the desktop all over again. Except now there’s a hegemony demanding that all dev be as cheap and shoddy as possible, so everyone just shrugs and moves along.
- palata 3y ago> It’s Java on the desktop all over again. What was the problem with Java on the desktop? Maybe I was a bit too young to remember. I just remember that Java apps looked "funny". But in my experience with the JetBrains apps in the last 8 years... JVM rocks. I hate ElectronJS though.
- mattgreenrocks 3y agoJava desktop apps looked and felt off, because all the windowing toolkits had to reinvent the [windowing] universe from scratch. Cold boots of apps could be painful, as the JVM didn't optimize for that, and actually deploying the apps was not pleasant (fun times guessing how much RAM the app should take as part of the CLI args). Nowadays I have few issues with JVM apps on the desktop other than non-native UI, but that ship sailed a long time ago. And yes, JetBrains is a great example of how to do this well.
- The_Colonel 3y agoComputers were much slower than today and even JVM was slower. Java wasn't open source. Plus the non-native UI made Java on desktop a meh experience.