![]() ![]()
I also had no other plugins other than the default bundle. >and I've also seen this behavior while editing small Python files. So I returned to my dark corner under Eclipse to work and recover. I tried to migrate to it, but it has burned me with its radioactivity. Maybe my build was buggy (I used an official deb package BTW), or maybe he tested a buggy version, but these problems were (or are) real for some other people, and they may have been solved or not but I'm neither the only, nor the last people who talked about excessive memory usage of atom. Honestly, maybe atom was not optimized for better memory usage before. I used atom as a pretty text and script editor for my needs, but its auto complete capabilities left too much to be desired for me. I develop at the system level, and for development scenarios Atom is nowhere capable as Eclipse, and seriously that's OK. It looks like you're a web developer, I'm not. It can be, just like with any language/platform, but it's not "inherent" to the technology.įirst of all, for the 800MB thing, there's the source: and I've also seen this behavior while editing small Python files. There are a lot of problems with Electron, but memory usage isn't one of them any more. Switching to something which uses a few hundred less MB of RAM for a fraction of the capability would be a monumentally stupid thing to do, as Atom makes me significantly more productive than any other editor I've tried has ever before. ASCIIDOCFX CHANGE PREVIEW STYLE CODELinters, autocomplete, code analysis tools, CI server integration, a webserver for serving up my application in the editor, a debugger that links the live preview in the editor with the code in the editor, and a ton more. ASCIIDOCFX CHANGE PREVIEW STYLE WINDOWSAnd those windows have been open for about a week now.Īnd that Atom instance is running a lot of what your Eclipse instance is running. I personally have currently 5 windows open in atom, with about a combined 40 tabs, and about 30 plugins installed, and my instance is using 360mb of memory right now across all processes. And that's not indicative of a "normal" Atom user (if there can be such a thing). Facebook just released information on the average memory usage of "nuclide" (their Atom editor bundled with a metric ton of plugins which use quite a lot of memory) to be around 600mb. This is an over exaggeration, and quite a large one. If you can write an application with a GUI which slow to respond to low-complexity, common tasks (naive text editing, input, menus, moving windows), something is very, very wrong (to be clear, GUI can trigger resource intensive background tasks, but that's not what I'm saying). ![]() Python is easy, but it's not as performant unless the underlying library is native, hence nobody is using it if it can't obtain very high performance in my field (scientific computing, HPC, and related areas).Īctually, writing a low performance GUI is pretty hard since most of its cycles are idle. I develop in C/C++/Python mainly and in some other languages for fun and curiosity. C is "slower" than assembly, yes however both assembly can be inlined into C, and magnitudes more can be done with C at near-assembly speeds. Resource usage can be justified if the that resources is used toward something meaningful. ASCIIDOCFX CHANGE PREVIEW STYLE PORTABLEAlso, Eclipse is portable around all major operating systems. Atom runs nothing at the back or provides the same functionality while using 800MB. On the other side, my Eclipse installation uses ~1100MB and runs whole array of analyzers and background stuff that an IDE should run. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |