81–90 of 93 posts
Earlier quoted context omitted.
If V8 can't handle it, there is no way Atom will handle it. Some would assess this as major software design issue (yeah I mean me).
Why can't V8 handle it? Too many pointers on the heap?
For once, on an atom release thread, can we have a discussion about atom and this release rather than endless threads about folks preferring vscode or sublime?
Not on HackerNews in this reality, a while back someone did analysis of most voted comments, the top-comment is usually contrary to the post and its first reply is counter-contrary (pro-OP). Post about Golang -> get pro-Haskell comments, Android iOS, iPad Surface, Linux *BSD. Its what we are.
For once, on an atom release thread, can we have a discussion about atom and this release rather than endless threads about folks preferring vscode or sublime?
Sure, let's focus on Atom's speed issues.
"Oh, I don't have a problem with my laptop's CPU fan spinning like a lawnmower. Surely deep architectural nonsense will be solved in the next minor update."
Earlier quoted context omitted.
Wholeheartedly agree. I just tested this new version out. I really keep trying to use Atom, but it's just unacceptable currently when compared to Sublime. Very slow startups and laggy. This new version takes 5-10 seconds before I can start coding, that's far too slow. With every update I keep hoping things are faster, but only marginally so. VS code loads in less than 3 seconds and is a lot more snappy. I don't under…
> This new version takes 5-10 seconds before I can start coding, that's far too slow. Last time I had to launch Atom was when 1.8 was released. In the use case where you leave the editor running this startup time isn't a problem.
Earlier quoted context omitted.
VSCode from Microsoft is also wrapped in electron and uses a fraction of what Atom is consuming. Not being native has nothing to do here.
The memory consumption is a magnitude larger in JavaScript than native. http://benchmarksgame.alioth.debian.org/u64/compare.php?lang...
There are javascript editors that don't use as much memory as atom. What you're saying is irrelevant.
Earlier quoted context omitted.
> This new version takes 5-10 seconds before I can start coding, that's far too slow. Last time I had to launch Atom was when 1.8 was released. In the use case where you leave the editor running this startup time isn't a problem.
I would love to see how many petabytes of RAM your installation is using.
I have participated a bit in the Atom.io open source repository, but now I am back to Sublime. It's so fast and reliable compared to Atom.io.
Wholeheartedly agree. I just tested this new version out. I really keep trying to use Atom, but it's just unacceptable currently when compared to Sublime. Very slow startups and laggy. This new version takes 5-10 seconds before I can start coding, that's far too slow. With every update I keep hoping things are faster, but only marginally so. VS code loads in less than 3 seconds and is a lot more snappy. I don't under…
VS Code and Atom both launch a 'full' browser and server, html, css, js and the whole shebang to make all of that work; while Sublime is compiled C++ (with a python API).
But think of how many software abstractions/levels each line of atom code has to go through. I mean, each keypress probably produces in the order of 100 million CPU instructions in the metal (number pulled out of my behind but you get the idea) just to display a single character. Is this what progress looks like?
I guess there's a balance between developer comfort and software efficiency.
Earlier quoted context omitted.
So I don't clog up the rest of the comment thread I'll add my atom/vscode/sublime thoughts here. I've been a long time sublime user and found it very very difficult to switch to anything else, mainly for performance reasons. But I decided to give atom and vscode a real try for a couple of weeks each. These are my findings and results. I started with VScode when dotnet-core was officially released for OSX. The debuggi…
Sublime also has the reveal in sidebar functionality. At least my setup has, not sure if it came with the enhanced sidebar plugin, but you need that one anyway to be able to work properly. Indeed I liked the good looking atom without configuration. Lately I switched back and use sublime with the material theme which is great, but atom is much easier to style, or doesn't event need it. In the end it was startup perfor…
Earlier quoted context omitted.
This, and the inability to open large text files. You would think a priority for a text editor would be to be able to actually open text files and write correctly on them.
If V8 can't handle it, there is no way Atom will handle it. Some would assess this as major software design issue (yeah I mean me).