4 ms·
What about the users? This whole thread is entirely developer centric. Odds are you are going to have 1000x more time users than developers. A native solutio
by snarfy 3y ago
What about the users? This whole thread is entirely developer centric. Odds are you are going to have 1000x more time users than developers. A native solution and not some node interpreted monstrosity is the right choice. We all loathe electron apps because they perform like shit. What's worse, inconvenience a handful of developers to learn a native language, or make thousands of users run node apps? The carbon footprint alone is worth it.
- Timon3 3y agoI disagree. If the program is fast enough for its purpose, and my developers can write better code (as in, code with better architecture allowing for flexible development while being easy to read) and develop features faster, it doesn't matter which language is "right", it matters which one will get the thing developed in an acceptable amount of time. Users would rather have bad software than no software, as you can see with Electron apps that perform like shit. I'm not saying that performance, memory consumption etc. are completely insignificant. I myself prefer to use faster tools that use less memory. But if all you have is a bunch of Typescript devs, and you want them to develop a CLI, you're not going to get a better result by telling them to do it in Rust. To get a better result you'd have to tell them to learn Rust and work in it for half a year. And yes, that would be better for users in the long run, but that doesn't mean it's realistic in all cases.