2 ms·
+1 I've explored Atom when it was the hot thing, and more recently, an IDE called Lapce, which is built in Rust and doesn't use Electron. They've been great, b
by princevegeta89 1y ago
+1 I've explored Atom when it was the hot thing, and more recently, an IDE called Lapce, which is built in Rust and doesn't use Electron.
They've been great, but the lack of an ecosystem stares glaringly right at your face. I don't like Electron apps but VSCode gets the job done.
I have my entire set of plugins and things installed here and now the productivity that I get off this setup even exceeded my long-loved Jetbrains IDEs. I hope that will be temporary though, seriously.
The only thing that I strictly dislike about VSCode is the number of high quality themes available - and there are not that many.
Recently stumbled upon VSCodium which is a clean VSCode fork that can work with any VSCode plugin, but I am yet to try it out.
- Night_Thastus 1y agoI miss Atom. I loved it. I loved all the crazy plugins people would make to do all sorts of things. It was a fun time. These days I'm stuck on QTCreator most of the time. It's OK for core editing functionality but there's a lot that I miss, and some things like the generic Language Server support just aren't fleshed out much. I'm tempted to use another editor whenever I'm not working on UI files but it adds some friction.
- xrisk 1y agoWas atom functionally ever any different from vscode today?
- princevegeta89 1y agoI only remember Atom being painfully slow. It was using Electron too btw.
- CitrusFruits 1y agoAt the time it was actually called "atom shell" iirc. Electron came from Atom.
- debugnik 1y ago> VSCode fork that can work with any VSCode plugin Technically yes, but if you care about legally, you can't use extensions from Microsoft's marketplace, which excludes Microsoft's own closed extensions such as WSL/SSH/devcontainer remoting and Pylance. It ships with Open VSX instead.