To anyone who is following Atom closely,
1. What happened to Xray? The Next Generation of Atom that was suppose to fix all the performance problem of Atom.
2. Is Atom as fast as VS Code now?
Atom 1.36
31–40 of 75 posts
Re: Atom 1.36
#32While Atom was Mac-only, VSCode was eating their lunch. It's too little, too late now.
> While Atom was Mac-only, VSCode was eating their lunch. It's too little, too late now. What do you mean? Atom has always been available for macOS, Windows, and Linux.
...ever tried actually using it on Windows? Like a year ago it got to ok-ish usable. A bit before that even on most Linuxes it had crappy performance.
Again, I like Atom's hackability, and mainly avoid it because the ecosystem of plugins is so full of halfly owkring abandonware
Re: Atom 1.36
#33Prediction: I believe eventually MS will kill Atom or let development languish. People will complain that "MS is evil" and "look who they were in the past" and so on, but devs will go where the features are. VS Code is one of the finest examples of open source Done Right™, and while it owes something to Atom and Electron, this is pure open source darwinism.
Strongly disagree. VS Code is a corporate tool IDE, which is dull and awkward to use as just an editor, and binary spyware in it "phones home" to its users' masters in Redmond. It's exactly what an MSDN subscriber would like, but dire for anyone else.
Atom is fun. It's easy to configure in weird personal ways, get rid of parts you don't use, add your own plugins, change CSS as you like. There's an insane number of plugins and themes. It's like emacs but organized and nice.
So far the statements from project owners in public and on Slack have been that Atom 1 & 2 development continues full speed.
If it is "killed" we'll just fork it and run up a black flag.
Re: Atom 1.36
#34Earlier quoted context omitted.
Can anyone who has stayed with Atom after evaluating VSCode comment on why to stay with Atom? I switched to VSCode and would never consider going back to Atom at this point. Since the GitHub acquisition, it makes no sense for MS to maintain both and I agree 100% with the parent comment that this will be killed soon.
I followed the crowd on the switch from Hot Dog Pro to Notepad++, then followed the crowd again to TextMate. Then again to Sublime Text. Then again to Atom. I installed VSCode and it took over my file extensions without asking me and I got annoyed and was going to go back to Atom, but then wondered why I was still playing this game. So I switched to Emacs. Now I wish I did that 20 years ago!
Emacs is amazing and I still use it when I'm inside an ssh session. But I'm a convert to VSCode because of the node debugging capabilities. Those are just awesome.
Re: Atom 1.36
#35To anyone who is following Atom closely, 1. What happened to Xray? The Next Generation of Atom that was suppose to fix all the performance problem of Atom. 2. Is Atom as fast as VS Code now?
1. I haven't heard anything about it recently but that doesn't mean work isn't continuing on it. Xray wasn't supposed to "fix" anything really, it was a fairly extreme experiment to see if it would be worth going down that path.
2. No, and it's not trying to be, as "speed" isn't their top priority, extensibility is.
That being said, the days of opening a 5mb file and the editor getting brought to its knees are largely over (unless you have poorly written extensions which can still take everything down, because again in Atom extensions are EVERYTHING and can do ANYTHING).
Re: Atom 1.36
#36Prediction: I believe eventually MS will kill Atom or let development languish. People will complain that "MS is evil" and "look who they were in the past" and so on, but devs will go where the features are. VS Code is one of the finest examples of open source Done Right™, and while it owes something to Atom and Electron, this is pure open source darwinism.
Strongly disagree. VS Code is a corporate tool IDE, which is dull and awkward to use as just an editor, and binary spyware in it "phones home" to its users' masters in Redmond. It's exactly what an MSDN subscriber would like, but dire for anyone else. Atom is fun. It's easy to configure in weird personal ways, get rid of parts you don't use, add your own plugins, change CSS as you like. There's an insane number of pl…
I think you missed the /s in your comment.
Re: Atom 1.36
#37Earlier quoted context omitted.
I followed the crowd on the switch from Hot Dog Pro to Notepad++, then followed the crowd again to TextMate. Then again to Sublime Text. Then again to Atom. I installed VSCode and it took over my file extensions without asking me and I got annoyed and was going to go back to Atom, but then wondered why I was still playing this game. So I switched to Emacs. Now I wish I did that 20 years ago!
Why? (compared to Sublime Text, Atom and VSCode)
I think it's a case of "you can't be told, you have to discover for yourself"... I've written it off a few times in the past. I thought Emacs was just a text editor - and after trying it a couple of times it seemed like a clunky relic with really stupid keybinds.
This time when I tried it I started to realised that Emacs is a text editor like a saucepan is a popcorn maker: it can do it, but that's not the point.
Once you commit the stupid keybinds to memory, it works the same in most "modes" - git mode, JS mode, file management mode, ftp/remote file mode, hackernews mode... Now I rarely leave Emacs - my entire workflow is inside it and everything starts to feel like "one". It's replaced a dozen third-party apps and websites I'd normally use. I'm annoyed when I have to leave.
It's crap by default, you have to make it your own. Then it's lisp all the way down. You can ask "what is the command bound to the down arrow key?" and it says "next-line". Then you can ask "what is 'next-line"? and it tells you all the function, including a hyperlink to the actual executable source code that you can inspect, or change in place, or use in your higher level scripts.
It's simultaneously living in the past and way in the future. I wouldn't outright recommend it to anyone trying to choose between VSCode and Atom though... you'll just have to discover it for yourself in 20 years time ;)
Re: Atom 1.36
#38Prediction: I believe eventually MS will kill Atom or let development languish. People will complain that "MS is evil" and "look who they were in the past" and so on, but devs will go where the features are. VS Code is one of the finest examples of open source Done Right™, and while it owes something to Atom and Electron, this is pure open source darwinism.
15-20 commits per week says they just support it and don't implement any major features. Hope I'm not right here.
Looking only at the commit numbers of the `atom/atom` repo is a bit misleading as the Atom source code as the core plugin packages (e.g., the language modes, but also fundamental features like the tree and the fuzzer) are each in their own repo. For instance, the fuzzy-finder repo alone had 15+ commits in the last three weeks.
Re: Atom 1.36
#39I get that it's got a bit more going on, but Atom's startup time is still so much slower than Sublime Text.
I open a file, there's still this "clunky" lag of 2-3 seconds to open. I hope they work on optimizing this at some point.
Re: Atom 1.36
#40Prediction: I believe eventually MS will kill Atom or let development languish. People will complain that "MS is evil" and "look who they were in the past" and so on, but devs will go where the features are. VS Code is one of the finest examples of open source Done Right™, and while it owes something to Atom and Electron, this is pure open source darwinism.
Can anyone who has stayed with Atom after evaluating VSCode comment on why to stay with Atom? I switched to VSCode and would never consider going back to Atom at this point. Since the GitHub acquisition, it makes no sense for MS to maintain both and I agree 100% with the parent comment that this will be killed soon.
Tree Sitter. Being able to do Alt+Up/Down and have syntax blocks selected with such a confidence has really changed the way I write code.