4 ms·
>> Atom's primary innovation They couldn't make it fast on modern hardware? It's a significant indictment of the technology, and of GitHub's engineering that
by biocomputation 10y ago
>> Atom's primary innovation
They couldn't make it fast on modern hardware?
It's a significant indictment of the technology, and of GitHub's engineering that a product like Atom is slow on th high-end Dell hardware that my employer buys for me.
Atom's problem, which includes the astoundingly enormous amount of CPU and memory that it guzzles, is that the people who built it demonstrably didn't care about performance, didn't know better, or both.
Atom is a textbook example of how not to write software. I guess it's not only 'hackable to the core', but 'inefficient to the core'.
It's just bad software.
- niftich 10y ago> It's a significant indictment of the technology Yes, it is; much more so an indictment of the stack than Atom itself. > didn't care about performance Perhaps; I can see why they would prioritize features over performance. > Atom is just a textbook example of how not to write software. I disagree. I very much feel that Atom is about demonstrating an archetypal 'desktop application', like a text editor, in Electron. And Electron is about coding in HTML/JS/CSS, albeit currently it's backed by a entire shrinkwrapped Chromium, which means you're essentially stuck inside a particular browser and inherit all of its performance characteristics. It's the Electron stack that must prove that it's viable in the long-term, but it's possible that Atom will catch a lot of the flak instead.