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

Sunsetting Atom

github.blog

Post reply on HN
Print view View original

91–100 of 880 posts

Re: Sunsetting Atom

#91

Post by travisgriggs »

Doctor_Fegg wrote: post #7

“Sunsetting” an open source project seems… unfitting? Hand it off to the community, look for new maintainers, donate it to the Apache Retirement Home for Veteran Projects, sure. But saying that you’ve decided to “sunset” or “archive” it, telling users to plan for their migration, seems counter to the notion that open source software forms part of a commons - something that Github, of all companies, should understand.

I actually prefer what they're doing. Consider most open source projects. Our involvement with them goes something like:

1. I need feature X

2. I find library WeLoveX

3. Is WeLoveX a good investment for my larger product?

4. Ambiguity happens here

The ambiguity happens because I have one prominent indicator: release activity. If it's changing lots, does that mean it's active and a solid foundation? Or does it mean it's actually probably not quite ready for prime time yet and hasn't found stability? On the flip, if there's very little release activity, does that mean it's dead, the developers have moved on and maybe there's something better out there? Or does it mean it just does its job really really well and doesn't need a constant stream of tweaks?

It's nice to have a general statement of disposition towards the product by the original authors.

Re: Sunsetting Atom

#93

Post by ketzo »

faizshah wrote: post #51
jstx1 wrote: 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.

Did my first ever paid programming work in Brackets, helping some friends build a Wordpress blog. Good times.

Re: Sunsetting Atom

#94

Post by vchuravy »

babypuncher wrote: post #59
civilized wrote: post #29

Earlier quoted context omitted.

Atom was developed before the acquisition. Which brings us to the second proud tradition of the tech titans, acquiring companies to end the products the acquirer doesn't like.

Does Microsoft not "like" Atom, or has its market share dwindled to the point that it is no longer worth maintaining?

If you look at the contribution activity it dropped off after acquisition of GitHub by Microsoft and it seems that development was redirected to VSCode.

The writing was on the wall for a long while now, and was one of the reasons why the JuliaCommunity stopped advocating Juno/Atom as a platform and instead switched to VSCode

Re: Sunsetting Atom

#95

Post by aordano »

Atreiden wrote: post #38

Called this ~4 years ago when they were acquired by M$. But it's still really sad to see. I use it because it was trivial to CSS style it to match my Desktop. It's comfortable to me in a way that other editors thus far have not been. Are there other editors with this level of customizability? I know VSCode and Sublime support theming but from what I can tell it involves installing pre-packaged themes.

there is an extension that lets you set arbitrary css in VSCode, albeit it's a bit cumbersome to use.

https://marketplace.visualstudio.com/items?itemName=be5invis...

Re: Sunsetting Atom

#96

Post by trinsic2 »

acwan93 wrote: post #39
mproud wrote: post #4

What recommendations do you all have for alternatives?

I really wanted to use Coda (now Nova [1]) from Panic, but I kept coming back to VSCode. VSCode seems to be the path of least resistance. I think I’ll try it again after seeing the news about Atom. [1]: https://nova.app/

Isn't this for MacOS only? Sorry, [I just left Windows](https://www.scottrlarson.com/publications/publication-transi...) recently for it's anti-customer changes in Windows 11, Apple is way worse than Microsoft regarding its anti-choice position on all its products.

Re: Sunsetting Atom

#98

Post by tinco »

wly_cdgr wrote: post #73

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

I use VSCode because its Vim plugin is better than that of Sublime. If/when Sublime has caught up, I'd happily go back to it for that sweet performance and uncluttered UI. So am I a normie, a corpo-hipster or a furry wizard?

Re: Sunsetting Atom

#99

Post by bckr »

joshstrange wrote: post #56

I know a lot of people love vscode but are there any people who have tried something like IDEA/WebStorm/PHPStorm/etc that then went back to vscode? I had to help a developer setup deploys to a dev server from vscode the other day and I wanted to pull my hair out. I'll admit it's at least in part due to not using vscode myself but I was a heavy Sublime Text user which is very similar to vscode when it comes to how you…

> setup deploys to a dev server from vscode

What does this mean? Setting it up so you can deploy through GUI?

Re: Sunsetting Atom

#100

Post by hombre_fatal »

joshstrange wrote: post #56

I know a lot of people love vscode but are there any people who have tried something like IDEA/WebStorm/PHPStorm/etc that then went back to vscode? I had to help a developer setup deploys to a dev server from vscode the other day and I wanted to pull my hair out. I'll admit it's at least in part due to not using vscode myself but I was a heavy Sublime Text user which is very similar to vscode when it comes to how you…

> I know a lot of people love vscode but are there any people who have tried something like IDEA/WebStorm/PHPStorm/etc that then went back to vscode?

Everyone who uses VSCode has surely used an IDE before. It just turns out they aren’t better in every way, and possibly not in the ways that matter.

VSCode plug-ins just have more eyeballs and work done on them for various ecosystems, for example. Especially for less common languages and features.

Post reply on HN