Oh this is sad. As a teacher I loved introducing Atom as a first text editor as out of the box it did nothing but look nice. Then I could gradually add plugins everytime a student said something was annoying. Great for teaching principles before tools/shortcuts. Something which I think IDEs do far too often imo.
Sunsetting Atom
211–220 of 880 posts
Re: Sunsetting Atom
#212Re: Sunsetting Atom
#213I guess this idea of "Sunsetting" a project highlights one of the main differences between Open source and Free Software.
A successful Free Software project rarely gets "Sunset".
Re: Sunsetting Atom
#214I 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 have used both, and use both working daily. If I could get away with doing everything in VSCode, I would. Part of this is how the community treats tools. VSCode is an editor, with some plugin support that lets it work as a bit of an IDE. But these are almost always optional. Code ecosystems and communities built around an IDE tend to only support working in that IDE, so there's typically only one way to do things, good or bad.
Re: Sunsetting Atom
#215Earlier quoted context omitted.
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?
> its Vim plugin is better than that of Sublime I'm pretty sure Sublime has a plugin that uses an actual NeoVim instance to process all inputs with all your configuration. Never tried it, I don't use Sublime. But I can confirm the feature works well in Firefox via FireNvim.
I think this is what vscode does as well. The magic is in how it cooperates with the GUI. All jumps and movements work, as well as search/replace and the hilighting and selections are even the native vscode hilights and selections so it's fluid going from mouse to vim and back. Last time I used Sublime (4+ years ago) there were a bunch of vim commands that didn't work.
Re: Sunsetting Atom
#216I still prefer Atom's UX design over VSCode and I can't explain why. Amazing job on that front! I hope it gets traction with community support.
It feels a little more natural/human. VSCode's default theme looks like Tron. Both are valid, but I can see how Atom's is more "cozy". It also had some fun "squishy" animations that were nice
For the colors at least, there are VSCode themes that will try to mimic it for you
Re: Sunsetting Atom
#217Earlier quoted context omitted.
> 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 co…
> 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. Almost every junior I hire has only used Atom, Sublime or VS Code, especially JavaScript developers. >VSCode plug-ins just have more eyeballs and work done on them for various ecosystems, for example. Especially for less common languages and features. The reason to swi…
> The reason to switch to an IDE from something more flexible like VSCode or Emacs is the amount of time spent keeping the editor working.
An editor will generally not stop working like a car without oil. But, IDEs may stop working due to more complex configurations and disparate use cases.
Re: Sunsetting Atom
#218Really begs the question what Visual Studio Code did right and what Atom did wrong.
The first thing which Visual Studio Code did right was the better performance. The initial reaction to Atom was that it was very promising, but very slow. The second big innovation was the language server protocol.This allowed any language to be supported by VS Code.
Third, for me at least: Remote Extensions. That suite of extensions including SSH WSL, and Container support made things I was already doing frictionless.
Re: Sunsetting Atom
#219“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.
"sunsetting" is better than corp-speak saying "handing it off to community maintenance"
Especially, if there isn't a dedicated community to maintain it.
I'll take honesty over corp-speak any day.
That said we probably only get honesty, because they want us using vscode instead.
Re: Sunsetting Atom
#220Even after they promised they'll keep developing it despite of the acquisition:
https://www.reddit.com/r/AMA/comments/8pc8mf/im_nat_friedman...
Not surprising. When this stuff happens is always lies because you plan for people to forget about stuff as times goes by, which usually happens.