Live data from Hacker News

Atom 1.36

blog.atom.io

11–20 of 75 posts

Re: Atom 1.36

#11

Prediction: If VS Code is the general do-it-all editor, Atom will become the GitHub editor. Atom is quickly ramping up feature integration with GitHub — seen here with integrating review comments inline with the code and the deep GitHub PR integration in general. GitHub and Atom have a very linked future, with GitHub planning to become more involved with the actual code-writing process. Atom will be the conduit thoug…

I think you forgot who owns GitHub.

Re: Atom 1.36

#12
post #5

Earlier quoted context omitted.

There's been previous discussion over this: https://news.ycombinator.com/item?id=18507817 Take what you will from it. I'm not sure they will kill it, but I don't know why they need to maintain two editors either, then again they already maintain Visual Studio as well. I think it would be nice to see how both teams push their editors, but I feel like over the long haul it will be some VIM vs Neovim type of this. Addit…

My guess is that if anything, they'd turn Atom over to an external body to maintain and let it sink/swim on its own. Currently they seem to be fine with having both, which is cool. Maybe it is to have two separate teams work on different ideas and see which ones work and mainline it into Visual Studio Code? Not sure. I wish Visual Studio Code replaced Visual Studio, but unfortunately, it still holds value if working…

Until vscode and omnisharp support design time builds of msbuild projects, visual studio proper isn't going anywhere. Vscode cannot support anything beyond the happy path of csproj files which means I will always have to dip back into visual studio

Re: Atom 1.36

#13

Prediction: If VS Code is the general do-it-all editor, Atom will become the GitHub editor. Atom is quickly ramping up feature integration with GitHub — seen here with integrating review comments inline with the code and the deep GitHub PR integration in general. GitHub and Atom have a very linked future, with GitHub planning to become more involved with the actual code-writing process. Atom will be the conduit thoug…

fyi, the GitHub PR extension[1] for VS Code has review comments in the editor.

[1] https://marketplace.visualstudio.com/itemdetails?itemName=Gi...

Re: Atom 1.36

#15
>The fuzzy finder’s project crawling performance has been improved dramatically by switching to a ripgrep-powered backend. This is most noticeable in projects with large numbers of files - for example, we measured a 14x speed boost in a project with 270K files.

Another leaf out of VS Code's book?

Re: Atom 1.36

#16
post #8

Prediction: 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.

Atom's user interface feels more ergonomic. Atom can show panels on the left and right at the same time, so you can set it up to have the file explorer on the left, and Git on the right, enabling you to work without having to switch between views. The small buttons for quickly folding panels are also a nice touch.

https://github.com/Microsoft/vscode/issues/26777

Re: Atom 1.36

#17
post #8

Prediction: 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.

I, for one, couldn't get used to VS Code look and feel for some reason. I mostly do Sublime Text, but I combined it with Atom a lot in the past. So yeah, not about features or anything.

Re: Atom 1.36

#18
post #8

Prediction: 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.

I personally never liked VSCode's UI. That's 100% subjective, I'm not claiming Atom's UI is better, I just like it a lot and it was kind of a “love at first sight moment”, and VSCode just didn't gave me that feeling.

Also, I'm using a ton of Atom plugin that didn't exist on VSCode at the time I tried (this may have changed, but since I disliked the UI, I'm not going to try VSCode again).

Re: Atom 1.36

#19
post #8

Prediction: 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.

I don't use Atom, but one feature it has that I wish VSCode has is "atomic tabstops". It means if you are forced to work against your will on code that inexplicably uses spaces for indentation, it will act as if they really used tabs.

Atom is the only editor I've seen that has it unfortunately.

Re: Atom 1.36

#20
post #8

Prediction: 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.

I stayed with Atom for a long while because my main use case at work is editing single text files on remote servers... There's not a great plugin for this in VSCode. Atom makes it easy to quickly open, edit, save, and close over FTP/SFTP.
Post reply on HN