Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Atom 1.36

blog.atom.io

Post reply on HN
Print view View original

41–50 of 75 posts

Re: Atom 1.36

#41

Post by mythz »

wakeywakeywakey wrote: post #2

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.

> VS Code is one of the finest examples of open source Done Right™

It's easy to do OSS right when your a major cloud OSS vendor who are able to use your billions of profits from hosting OSS to fund a 30+ strong dev team in creating a free "OSS" product.

If that's the definition of doing OSS right, then the only sustainable "free" products that will be done right will come from multi-billion dollar cloud vendors. I do love VS Code tho, just not a fan of seeing most of the generated wealth from OSS being collected by the major cloud vendors, this trend is going to hurt the diversity of the OSS ecosystem as we know it.

Irrespective of the funding model that made it possible, I will say the VS Code team is doing a fantastic work iteratively shipping new features with each release at a super high velocity.

IMO it's a poster child for why most future Desktop Apps will be built using a Hybrid or WebView dev model like Electron where its productivity is unmatched.

Re: Atom 1.36

#42

Post by si1entstill »

citrusx wrote: post #25
xrd wrote: post #8

Earlier 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.

Two things about VSC, in comparison to Atom, that are Done Wrong: 1) Extensibility. There's like a dozen times more friction involved in creating a plugin for VSC than for Atom. Atom was built to be as easy to change as a web app. They also created apm, which is sort of a clone of npm, for installing plugins. 2) Configurability. I can set personal keyboard shortcuts very easily, and in a way that's easily transportab…

It looks to me that keyboard configuration is pretty similar:

https://flight-manual.atom.io/using-atom/sections/basic-cust... https://code.visualstudio.com/docs/getstarted/keybindings#_k...

With VSCode, I haven't had any trouble moving my keybindings file between installations, even between my Windows and Mac environments (I do the same with my theme, and it works great as well).

What functional difference between the configuration styles did you run in to?

Re: Atom 1.36

#43

Post by [deleted] »

equasar wrote: post #36
mdhughes wrote: post #33

Earlier quoted context omitted.

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.

[deleted]

Re: Atom 1.36

#44

Post by mises »

citrusx wrote: post #25
xrd wrote: post #8

Earlier 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.

Two things about VSC, in comparison to Atom, that are Done Wrong: 1) Extensibility. There's like a dozen times more friction involved in creating a plugin for VSC than for Atom. Atom was built to be as easy to change as a web app. They also created apm, which is sort of a clone of npm, for installing plugins. 2) Configurability. I can set personal keyboard shortcuts very easily, and in a way that's easily transportab…

> there's a reason that every editor takes a swing at a "vim mode". People get comfortable with the aesthetics of their tools.

To be fair, vim is radically different in terms of navigation, keybindings, capability, etc. than your average gui-based text editor. I am not saying that your point is wrong, but vim is sort of an extreme example of a. the difference between vim vs. other editors, and b. the zeal with which vim users tend to cling to it (as a vim user).

Re: Atom 1.36

#46

Post by GordonS »

taylorlapeyre wrote: post #10

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…

VS Code has had excellent git integration for a long time, as well as GitHub-specific integrations through an extension.

Atom may have started the move towards lightweight (relatively) IDEs, but VS Code is undoubtedly the more popular one. Honestly, when I saw this post on HN I was quite surprised to see that Atom is still actively developed - if there's anyone reading this that prefers Atom over VS Code, I'd really like to find out why?

Re: Atom 1.36

#47

Post by bwha »

xrd wrote: post #8
wakeywakeywakey wrote: post #2

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 was with Atom for years, switched to VS Code and feel in love (save for the find and replace as cited above, I still felt/feel Atom's is better than VS Code's) and stuck with it (VS Code) for months.

The thing that made me switch back was that there was some combination of plugins I was using in VS Code (I think it was the VIM plugin and something else maybe) started freezing periodically and the whole editor would become unresponsive and I'd have to restart. After that became normal I decided to switch back.

In the end I preferred to spend my time coding rather than hunt down the problem.

Also Atom's VIM plugin is strictly better for my use case. The highlighting effect to show you what you just `yw` for example is great!

Re: Atom 1.36

#48

Post by galfarragem »

GordonS wrote: post #46
taylorlapeyre wrote: post #10

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…

VS Code has had excellent git integration for a long time, as well as GitHub-specific integrations through an extension. Atom may have started the move towards lightweight (relatively) IDEs, but VS Code is undoubtedly the more popular one. Honestly, when I saw this post on HN I was quite surprised to see that Atom is still actively developed - if there's anyone reading this that prefers Atom over VS Code, I'd really…

VS Code, like Python, seems to be the second best tool on everything: it looks good but not as much as Atom, it's fast but not like Sublime or Vim, it's a lightweight IDE but not a full IDE.

Re: Atom 1.36

#49

Post by dmnd »

I do a lot of code review, so I'm excited to be able to do that from my editor where all of my other tooling is set up instead of in a web browser. Suggested code changes will be much easier if I write them in a context where I can compile/run them. And no more clicking that "expand" thing 20 times to see something earlier in the file.

Thanks, Atom team!

Re: Atom 1.36

#50

Post by herrvogel- »

yuchi wrote: post #40
xrd wrote: post #8

Earlier 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.

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.

This! Tree Sitter is the only thing I miss in VSCode
Post reply on HN