Live data from Hacker News

Atom 1.9 and 1.10 beta

blog.atom.io

91–93 of 93 posts

Re: Atom 1.9 and 1.10 beta

#91
post #52

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?

> 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 Su…

Maybe Hacker News readers appreciate hearing different perspectives on issues? This leads them to up-vote quality counter points to articles.

Re: Atom 1.9 and 1.10 beta

#92
post #85
post #78

Earlier quoted context omitted.

The memory consumption is a magnitude larger in JavaScript than native. http://benchmarksgame.alioth.debian.org/u64/compare.php?lang...

So what? There are javascript editors that don't use as much memory as atom. What you're saying is irrelevant.

So if this is hard to understand, the conclusion, in simple words:

the memory consumption for a javascript editor will be a magnitude bigger than native.

In my example 66Mb Sublime vs 620MB VS Code (no plugins)

Re: Atom 1.9 and 1.10 beta

#93
post #92
post #85

Earlier quoted context omitted.

So what? There are javascript editors that don't use as much memory as atom. What you're saying is irrelevant.

So if this is hard to understand, the conclusion, in simple words: the memory consumption for a javascript editor will be a magnitude bigger than native. In my example 66Mb Sublime vs 620MB VS Code (no plugins)

halokonrad isn't talking about sublime. He's talking about Atom vs VS Code.
Post reply on HN