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

231–240 of 880 posts

Re: Sunsetting Atom

#231

Post by dingleberry420 »

tomca32 wrote: post #146
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 switch back and forth between IntelliJ products and VSCode. As a pure editor I prefer VSCode. It's fast and has a great plugin ecosystem. Another great feature is that it's config is just a JSON file that I can put into git and push it to my dotfiles repo making it easy to share config on all of my machines. However, there's just some functionality in IntelliJ that I miss in VSCode like running tests. Of course the…

I'm cautiously optimistic for https://www.jetbrains.com/fleet/

Re: Sunsetting Atom

#232

Post by IncRnd »

edgyquant wrote: post #48
tediousdemise wrote: post #37

Earlier quoted context omitted.

When this inevitably happens to VSCode, I'm sure we'll all flock to Sublime Text in droves (or some hip new editor on the block). Contingency planning for this could be a small but wise time investment for dependent teams. VSCode could very well go the way of the Do... Docker.

Why would this happen to VsCode? VSCode is a proprietary form of Atom is not? It’s hugely successful Microsoft would never do such a thing.

The codebases of VS Code and Atom are unrelated to each other.

Re: Sunsetting Atom

#233

Post by tonymet »

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.

the code is only one of many artifacts within a project . you have multiple support channels for bugs and features, builds, distribution , monitoring / ops (crash and perf reports), developer apis and a dozen more – each requiring time, attention, people and effort .

fork the code and start a new project with resources to take care of those and many other artifacts if you are so inclined . you have the license to do so

Re: Sunsetting Atom

#234

Post by toyg »

vdnkh wrote: post #190
skohan wrote: post #165

Earlier quoted context omitted.

Electron is both an amazing enabling technology, and also an artifact of the sad state of affairs for computing platforms. One could imagine a world where strong standards have been established which would allow you to easily deploy lean native applications across a wide variety of platforms. Instead we ended up in this bizzare world where if you want to maintain a desktop GUI app, you either need a large team to sup…

> One could imagine a world where strong standards have been established w And yet this didn't happen and Electron did. The "free market" of FOSS development settled on Electron as the winner for cross-platform development.

It wasn't FOSS that settled on Electron - it was businesses and corporations.

Decisions were taken with an eye to balance sheets and P&L reports; Electron remains the cheapest option of them all, because the supply of moderately-skilled HTML/JS labor is naturally larger than for any other language - all thanks to choices the Netscape Corporation made in 1995, when they needed interactivity in their product and they needed it quick.

Re: Sunsetting Atom

#235

Post by joshstrange »

dingleberry420 wrote: post #231
tomca32 wrote: post #146

Earlier quoted context omitted.

I switch back and forth between IntelliJ products and VSCode. As a pure editor I prefer VSCode. It's fast and has a great plugin ecosystem. Another great feature is that it's config is just a JSON file that I can put into git and push it to my dotfiles repo making it easy to share config on all of my machines. However, there's just some functionality in IntelliJ that I miss in VSCode like running tests. Of course the…

I'm cautiously optimistic for https://www.jetbrains.com/fleet/

I just got access to this the other day and I'm excited to try it out!

Re: Sunsetting Atom

#236

Post by dingleberry420 »

joshstrange wrote: post #151
datalopers wrote: post #83

Earlier quoted context omitted.

https://code.visualstudio.com/docs/remote/remote-overview far better and faster than sftp

I looked into that plugin but we don't run any special daemon/server for editing on our servers (nor do we want to).

Maybe don't edit on a server. Have you heard of git?

Re: Sunsetting Atom

#237

Post by jbiason »

tinco wrote: post #98
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?

The Vim plugin in VSCode is the thing that drives me out of VSCode, to be honest.

I have to say that I built so much muscle memory in those years that it is kinda hard to realized I'm not using Vim, and there is always something not-quite-like-vim in VSCode-vim that usually gets in my way.

(To be honest, the only editor that I found that is really close to Vim without being a Vim-thing was GNOME Builder.)

Re: Sunsetting Atom

#238

Post by jlkuester7 »

frostwarrior wrote: post #194
mumblemumble wrote: post #47

Earlier quoted context omitted.

The code isn't being sunsetted, and anyone who wants to take it and keep working on it is free to do so. But winding down the project is still a major event, and I think that it is appropriate to call that sunsetting. The existing project organization will go away. The team will presumably dissolve, with any people being paid to work on it going on to other things. I've seen this happen enough times to know that it i…

I agree. Correct me if I'm wrong, but most projects started by some form of organization end up being dead after handing them off to the community. That is, unless they make their code from the ground up to be as most readable and modular as possible. I remember many projects made by Sun Microsystems that just died when Oracle took over, even if the code is still there.

The history of Zulip is one of my favorite counter-examples to this trend. They have seen great growth and success since spinning off from Dropbox!

https://zulip.com/history/

Re: Sunsetting Atom

#239

Post by torstenvl »

jacobmischka wrote: post #71
jonathaneunice wrote: post #27

I like Atom and use it occasionally. But I use VS Code day-in and day-out. The decision makes sense. If VS Code were not exceptionally good, Atom might have had more of an opportunity. But "yet another good option" is not enough to drive investment, sustain a community, and spin an ecosystem.

Atom predated VS Code and was the impetus for Electron, which VS Code uses. You may know this, but this comment makes it seem like they tried and didn't have an opportunity. They literally invented what the majority of new "desktop" apps uses to render UIs, they just couldn't compete with Microsoft (before they were bought out, after which of course Microsoft wasn't going to invest seriously in it). Edit: Fixed typo…

impotence means powerlessness or inability; the state of lacking potency. It's usually used to refer politely to erectile dysfunction.

Perhaps you meant impetus?

https://www.merriam-webster.com/dictionary/impetus

Re: Sunsetting Atom

#240

Post by forgetfulness »

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…

It's trite to say "the best tool for the job", but language support can vary drastically from one editor platform to another.

So I end up using IDEA if I'm working with Scala and Java at a job, Emacs if using Clojure, vim for those tasks that are kind of like using sed and awk but not quite, and for everything else, like Terraform, Python, shell, SQL, there's VS Code.

Post reply on HN