Live data from Hacker News

Sunsetting Atom

github.blog

111–120 of 880 posts

Re: Sunsetting Atom

#111

Earlier quoted context omitted.

I like brackets but always ends up in VSCode due to extensions.

Brackets in nearing end of life or is already at that point. Adobe announced it a while ago.

https://news.ycombinator.com/item?id=26341931

Just found this. It’s a shame. I donno why but I just liked brackets interface.

Re: Sunsetting Atom

#112
post #43

Earlier quoted context omitted.

VS Code Pro already exists. It's called Visual Studio.

Despite the name, they have basically nothing in common. They don't share a user interface, they don't share plugins, they don't share hotkeys. One of the main complaints many of the C# developers on my team have when they have to touch languages that aren't well supported by Visual Studio is that they don't know how to work VSCode.

I'm well aware of the differences between the two products, since I use both on a daily basis. My answer was a bit flippant, sure, but they are both IDEs developed by Microsoft and Visual Studio is definitely the "Pro" version of the two.

Re: Sunsetting Atom

#115
I held out for a year or so after VSCode was released. It felt scummy how MS had swooped in and tried to hijack this new category of editor that GitHub had invented (this was before they'd been acquired, I believe)

But once I tried VSCode... man, there was no going back. It was infinitely more performant and cohesive. Atom (with IDE-like features installed) felt so sluggish by comparison. I think the main improvement was how opinionated VSCode and its extension APIs were; Atom extensions could have dependencies on each other. I remember you had to install an extension for generic IDE hover-overs and such, before installing the actual language plugin, and then there were competing standards for which generic hover-over framework each language wanted to use. It didn't just complicate the user-experience, I'm convinced this was the reason the editor would get so slow; the APIs were too low-level and all the plugins were fighting with each other instead of going through standard channels.

But, Atom will always have a special place in my heart. It blazed new trails in editor customizability (even if the degree ended up being its downfall, quite a bit of that legacy can still be found in VSCode). It invented the entire concept of web apps as desktop apps, which despite what some here would tell you, I think is a very good and important thing. And it always had such a fun, community feel to it that's been mostly lost with VSCode.

It was time, but I will miss it. I'll close off with the very cute and fun Atom 1.0 announcement video: https://youtu.be/Y7aEiVwBAdk

Re: Sunsetting Atom

#116
post #2

It's what kickstarted Electron which eventually gave us VSCode, Slack, and lots of HN comments about memory usage. It also had the sweetest default theme of any code editor. RIP.

Does anyone remember brackets? I cant remember if brackets or atom came first but I remember switching from sublime to brackets to atom. Good times, I heard DHH is still using TextMate.

[deleted]

Re: Sunsetting Atom

#117
I use Atom for static Markdown blogging only. The reason is I customized Atom for this specific task and nothing more. Atom is mostly an advanced text editor than an IDE. I have Hunspell in both English and french, it detect word similarity and provide auto completion for this, it has some typewriter extension, etc.

I'm reluctant to use VSCode because of M$ pushing for its tooling, but it looks like I will have no choice on the long run.

Is there anyone in the same boat? Which highly configurable text editor can be use for this?

Re: Sunsetting Atom

#118

Atom has been dead for years, this is just the state funeral. The situation now is: * Sublime for the Williamsburg corpo-hipsters * emacs and vim for the wizards and furries * VSCode for all the normies who just want to get on with doing their job and don't feel a need to express their identity or politics through choice of editor * WebStorm for the chads with the monster rigs to run it

So MS owns the default place where code is hosted, and the default tool people use to edit code. Neat.

Re: Sunsetting Atom

#119
Man this is sad... As a markdown/HTMl writer, I used Atom every day... It had great extensions. So It looks like Sublime then.. Any other Editors for a non-coder that has good (Community) extension support like Atom besides Sublime?
Post reply on HN