Pulsar: A Community Effort to Revive the Atom Text Editor
pulsar-edit.dev
Pulsar: A Community Effort to Revive the Atom Text Editor
1–10 of 89 posts
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#2What does Atom offer over alternatives, in particular Visual Studio Code?
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#3What does Atom offer over alternatives, in particular Visual Studio Code?
It’s open source.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#4Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#5What 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 is an extension" can be hard to performance adjust at scale).
Given this Pulsar page makes a big deal about trying to preserve the package source (list of extensions), the different extension model and history/long-tail of community extensions was probably important to them.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#6Post photos of it
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#7What 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…
Yeah- its open extensions model was a neat idea, but in practice it made it slow, buggy, and complicated to configure (extensions would have dependencies on other extensions, etc). I really tried to stick with it, but as soon as I tried VSCode I sighed a breath of relief and knew I couldn't go back
I think the most egregious example was having two competing IDE hints extensions (not the content, just the GUI). They could both be enabled and they could fight each other or overlay each other if they were. Some language extensions then depended on one, and some depended on the other. It was kind of a mess.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#8You could borrow some good ideas from Monaco Editor. If some application can run on a web page, then it's a completely different level for a “cross-platform” badge.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#9For some context, it was announced some months ago that atom would be sunsetted.
Re: Pulsar: A Community Effort to Revive the Atom Text Editor
#10What does Atom offer over alternatives, in particular Visual Studio Code?
It’s open source.
What does that offer to it as an editor? And Visual Studio Code is open source as well.