Is atom dead, again?

I’ve been talking about this for ages, finally it happened.
Choosing coffeescript over JS was a bad idea.
Choosing extensiveness VS performance was a bad idea.
Choosing random plugins VS built-in functionality… you get the point.

And oh how the mighty have fallen…

Keep -1’ing me.

2 Likes

I’m still using Atom but if thinks don’t change direction and Atom get updated in the near future I think I’ll give VSCodium a try. At least I’ll not let M$ spy on me.

I use Atom right now it’s not being bad

2 Likes

The main reason why Atom development is fading little by little is because indeed Atom is too similar to Visual Studio Code:

  • Both have the same minimalistic Sublime-like interface with lateral collapsible configurable panels, no buttons’ bars and Settings opening in a new tab.
  • Both have good built-in git support in the form of an attachable panel.
  • Both use the same underlining multi-OS application platform: Electron.
  • Both are open source one-company-driven yet community backed projects hosted on GitHub with big emphasis on third-party extensions and themes with corresponding online marketplaces.
  • Both are now owned by the same company.

In general the philosophy and technical approaches behind these two projects are identical.

I’ve followed the same path that many people here. I used Atom for around 3 years. Until last year 2019 when I moved to VSCode. And it’s a no-return change.

However the reasons for the change weren’t technical. I see tiny differences between the two, having VSCode in my opinion a small lead on things here and there. But this is so simply because Atom development has almost halted (https://github.com/atom/atom/graphs/contributors) and instead VSCode development is on fire (https://github.com/microsoft/vscode/graphs/contributors).

The main reason I switched to VSCode was because everyone around me was using that IDE, the development of it was skyrocketing yet the development for my IDE was slowing down every day. No one wants to use an IDE that, even when it does a great job, feels like is something from the past and will soon have problems derived from this fact.

In a nutshell, there is not much point on developing two projects that are so tightly equal. I think it’s a much better approach to deprecate one of them, Atom, and devote freed resources to carry on the development of one single great product, this time, Visual Studio Code.

1 Like

Really good points. Mostly the 2 links you posted, this is crazy how the development is breaking down while VSCode is still strong.

Hi
It’s not connected with the theme but I’d like to share a freelance job link https://jointohire.com/ where any IT specialist can find some freelance projects. I’ve used it and looks normal. Maybe It will be useful for someone.

I feel the same way, it just feels bad to use something you know it’s slowly dying. I don’t use Atom as my main editor, I use (neo)Vim, but still I do use Atom for some things, particularly on Windows.

The plugins I use are developed by me and have no equivalent on VSCode, so I think that’s a big reason why I don’t swap. Eventually though I might have to just bite the bullet and re-write them.

I guess until I have some major problems though, I’ll continue to use Atom :slight_smile: I like that it has less built-in features than VSCode. I don’t need a terminal, I like using a separate app for that. I don’t need an integrated debugger for my particular use-case (JavaScript, Rails, etc). Atom is simpler by default, I like that.

It does feel like VSCode is more performant though, even with all the bloat, but it’s to be expected with Atom’s halt in development.

Yeah, I remember when I installed VSCode and tried to disable some stuff, first you have to scroll 5 years to find stuff (I know you can just type it in) this is crazy. When I do a clean install of Atom I just go in the settings, click here click there, DONE.

It would be nice if Atom were to survive as a community project.

I Do Not Like Corporate-Driven “Open Source”.

I work some in NetBeans and some in Atom and some in jEdit and some in Spyder.

I have contributed code to NetBeans and jEdit. I’m going to do more work in NetBeans.

If the Free Software movement returned to its roots, we would not be facing this “enclosure of the commons”.

To be fair it looks like that’s the case. While Atom is backed by GitHub, it has very little resources. So as long as it doesn’t die, it seems to be in a decent place.

Also, I started contributing on it, submitted a small PR and will see if I can contribute at least with some low-hanging-fruit patches.

Gotta be the change you want to see :slight_smile:

2 Likes

Angela? I’m also taking a course that uses this editor. We might be taking the same one! And to contribute to the conversation, I think both will stay, for maximum money, maybe if a few more people left, it might actually die… Sadly…

After hanging out in Slack and GitHub for a while, while the development team is small, and not fast-paced, the development seems to be quite active. So unless an unexpected cut comes from GitHub (it doesn’t seem like that at all) I think Atom is quite healthy. It recently got updated to Electron 6!