Hacker News new | past | comments | ask | show | jobs | submit login

>you don't know that the difference is due to the two platforms though

When loading the UI takes 4 seconds. Pretty sure thats a problem, and its impossible to actually /prove/ its 'just their code', there is supporting evidence due to the technologies they chose and the nature of why they're used.

>whether yours is fast or slow, and whether you can build it quickly only depends on your skillset

The software you are using matters a lot, too. You can't just throw any tech at a problem and it'l solve it. Your skillset is dependent upon what you know, and how you know to use it, but is limited based upon what is available and readily possible. Chromium and node.js have overhead, and are very good at some things, and other things they are much worse for than a native app. Add ontop the crazy environment of JS and its inneficiencies for performance in comparison, and you get a big pile of mud. Useful, if you need to create something quickly, like many startups.




for sure, its uncontroversial that there is overhead with JS and that when top performance is required this overhead can be too costly.

but is this the reason for a desktop music player to be lagging on a "pretty good system"? no way -- there's no real excuse for that. its just a shitty app. perhaps electron gives teams the impression they can just type npm in front of some stuff to turn their website into a performant desktop app -- not quite so ;)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: