News for hackers. Stuff that matters.
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by butz on Tuesday August 08, 2017 @04:17PM (#14962070)
How does VSCode manage to take up less disk space than Atom, with similar feature set? Currently on Windows box: VSCode 1.14.0 - 156MB Atom 1.19.0 - 516MB
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by mirekrusin on Tuesday August 08, 2017 @04:43PM (#14962451)
Maybe it boils down to npms? Atom is using `dugite` npm for git, which takes more than 40MB alone, babel-* packages are probably above 50MB and silly things like emoji-images >11MB... but to be honest VSCode must be taking more space than that, maybe they're keeping npms outside of the main app because electron framework itself takes 167MB on the current Atom so technically you can't get below that.
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by nkkollaw on Tuesday August 08, 2017 @04:39PM (#14962377)
We always have to have somebody remind us how wonderful VSCode is compared to Atom every time there's a post about Atom.

I'm wondering—if you prefer VSCode, why even comment a post about Atom? I doubt your care that much..?

Atom is built on Electron. That means that it includes a whole version of Chromium (OMG!), and it isn't even optimized, so its size is 5 times that of VSCode.

Is that really a problem? Are you trying to tell me that as a developer you don't have 400MB to spare on your hard disk for one of—if not the most—important tool to work your job, and the size is really a reason to pick one editor over another?

Atom is about 100 times slower than Sublime Text, and like you pointed out 5 times bigger than the insuperable VSCode.

Now, I use Atom as my main editor, because I find it simpler than others for certain things, and it saves be a lot of time because GitHub integration is done very well. Also, I like the name (can't say the same thing about VSCode).

Some people like Atom because they're more productive, and don't care about its size, super-crappy speed, and whatever else you think Atom is worse than VSCode at.

Can we put this thing to rest..?

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by MisterKent on Tuesday August 08, 2017 @04:50PM (#14962534)
VSCode is also built with electron[1], so that doesn't excuse it. Atom's defenders always bring up that it was made with electron as the reason for it's slowness. Then, VSCode came along and invalidated that. Now, that leaves only one conclusion: Atom is slow because it was not engineered well.

And no, I don't think anyone is ready to stop pointing out that Atom is slow. Atom can implement a thousand killer features, but until they fix their performance problem nobody is going to switch back to it.

[1] https://en.wikipedia.org/wiki/Visual_Studio_Code

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by nkkollaw on Tuesday August 08, 2017 @04:56PM (#14962615)
Meh.

I tried many editors when I decided which one to use—including VSCode—and Atom was the one where I was the most productive by a long shot.

Speed isn't everything. Atom is quick enough for the code I work on, and in other, much faster editors like Sublime Text I would be less productive and therefore slower. For instance, editing settings/packages in Sublime Text in unnecessarily nightmarish. Changing settings and installing plugins in Atom is a breeze.

Who cares if the editor is a few milliseconds faster when you're many minutes slower..? Just because of its excellent GitHub integration Atom is worth 100 times more than Sublime Text to me (even if it wasn't free).

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by castis on Tuesday August 08, 2017 @05:02PM (#14962667)
> Who cares if the editor is a few milliseconds faster when you're many minutes slower

Me. I care. That little hang Atom does after saving a file gets annoying after a while.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by nicwolff on Tuesday August 08, 2017 @05:24PM (#14962874)
That's fixed in the linked update: "Saving a file now happens asynchronously without blocking the UI, so that you can move smoothly from one task to the next."
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by nkkollaw on Tuesday August 08, 2017 @05:12PM (#14962750)
Then you might give Sublime Text a try.

I get annoyed about having to switch to GitHub, for instance.

It's fine to have opinions, I'm just annoyed by the fact that every time there's a post about Atom the conversation gets hijacked by "VSCode vs. Atom" comments.

That's why I'm bitching.

I shall go update Atom instead.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by sds2 on Tuesday August 08, 2017 @05:47PM (#14963155)
> Atom's defenders always bring up that it was made with electron as the reason for it's slowness.Then, VSCode came along and invalidated that.

How so?

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by nkkollaw on Tuesday August 08, 2017 @06:47PM (#14963702)
He's saying that since VSCode is built on Electron and it's fast, the Atom guys can't blame Electron anymore.
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by sds2 on Wednesday August 09, 2017 @01:35PM (#14971614)
Where is the proof on vscode being "fast"? And compared to what? I can only talk about my and some of my friends' personal experience but it won't praise vscode's performance. It's maybe less glitchy(latency) than atom but it feels like it's still far from sublime/emacs/vim.
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by fookYou on Wednesday August 16, 2017 @05:06PM (#15031378)
vscode is slow as dogshit. Its performance is barely passable on windows(making it just barely usable), but when you run it on linux its pathetic and glitchy. If Vscode could eliminate click latency and unselecting highlighted text latency/glitches, it might be an ok editor. I will say the features it has are impressive, but its downsides are outweighing its benefits for me on ubuntu 16.04.3 on the brightside, my replacement ssd will be here soon and i can return to windows 10 and vscode is much better on windows, since windows always has superior desktop performance to linux.
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by eridius on Tuesday August 08, 2017 @04:41PM (#14962420)
> Atom is built on Electron.

So is VSCode.

> Can we put this thing to rest..?

Where's the harm in having an actual discussion about this? If you're comfortable with your choice of Atom, you can just ignore anyone comparing Atom to VSCode.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by nkkollaw on Tuesday August 08, 2017 @04:45PM (#14962475)
The harm is that every time there's an Atom post, most comments are about how much it sucks compared to VSCode, and always from the point of view of memory footprint, and size. I have both GB of memory, and GB of HD space.

I don't get the point.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by krisdol on Tuesday August 08, 2017 @05:23PM (#14962857)
I'm guessing they are trying to run atom on an embedded android smartwatch OS backported to 2006 hardware? I've never found the argument compelling. My memory is there to be used by apps I use.
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by nkkollaw on Tuesday August 08, 2017 @05:32PM (#14962973)
Yes, I have no idea.

It seems more like discussion just for the sake of it, then because of actual, real-life problems.

My laptop isn't even amazingly powerful, and I constantly have 3GB to spare despite the fact that I run many random apps and almost never restart it.

As a developer, I don't see what the problem would be if my main tool occupied even 2GB of memory (and we're talking about 500MB-1GB in most cases).

I never heard any graphic designer complaining about Photoshop occupying 10GB of memory for a logo (which happened to me a few hours ago).

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by holtalanm on Tuesday August 08, 2017 @04:58PM (#14962642)
Atom is built on Electron -- So is VSCode

GitHub integration is done very well -- Not nearly as well as the Git integration in VSCode

Also, Atom has in the past been much slower than VSCode in nearly every aspect.

VSCode has a built-in debugger which takes it dangerously close to being called a full-fledged IDE rather than just a text editor with plugins cough Atom cough

The reason they keep getting compared is really simple: they both aim to achieve the same goals, and both use a very similar approach.

One editor I haven't seen mentioned in a LONG while, though, that can probably be considered the 'grandfather' of both of these is Brackets. If I remember right, it had a lot of performance issues, as well.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by wcummings on Tuesday August 08, 2017 @09:44PM (#14964843)
>VSCode has a built-in debugger which takes it dangerously close to being called a full-fledged IDE rather than just a text editor with plugins cough Atom cough

Is that a bad thing? I like debuggers.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by holtalanm on Wednesday August 09, 2017 @09:14AM (#14968373)
That was meant as a positive point. The debugger in VSCode is phenomenal, while there isn't one for Atom.

VSCode ranges closer and closer to a full-fledged IDE, which is awesome.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by Ezhik on Tuesday August 08, 2017 @08:16PM (#14964322)
>it includes a whole version of Chromium (OMG!)

OMG! is right, imagine trying to make sure the zoo of various Node and Chromium versions on your computer do not have any unlatched vulnerabilities.

And you know? I have 400 MB for one Electron app. I even have 8000 MB for 20 Electron apps. I just do not want to give them because you'll eventually tell me that your containerized Electron-on-Docker-on-Electron virtual machine requires 64GB of RAM to run.

Now, I'm not saying that you should not use Electron ever. But if using a TEXT EDITOR on a laptop with 2GB of RAM requires sacrificing a quarter of its resources, that text editor is not a good piece of software. And if you say I should buy an OP max-spec computer to write freaking HTML, you are creating an unnecessary barrier to CS.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by hibbelig on Tuesday August 08, 2017 @04:44PM (#14962462)
It's actually a valid question: Both Atom and VSCode are built on Electron, both provide similar functionality, and one is a lot faster than the other. (Or _was_ a lot faster than the other?)

So it's valid to ask what did the VSCode people do to come to the different result?

On a related note, I wonder about the speed difference now, after Atom has done a lot of optimizations.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by krisdol on Tuesday August 08, 2017 @05:25PM (#14962892)
I'm guessing a lot of cruft built up on atom as it was iteratively built on top of developing front-end frameworks and transpilers over the years, compared to vscode which came on the scene much later when a lot of this had already settled. My guess it's just an older project with many times more contributions that accumulated legacy cruft that takes time to fully expunge.

I'm also not convinced the feature set is identical. Atom comes with a lot of language support, customization options, and extensibility out of the box.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by ythn on Tuesday August 08, 2017 @05:16PM (#14962784)
People are just incredulous that Microsoft is able to make an Electron app of superior quality than GitHub (who develops and maintains Electron).

It would be like if Honda made a better car utilizing a Mazda engine than Mazda itself.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by nkkollaw on Tuesday August 08, 2017 @06:50PM (#14963713)
Steve Jobs said "iTunes on Windows is like giving a glass of water to somebody in hell", what you're saying might be less rare that we think :-)

(I hate iTunes, and have no idea if the Windows version was a better Windows programs than others, I just thought I'd leave this here)

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by spiralx on Wednesday August 09, 2017 @10:37AM (#14969387)
No, iTunes on Windows was at least as shit as it was on OS X, both in terms of awful UI and the sheer bloat of it and all the extra crap it installed.
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by jdormit on Tuesday August 08, 2017 @04:42PM (#14962432)
> Atom is built on Electron

So is VSCode! Hence the constant comparisons.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by laken on Tuesday August 08, 2017 @04:43PM (#14962460)
Atom also happens to be built on Electron; I think that commenter was genuinely curious as to how Atom was that much smaller than VSCode when both are built with similar technologies.
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by Volt on Tuesday August 08, 2017 @06:22PM (#14963489)
The parent asked a legitimate question. Do you have an answer?
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by FRex on Tuesday August 08, 2017 @05:37PM (#14963037)
Even VSCode is sloppy and could go down easily IMO.

They have a folder with js modules (I didn't look too deep into it, there might be native dlls there too) that's 75 megs, compressing (and i.e.: recompressing on any change, update, download, etc.) would help with disk space taken and loading times. Not even an SSD will beat a zip file kept in memory, SSD, resolving file paths, NTFS, they still have overhead and I'm sure it'll be more than just decompressing out of a zip in memory.

would beat keeping that zip in memory and accessing it to decompress any script when needed. 75M resources 17M resources.zip 6.7M resources.7z

Third party ones aren't even minified which would be free size savings!

It's basically free saving and super common in game dev to package files and not have them scattered like that.

Re:Atom 1.19 – Improved Responsiveness and Memory Usage by glibgil on Tuesday August 08, 2017 @04:21PM (#14962118)
The developers of VS Code wanted it to take up less space? I'm sure someone could reduce Atom to the same footprint
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by ComputerGuru on Tuesday August 08, 2017 @04:34PM (#14962312)
I don't think anyone is questioning that; I believe the OP's question was more along the lines of "what wasteful resource management strategies on behalf of Atom's developers lead to the product consuming so much space and running so slow?"
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by glibgil on Tuesday August 15, 2017 @06:43PM (#15023413)
You misunderstood my answer. The only way you get to "I want this app to be no larger than 80Mb" is to make that goal and get to work. You cannot, for example, make your operating system boot faster from 30 seconds down to 3 seconds just by making things faster everywhere you can. You have to set the budget at three seconds and approach every problem from there. Atom is large because it has no size budget
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by Bilters on Tuesday August 08, 2017 @04:19PM (#14962095)
This might be an intersting article to read on the side; https://josephg.com/blog/electron-is-flash-for-the-desktop/
Re:Atom 1.19 – Improved Responsiveness and Memory Usage by striking on Tuesday August 08, 2017 @04:22PM (#14962131)
They're both Electron-based. One is just less optimized than the other.

(edit: the parent comment has been edited. Mine no longer makes sense in context.)