6 ms·
Atom 1.20
- Dowwie 9y agoAtom 1.21 features support for the language server protocol
- paule89 9y agoHow about reducing the memory footprint?
- _eht 9y agoYou were downvoted to oblivion, but honestly this is a huge issue that somehow feels like people are just OK with. Honestly, work with Atom open for a day or two on the same project, that's not uncommon right? Prepare yourself for some serious type lag. Full disclosure, I run a Linux desktop with 32GB of RAM. I'm not accustomed to type lag. Judging by your downvotes it's an acquired taste.
- dmit 9y agoI downvoted paule89's comment because it felt like a cheap shot at an established product with well-known pros and cons. Yes, Electron apps consume a bunch of RAM. Yes, Rust needs you to deal with data lifetimes. Yes, Go still doesn't have generics. Yes, Haskell has a steep learning curve if you learned imperative languages first. No, restating those facts on HN at every opportunity is not constructive.
- _eht 9y agoIt's a hugely beneficial visual when they are deciding what to prioritize on the roadmap going forward. It's input directly from their user base about what they want in their work environment.
- dmit 9y agoDo you think this thread is the best place for that input? Or that the input is valuable enough to post at any opportunity? For the record, I disagree with both of those statements.
- _eht 9y agoYes, I do think this is the best place for that input. People post things on HN, and there is a comment section where we talk about the thing. What else would be in a thread about a thing? Noted.
- methodin 9y agoPerhaps not but not all of us follow such things as closely as you might so the assumption that it's common knowledge is not necessarily accurate.
- dmit 9y agoYou're absolutely right that not everyone seeing this comment tree knows the details of Electron's memory usage. But I don't think that GGP's original comment was aimed to educate those people about the issue. To me it just sounded like a quip aimed at getting some cheap points from the choir.
- methodin 9y agoYeah I could see how if you are used to seeing such posts it would come as more of a slight but from my perspective it's good to know people's gripes about a product having not followed much about this before - especially if some people might be trying it out as a result of the article. The ambiguity of purpose is the bane of internet comments.
- krainboltgreene 9y agoIf you have 32gb of RAM and you're getting type lag after 2 days, it's probably not a RAM issue, right?
- yjftsjthsd-h 9y agoWe'd need to know how much memory Atom itself is using after that time. Perhaps GP has found a memory leak, perhaps he's on an Atom processor; we don't know unless he tells us about resource use by Atom itself.
- _eht 9y agoYou might be right. At any rate it felt like an Atom issue, as I've not experienced lag like that on Bluefin, Geany, and other similar editors.
- alloyed 9y agoit can still be an issue with memory even if it isn't as blatant as "out of memory". The easy example being a datastructure growing over time and getting slower to manipulate and query. This is a problem where being cavalier with the amount of memory you allocate and use will hurt you, even if you've got lots of memory to spare.
- wjoe 9y ago>Honestly, work with Atom open for a day or two on the same project, that's not uncommon right? Prepare yourself for some serious type lag. I dunno, I have the same Atom instance open on Linux for weeks with 20+ files open, I haven't experienced any noticeable lag. Maybe I'm just not as sensitive to the sort of lag you're experiencing.
- cyberferret 9y ago> Honestly, work with Atom open for a day or two on the same project, that's not uncommon right? Prepare yourself for some serious type lag. iMac with 32GB RAM here, and I routinely work with 10+ tabs open with files of 1000-2000 lines of code, and never really noticed and lag or crashing in Atom? I leave Atom open and running 24/7 for days at a time. In fact, this morning was the first time I remember restarting Atom in over a fortnight because I installed 1.2.
- SwellJoe 9y agoTo add another anecdote, I tend to have an Atom window open with a couple dozen projects and a dozen or so open tabs for days or weeks at a time. I haven't noticed this problem. I'm on a Fedora Linux laptop with 16GB of RAM. Atom is big, but I haven't noticed any lag or seemingly memory-leaky behavior. Maybe one of the plugins you use is causing it?
- jimnotgym 9y agoI use Atom in a couple of places 1) Old Linux laptop with 4GB of RAM which I leave open for days on end without issues 2) Linux VM on virtualbox on my 8GB Ram desktop. I went for months leaving Atom open in the VM (saving it day to day) without issues I'm not even using an up to date version of Atom? I know Atom is not great with very large files (it warns you before you open them) but for me this is only things like logs which I read from the command line with tail and grep. I have no need to open large files in my coding editor.
- anonfunction 9y agoI'm on a MacBook Pro with 16GB RAM and I usually have Atom running ~5 projects with multiple tabs of source code open on each. I've left them open for days or even weeks and have not noticed any type lag. I wonder why you get type lag, maybe you're working with really large files?
- mmirate 9y agoAs long as it's Electron-based, that's basically impossible.
- _eht 9y agoI was a fan of Atom until I tried VSCode. Call me a shill, if you will, but it is an all around better experience and I haven't looked back.
- bauerd 9y agoThis has been my experience as well. I really wanted to like Atom, but then I tried VSC. It's an incredibly well done editor, and it doesn't feel nearly as laggy as the average Electron app.
- babaganoosh89 9y ago+1, VSCode feels way more polished.
- michaelmwangi 9y agoSame here the moment I tried VS code I never went back even abandoned my PyCharm IDE.
- kylehotchkiss 9y ago+1, my coworkers always teased me for sticking with Atom and tried to get me to Sublime Text but VSCode was the first thing post-atom that stuck. Atom just could not handle big files well, and years of waiting sadly didn't yield big enough results.
- igrekel 9y agoYes, big files has always been the major issue for me. I always kept sublime text around for some larger files and ultimately decided I would only stick with a single editor.
- czechdeveloper 9y agoWhy shill. It's just great tool. I love lots of what MS does. I still consider C# best language I ever learned.
- nurettin 9y ago
- zackify 9y agoEvery update I hope there won't be lag, but sure enough there always is. Leave it open for a whole day and text input + browsing a project tree will freeze periodically. I'm on a maxed out Mac too...
- Siilwyn 9y agoYou could try running it with no custom plugins. If it still happens I would report the issue at their GH repository. As others above have said, me included, never experienced what you describe.
- dna_polymerase 9y agoStill prefer Sublime over Atom. I can't stand software that wastes Memory like Atom does. Then again Atom has a nice UI. Maybe in the future...
- SwellJoe 9y agoI'm really impressed with the tick-tock of Atom development. Their turnaround time on releases with major new features in each release is really something to see. And, it's a pretty decent rebuttal to the questions folks raise about the decision to build on Electron in Javascript. The tradeoffs are big (memory, startup time, performance), but the benefits are maybe bigger (huge dev community, tremendous resources being thrown at the biggest problems in the form of work on the JavaScript engine and language, easy-ish entry for new developers, etc.). Even with all of its flaws, it's still a better experience enough of the time for enough of the people that it's become one of the most popular editors almost overnight.
- deleted 9y ago[deleted]
- thewhitetulip 9y agoBy how has the performance improved? The last I checked Atom was way too slow as compared to other editors even VSCode.
- jasonrhaas 9y agoI've tried all the editors, when it comes down to it I always end up going back to some combination of Sublime + Vim. I prefer to do most things on the command line rather than set up IDE configurations, so a plain text editor suits me just right. I like the customization of Sublime, and I've got it setup just how I like. In a way, Vim is similar... once you get it customized perfectly, there isn't going to be another text editor that beats it. VScode is nice, but I don't really see any pros to it that would make me switch from Sublime, other than the Debugger maybe (which I never use).
- catacombs 9y agoWhat's your combination of Sublime and Vim? I've recently switched from VSCode to Vim and have really started to like it. I try to use Vim keybindings in everything I do, including browsing on Chrome with the plethora of Vim-like extensions. I still use Sublime, mainly for its multi-cursor editing power. I don't there's an editor that can really match Sublime's multi-cursor feature. I know there's a way of doing in in Vim, but I'm still learning this language, and it seems like a difficult concept for me to grasp right now
- jasonrhaas 9y agoI just meant that I use Sublime and Vim as my primary text editors. I do use the "vintage" mode in Sublime also, which mimics some of Vim's functionality.
- sjellis 9y ago"I prefer to do most things on the command line rather than set up IDE configurations, so a plain text editor suits me just right." For me, the killer feature of editors like Atom and VS Code is zero-hassle setup of linters and code formatters. The integrations with Go tools will not only tell you what is wrong with your code as you work, they will automatically manage your imports directives and reformat the source. Periodically I think about switching to Vim. I am sure that I could set up Vim to have the same features, but I feel like I might have to find a big chunk of time to learn how to manage Vim plugins and the appropriate key combinations to get the same effect.