For those looking for a good substitute, I've switched to Sublime Text and so far I've gotten it to pretty much a near-perfect replica of the original. Kind of surprising to me how much of the Atom UI was built to mimic the Sublime interface. I also tried VSCode, but was never really quite able to get into the interface the same way. For a while I tried customizing the interface with plugins like CustomizeUI, but Mic…
Atom was archived today
51–60 of 614 posts
Re: Atom was archived today
#52Earlier quoted context omitted.
For better, certainly. Electron has in particular been an enormous boon for Linux users, because it's so easy to make cross-platform applications now that even companies who wouldn't have bothered otherwise now have a Linux download. No way that apps like Slack would have a Linux desktop version if it wasn't for Electron.
Or another way to phrase it is that the experience sucks equally on all platforms, so you might as well switch to Linux.
It's the "when you do things right, people won't be sure you've done anything at all" phenomenon. https://www.youtube.com/watch?v=VofkquwmT40&t=29s>
Re: Atom was archived today
#53I had a lot of fun whipping up plug-ins within minutes for Atom! It let me try out ideas very quickly.
emacs may probably let you do this too, and better. The big problem is: You need to know emacs beforehand, which is seriously a lot, and likely bizarre to any modern person. I do, and I will likely never give it up, but I've been at it since the 90s. In my mind, emacs suffers the same problem as TeX/LaTeX. Some parts of it are very antiquated and just don't fit into the modern world anymore. They'd need an overhaul.…
Re: Atom was archived today
#54Moment of silence.
Re: Atom was archived today
#55Sad to see this go. I was an early adopter of Atom, and I wrote two extensions for it, one of which while it was still in beta. The Atom developers made some technology choices that in retrospect were ill-advised, CoffeeScript being the worst of them and splitting everything into dozens of packages a close second. They tried to backpedal on both of these later on, but by that time VSCode, with its far superior engine…
Atom predated the LSP and leaned heavily into customizations with all the plugins running inside the UI thread (more like a traditional web page and 3p scripts). At the time they viewed the extreme customization support as a feature, and there was a thriving ecosystem of folks making plugins. That architecture has a major flaw though. A default install was fast, but a real configuration with all the plugins ended up…
Re: Atom was archived today
#56Damn! It's been a while since I heard about Atom. Sad this is happening!
Re: Atom was archived today
#57I'm a happy user of Atom as my daily driver for basic note taking and scratch pads. Even though it's being sunset, I look forward to using it for years to come. Perhaps it will have a good fork one day, but honestly it works great as-is. Sometimes software reaches a point where it just works, and you appreciate not having a team that wants to change everything.
Re: Atom was archived today
#58I think the Atom editor + Hydrogen plugin for running interactive Python sessions inline with the code is still unmatched by anything available in VS Code. This setup is what I migrated to when I ditched Matlab for the "scientific Python" stack, and I'm still here. Multiple concurrent kernels, the ability to connect any .py file to any running kernel, sharing variables and imports across multple .py files, inline mat…
What’s preventing this from being done in VSCode? Other than it hasn’t yet? I don’t think it ticks every box for you, but have you tried Jupyter Notebooks in VSCode[0]? [0] https://code.visualstudio.com/docs/datascience/jupyter-noteb...
Re: Atom was archived today
#59I resisted switching to VS Code for a long time because I far preferred the UX and design of Atom, but I eventually caved not because of performance gains I wanted in VS Code (honestly I found Atom plenty fast for the work I was doing), but because many Atom extensions were left to rot and slowly broke over time as most maintainers moved to VSCode extensions. Farewell friend, you will be missed.
That's my experience exactly. I still haven't been able to configure VS Code to fully match the experience I want with respect to keybindings and subtle look-and-feel and functionality details.
Aside from the infrequent case of hanging when opening very large files I had no real issues with Atom and could have happily kept using it.
For what it's worth Pulsar (https://pulsar-edit.dev/) appears to be a community-maintained fork of Atom. (For that matter one of the primary Atom creators is working on https://zed.dev/.) But personally I got tired of swimming upstream and just caved to VS Code.
(I am a little tempted to go back to emacs, which was my editor of choice before Atom, but that's ends up being an enormous time-sink for me anyway.)