Pulsar: A Community Effort to Revive the Atom Text Editor
11–20 of 89 posts
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#12This is great news. Looking forward to this and lapse.dev since VS Code is really slow and ugly.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#13Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#14What does Atom offer over alternatives, in particular Visual Studio Code?
* Atom was hackable from the ground-up. I use a VS Code extension called Customize UI that allows me to write custom CSS, but Atom supported custom CSS as a first-class feature.
* Nostalgia: Atom was the first text editor I used, and so it has a certain friendliness than other editors can't match.
* Atom One Dark and Atom One Light are the best pair of dark and light code themes I've ever used. I use ports of these themes in other editors, but you can't beat them in their original context.
* I don't love VS Code's whole design language (straight-thin lines and sharp angles, except for some corners, which are curved). But that's probably very much tinged by my other points.
* Atom, of course, matched VS Code on language support and plugin support at one point. You could find extensions for just about any language. (Something that wasn't ever true for Sublime or Textmate, for example.)
* Being truly open source (I would describe VS Code as more open-core).
* Not being the most popular editor. I love supporting the underdog in my software choices as a way of encouraging innovation and variety in the ecosystem. So if Microsoft makes VS Code so good that no editor can complete with it, I would use VS Code (VSCodium), but I would not be happy about it.
All that said; Atom's dead. Since the Microsoft acquisition, development has stalled. Atom's gotten increasingly buggy and many many packages were abandoned. As I understand it, there are architectural issues that make it very difficult to fork or maintain. Atom is upstream of Electron (not downstream of it), for example, since Electron was originally extracted from Atom's code, so that makes integrating Electron updates difficult. CoffeeScript (which a lot of Atom is written in) never really caught on. You have a bunch of existing packages, but as mentioned, most of them are unmaintained, so you'd have to rewrite them and it's not clear which ones. Tree-sitter was originally developed for use with Atom, but after most popular programming languages had packages, and they never got rewritten with tree-sitter.
I've been following Lapce. I think they're doing interesting work. Right now the editor is too buggy for me to consider as a daily driver. I've been using Emacs for the past couple of weeks. It exceeds Atom's hackability, but there are still a lot of rough edges in the UI, for someone used to GUI editors.
I didn't mean to write this much. Atom is obviously something that I care about and that I've been thinking about ever since the acquisition.
TL;DR: Some people don't like VS Code, as a personal preference, and other options for GUI text editors are good.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#15Earlier quoted context omitted.
It’s open source.
VSCodium works fine for me too.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#16What does Atom offer over alternatives, in particular Visual Studio Code?
Atom used a very different extension model than Visual Studio Code. Atom was designed more in the "everything is an extension" mold and even "core" functionality could be replaced or extended in ways that VS Code likely will never allow. On the one hand greater potential power, on the other hand more potential responsibility (Atom did have some notorious performance issues with comparison to VS Code and "everything i…
I guess my question is, is how did this work out for it? I never gave atom a try, but did it feel like everything sorta worked together? Or was it more of a eclipse feeling where every package feels like it’s own separate object?
Vscode is a decent out of box experience but it’s custom ability is rather limited imo. Would love to give atom a try if this community version succeeds at all.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#17How much money has MS spent on optimizing electron in VS Code again?
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#18Earlier quoted context omitted.
Atom used a very different extension model than Visual Studio Code. Atom was designed more in the "everything is an extension" mold and even "core" functionality could be replaced or extended in ways that VS Code likely will never allow. On the one hand greater potential power, on the other hand more potential responsibility (Atom did have some notorious performance issues with comparison to VS Code and "everything i…
I don’t know how to phrase this and it might be a bit of a ramble, but your reply is something I’ve been thinking about with atom. I personally hated eclipse, due to it feeling constantly like everything was it’s own package and not really working together, but recently was trying out emacs, and was quite impressed. Atoms philosophy sorta reminds me of the two where it’s “everything is an extension”. I guess my quest…
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#19I loved using Atom, and I like that there’s a community trying to keep it going. However, I think there’s value in trying to push the platform forward, too; maybe rethinking the extension model to maximize stability/performance would allow Pulsar to start stealing market share back from VS Code.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#20Earlier quoted context omitted.
It’s open source.
What does that offer to it as an editor? And Visual Studio Code is open source as well. https://github.com/microsoft/vscode/wiki/How-to-Contribute