News for hackers. Stuff that matters.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by lalaland1125 on Friday December 09, 2022 @05:30PM (#33927259)
What does Atom offer over alternatives, in particular Visual Studio Code?
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by WorldMaker on Friday December 09, 2022 @06:34PM (#33927942)
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 by brundolf on Friday December 09, 2022 @11:49PM (#33929964)
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 by piskerpan on Saturday December 10, 2022 @04:01AM (#33931138)
Knowing the history of Firefox, XUL extensions and their demise, this feels more of a limitation.

For those who don't know, Firefox couldn't innovate because any change to the UI broke half the extension ecosystem. This is what happens when you give carte blanche to third party developers on your UI: It's great for the short them.

Re:Pulsar: A Community Effort to Revive the Atom Text Editor by cardanome on Saturday December 10, 2022 @07:27AM (#33932011)
I mean it works for both emacs and vim which are even more extensible.

You shouldn't make any UI changes to text editors anyway if you don't plan on pissing off your power users. Never break compatibility.

As for Firefox, well if I could go back to the XUL based UI, I would do so. I don't think the new UI has improved for power users at all it just looks more "modern" which is fashion not progress.

What did Firefox gain from trying to copy Chrome? They are at a negligible market share and are only kept alive by Google money as alibi competition.

So no, that is not a good example. Moving away from XUL extension was not progress for Firefox, it was the beginning of it's decline becoming the rotting corpse of former ideals that it is now.

Re:Pulsar: A Community Effort to Revive the Atom Text Editor by piskerpan on Saturday December 10, 2022 @07:54AM (#33932190)
Sorry I don’t think Firefox lost because of extensions. Nobody cared except us. They lost because on Google advertised the living * out of Chrome. Firefox couldn’t compete regardless, it offered an inferior product out of the box.

Again, HN users are not the majority of internet users, which are counted in the billions.

Re:Pulsar: A Community Effort to Revive the Atom Text Editor by sporedro on Saturday December 10, 2022 @01:49AM (#33930549)
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 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 by WorldMaker on Saturday December 10, 2022 @06:21AM (#33931685)
> 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?

The obvious short answer here is: it obviously didn't work out for Atom. It wasn't able to compete with VS Code in the general marketplace, many people who tried to use Atom thought it was slow and buggy (there are examples in other comments near here, such as dueling tooltips plugins), and then eventually GitHub and Microsoft decided to pool all their official resources into VS Code and sunset Atom.

Pulsar linked here is an attempt to preserve what's left of Atom's open source community and I wish them luck, but they are maybe going to need a lot of it with competition like VS Code. Though admittedly Eclipse is an interesting comparison here because Eclipse still lives on, after several times where people assumed Eclipse was over with and the competition clearly winning. Some big companies still use Eclipse for all sorts of reasons.

Re:Pulsar: A Community Effort to Revive the Atom Text Editor by petre on Saturday December 10, 2022 @01:55AM (#33930580)
It's working out fine and doesn't have all the visual annoyances and wheel scrolling issues that CS Code has. I use it since version 1.1. I tried VS Codium this week but reverted back to Atom after reading about the RCE and not being impressed with it. I also want an editor, not an IDE, no Git integration as I don't use Git. And yes, it is slower compared to VS Code. Next I'm going to give Emacs a shot.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by nsonha on Saturday December 10, 2022 @05:01AM (#33931375)
it's technically true that VSCode is less customizable but honestly who cares? Both of these editors are so minimal in their design that UI customization doesn't mean much.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by MatthiasPortzel on Saturday December 10, 2022 @01:17AM (#33930402)
I really miss Atom. I'll enumerate some items here, since you asked, but all of them really just boil down to personal preference:

* 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 by dehrmann on Saturday December 10, 2022 @02:42AM (#33930792)
> Nostalgia: Atom was the first text editor I used, and so it has a certain friendliness than other editors can't match.

Can't say I felt this way about qbasic.

Re:Pulsar: A Community Effort to Revive the Atom Text Editor by rzzzt on Saturday December 10, 2022 @03:53AM (#33931101)
Maybe QB64 will change your mind: https://qb64.com/
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by fathyb on Saturday December 10, 2022 @05:51AM (#33931565)
The QBjs demo is great, looks like a retro ShaderToy.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by rd07 on Saturday December 10, 2022 @10:41AM (#33933518)
I think we have the same preference regarding text editor. I also prefer Atom UI compared to VSCode UI. And even if I can customize it to look the same as Atom, it will never feel the same.

My only complaint with Atom is about performance. A fresh install of Atom feels normal fast at first, but as I add more plugins, it gradually feels slower. VSCode is better in this regard. Nowadays I mainly use Sublime Text, which is faster than VSCode. I also keep an eye on Lite-XL, which has the potential to be as fast as Sublime Text with a smaller memory footprint.

Re:Pulsar: A Community Effort to Revive the Atom Text Editor by satvikpendem on Saturday December 10, 2022 @12:04PM (#33934249)
If you like Lapce, try Helix.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by onionisafruit on Friday December 09, 2022 @05:58PM (#33927560)
It’s open source.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by satvikpendem on Friday December 09, 2022 @06:00PM (#33927580)
VSCodium works fine for me too.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by zelphirkalt on Saturday December 10, 2022 @08:14AM (#33932325)
Unfortunately many VS Code users are uninformed and instead of using VS Codium by default (reproducible build, getting rid of telemetry), they put the cart before the horse and only know about VS Code, using it as the default choice. I have a hunch, that this is as intended or at least, that MS enjoys it being like that.

Fair move would be to put a well visible message into VS Code or their download pages, which informs the user: "If you need to check the build, you probably want VS Codium instead." -- Of course they are not obliged to do that, but meanwhile they are collecting telemetry to no end, from users, who are not informed about their main workhorse of their job. It does not seem right to me.

In general we need more awareness of telemetry, especially from companies like MS. Maybe at some point they will ship some telemetry update which the user "only needs to quickly confirm", before they can hack away and which opts into sharing code with their Copilot thingy. Before you know it, your solutions to problems are shared with other people, who will get a copy of your copy inserted. Lots of scenarios how this could go wrong, even if accidentally.

Re:Pulsar: A Community Effort to Revive the Atom Text Editor by satvikpendem on Saturday December 10, 2022 @04:20PM (#33936915)
Companies generally do use telemetry, and for good reason. If something breaks or crashes, it's useful to know where and what happened. I use telemetry too with my products because it really does help me figure out where the user is getting stuck. That some people, usually a very small minority, don't like it is of no concern to me, they can decide to block it or strip it away like with VSCodium.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by Pufferbo on Saturday December 10, 2022 @01:24AM (#33930439)
I want to try VSCodium so much but the fact they use self signed certs leaves a bad taste in my mouth. I know it’s probably a whole lot of nothing, but if I install it on my work computer and something happens because of it I would be in a massive pickle.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by mdaniel on Saturday December 10, 2022 @01:24PM (#33935174)
I don't know if this falls into the "can't be bothered" category, but it's not horrific to build it by yourself, side-stepping whatever self-signed cert woes you're talking about
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by elashri on Friday December 16, 2022 @12:19PM (#34017263)
Is there a problem with git clone the repo and then build it locally? It doesn't take much time.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by bmitc on Saturday December 10, 2022 @12:16AM (#33930113)
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

Re:Pulsar: A Community Effort to Revive the Atom Text Editor by pedro2 on Saturday December 10, 2022 @05:32AM (#33931492)
VSCode is like Chrome: based on opensource code -- not opensource in its entirety.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by bmitc on Saturday December 10, 2022 @10:47PM (#33939864)
Even if one feels that way, in what way does that matter or serve as an advantage?
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by ParetoOptimal on Saturday December 10, 2022 @02:26AM (#33930725)
Atom doesn't have a corporation trying to slowly and quietly strangle the open source python language server to gain market share for their proprietary one.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by apendleton on Saturday December 10, 2022 @03:23AM (#33930969)
Atom and VS Code are literally owned by the same corporation, though, since Microsoft bought GitHub.
Re:Pulsar: A Community Effort to Revive the Atom Text Editor by pgeorgi on Saturday December 10, 2022 @03:39AM (#33931042)
The difference is that Atom is spun down by the owner, so this fork doesn't compete against the corp's version.