2 ms·
Point by point: 1) If Electron fails, you are fucked on all platforms: a worse worst case than the fragmented lock-in of multiple native platforms. 2) JavaScr
by HelloNurse 3y ago
Point by point:
1) If Electron fails, you are fucked on all platforms: a worse worst case than the fragmented lock-in of multiple native platforms.
2) JavaScript sucks, and as noted in other comments the "vast ecosystem of libraries" is even worse. Overcomplication is part of the problem, not of the solution.
3) Startup times and memory occupation add up, and then the wasteful Electron app causes more problems than it solves.
4) Platforms that appeal to ignorant hipsters tend to be used badly. Not Electron's fault, but Electron is a warning sign, well correlated with all sorts of problems.
5) Electron might be the "only" option if you are an ignorant hipster, chained to JavaScript and behind the times; but there are still plenty of competent people and reasonable projects that can adopt less super risky technology.
- jamager 3y agoUnwelcoming stereotypes and labels were not called for. Arguments were called for, which you give 0.
- ironlake 3y agoThe "ignorant hipster" comment is uncalled-for. There's nothing wrong with accessible tools. But I agree with all your points. With regard to point 4, if I download a desktop app for my Macbook and it's Electron, I see it as a sign of minimal commitment to user experience. They prioritized cost over my experience and I'm probably not going to choose that app unless there are no other options. I do the same with iOS apps. If it's not native, I'll usually delete right away.