atom as an editor is too big #9755
Comments
Atom has been reduced in size significantly in the past (#6313, #6407, #6395, #6447, atom/notifications#54, among others). As a matter of fact, the If you have examples of duplicate code or specific suggestions of methods for shrinking the size of Atom, please open Issues or Pull Requests with that information. Unfortunately, I fear that simply "make it smaller" is not specific enough to be actionable. |
I'm not a node developer don't even know how to hack this project. the
|
There are a number of things that Atom could do to reduce install size, but tbh, does it really matter? Engineering work costs time, and optimizing disk space isn't really worth that time given that you can buy a 16GB USB Thumb drive on Amazon for less than a cup of coffee (in San Francisco :P). That's 78 copies of Atom, for $5. |
I think the original user's concern is not about disk space but download bandwidth. Disk space is indeed cheap. Bandwidth isn't so, especially if you live somewhere where you can't switch ISPs. |
that's not a good excuse for doing nothing, not everybody like you github employees (I heard most atom developers are ?) has a macbook for each, and there are many ones still using old computers, ... |
This is challenging the person, not the idea, and is generally considered poor form in online discussions. You still haven't addressed my concern with this Issue, @crquan, namely that there isn't a method of determining if Atom is "beyond the size of an editor should be". You only state that 208MB is too much. A bug is nearly worthless if it cannot ever be fixed. And without a clearly defined goal, this bug cannot be fixed. Is 207MB too big? Is 200MB? Is 10MB? Please give an example of what size is "small enough" and what size "too big" and, most importantly, why. |
In any case, as long as Atom uses electron, it's going to be an order of magnitude larger on disk than the example you provided (sublime 3 at 7 megs) because of libchromiumcontent, etc. We're generally working on reducing the file size of the editor where we can, but I am going to close this issue in favor of more specific issues - you could, for example, have a conversation about the pros and cons of asar actually doing compression rather than concatenation on the electron repository, or file an issue about problems with dependency deduping in atom. Still, Atom is likely going to be in the 100 meg order of magnitude, not 10 , for the forseeable future. |
I really agree with @crquan , The package is too big, However the Atom is open source, May be This is a only advantage vs sublime, If so, How can atom accepted by common people. We all know sublime can use free for a long time which you can think. @lee-dohm as a common user, We already find the "bug" lies, not us to fix it. Not all common people go through all the code which Atom has. This is just suggestion or mind which everyone can see it. |
I'll add my comment, albeit late. I am using Atom on Xubuntu running alongside Chrome OS. I only have a 16 GB SSD to play with and once you factor in the Chrome OS, Xubuntu and the necessary software that comes with them, there isn't much room left. I currently only have 2.5 GB left so Atom is taking up 10% of that. |
@thedaniel, I do not think it is a good idea to close this, even have a plan to reduce the size of atom, why not keep this open as a place where can remind us we have a really important thing to do. not just a idea. anyway, Thanks all the efforts to ATOM. Thanks all you here. Thanks. |
Just installed it on my Mac. Gosh, it's 530 Mb... |
Atom was taking up 1.5GiB (one and a half gibibytes) in my %APPDATA% folder on Windows 10. Because this goes on my OS SSD where space is very limited, I ended up uninstalling it. This is just ridicilous for a bloody text editor, but then again it's JavaScript. |
Adding to this, Atom was taking 5.5GB on my SSD as well, most of it in local appdata. Windows 10. |
Just saying: VSCode is < 100 mb download size, ~ 200 mb memory print and also build up on Electron. |
There is a known issue on Windows where the auto-updater may fail to remove old versions of Atom. It is safe to delete all the older versions. |
I used to use atom a lot, and now it pushed me to vscode side, because obviously this HUGE beast become a problem~ |
I understand that Node.js style code must be transmitted as text, and 1.0 GB sounds reasonable for a piece of software with the versatility of Atom. Admittedly, I am also not a Node.js developer; I haven't used it in about a year and a half. However, I'm installing software on Mint 19 right now, and it's had to download an entire gigabyte. Part of why I picked up Atom was because it was so much quicker and more lightweight than something like Visual Studio. Is there anyway you could perhaps take a machine-compiled portion of that code, and put it together as a binary on the host, then distribute it selectively? Something like binary, dev, and src packages? Because it is losing its original grace, and if this keeps up, I may have to switch. |
I was searching about Atom's size and found this thread. I downloaded it from atom.io for my Mac and the app is a whopping 865MB!!! So is this normal? I was searching because I was afraid the download could have been compromised on the website or something like that... How can a text editor take more than 800 MB of disk space? |
compare to sublime 3 is 7.2MB
install size: atom is 208M vs. sublime3 is 17M
run like:
I'm trying to understand why it's so large: it seems a nodejs project / embedding a nodejs v0.10.40 binaries, and suffering the same nodejs project's recursive node_modules problem,
The largest ones are app.asar (72M), apm (33M), and node binaries (16M+11M), and there are 90 node_modules directories totally, from 277 to unique 223 package names means a lot of potential duplicate code,
The app.asar (72M) resource file seems to be a large plain text file with 16 bytes binary header, is that a webpack or something I don't understand, look like a plain text javascript file, why it needs to be 72MB large? why not try some xz or gzip compressed resource?
Could you atom developers try to reduce the size ? is there any one making effort on any node dedupe solution? if can't compare with sublime, anyway keep install size below 100M or even smaller would be much appreciated; thanks
The text was updated successfully, but these errors were encountered: