3 ms·

For me, Emacs was a natural progression from VS Code, which was a natural progression from Gedit. Similarly, at roughly the same time, I "progressed" from Ubunt

For me, Emacs was a natural progression from VS Code, which was a natural progression from Gedit. Similarly, at roughly the same time, I "progressed" from Ubuntu to Gentoo. I want full control over my computing experience. Little things annoy me, and when things annoy me I get distracted. For me, taking the time to configure Emacs exactly the way I want it is a small up-front cost compared to the large ongoing cost of dealing with annoyances. Now, some time later, I've built up a computing environment that blows everything else out of the water, because it's mine (and mine isn't even as good as other people's Emacs configs, I'm a noob). I would never go back to VS Code. Not because I don't like it, but it just doesn't do what Emacs does. Emacs is... what's the word?.. Unified? Hyper-integrated? You can't use your VS Code extensions in other programs, but with EXWM you can use Emacs functionality in all of them (okay, there are exceptions). To use anything but Emacs would mean un-unifying my computing environment, and that's the opposite of what I want.

iLemming 3y ago
> I would never go back to VS Code. Even though I probably will not be using VSCode seriously, I still want to learn it to the point that I understand how things work. At some point, I'm gonna have to work on a diverse team of programmers, it's useful to see everyone's perspective on things to be able to explain your own approach and the workflow. I don't want to sound like an ignorant douche, saying things like: "yeah, but VSCode can't even do X", what if that wouldn't even make sense, because in order to have X, first, there's gotta be a foundational base feature that VSCode simply cannot ever have? You can't describe the universe of infinitely many similar but non-congruent shapes that exists in the realm of hyperbolic geometry if you never cared to learn the Euclidian one. Conversely, there are certain things that Emacs unlikely will have anytime soon, but VSCode maybe was designed to have them from the get-go.

iLemming 3y ago

> I would never go back to VS Code. Even though I probably will not be using VSCode seriously, I still want to learn it to the point that I understand how things work. At some point, I'm gonna have to work on a diverse team of programmers, it's useful to see everyone's perspective on things to be able to explain your own approach and the workflow. I don't want to sound like an ignorant douche, saying things like: "yeah, but VSCode can't even do X", what if that wouldn't even make sense, because in order to have X, first, there's gotta be a foundational base feature that VSCode simply cannot ever have? You can't describe the universe of infinitely many similar but non-congruent shapes that exists in the realm of hyperbolic geometry if you never cared to learn the Euclidian one. Conversely, there are certain things that Emacs unlikely will have anytime soon, but VSCode maybe was designed to have them from the get-go.