3 ms·
I am. I went from vim to Atom, and then to VSCode, because it was Absolutely Fast Enough (I was using a 2014 rMBP in 2020! it was fine!). You can write slow, ch
by eropple 3y ago
I am. I went from vim to Atom, and then to VSCode, because it was Absolutely Fast Enough (I was using a 2014 rMBP in 2020! it was fine!). You can write slow, chunky crap in Electron, granted. But IntelliJ has been doing that in Java and Swing for years and nobody grinds their axe about that.
Electron isn't the problem here. And neither is JavaScript (well, TypeScript--JS itself isn't great). If anything is, a combination of competence and scheduling are the culprits.
- jen20 3y agoElectron is a different problem: lowest common denominator crap. Apps that don't form a cohesive platform, because some product middle-manager wants to piss all over the users desktop to leave their own "branding" scent. The fact that most of them are also poorly engineered is orthogonal.
- eropple 3y agoSo maybe it's different from your use case, but I use the same applications on multiple platforms so I don't care about the underlying OS. I'm a browser/terminal/editor sort for the most part, so VSCode acts close-enough to native on Mac, Linux, and Windows, in terms of keyboard shortcuts and affordances (hitting enter to rename on MacOS, for example)--the look of it is completely transparent to me. Balena Etcher's another good example of that. Thing just works.
- pjmlp 3y agoSwing applications are famous for a reason, and it isn't because they are an example of excelency. It is not an accident that Swing only survives as toolkit for developer tooling, and Java is mostly relevant on the server. Even on Android, the devices are more beefy than iDevices for a reason.