PDE: A different take on editing code

The advantage of (Neo)vim is that it lets you create a PDE (personalized development environment) [1] where you can customize every little detail to your liking easily [2] and as a result program and navigate at the speed of thought. It takes some effort and likely 20-30 plugins, but you get to learn a lot and IMO become a better programmer as a (unintended?) side effect. For me it's part of the continuous improvement to understand your tools. Last but not least it's just so much joy when you can envision a certain feature (e.g. I wanted to have a function header visible in the first line of editor even when the top of the function has scrolled off the screen) and either find a plugin or program it yourself. This is exactly the kind of primal joy that initially made me pursue the career of software engineer. [1] The concept of PDE is explained in this video: [this video] [2] Easily is relative. IMO each little customization is quick, but you'll end up customizing hundreds of things over time.

I think it's worth it, if you are a tinkerer and if you look at that kind of software as a "Personal Development Environment" a phrase I first heard in this video[1]. So, yeah the focus is on creating software that is tailored to your requirements. If your requirements are that someone else has to be able to use it, because you do a lot of pair programming, then that's something to consider. I've tried a lot of editors over the years... Currently I'm using neovim. It's been pretty nice--after some major adjustments. I like altering my configs and changing what's not working for me. Would I use it exclusively? No, but it's a nice tool to have in my toolbox. And with some effort it also can look very pretty. [1]: [this video]

Well, I'd rather call it a PDE (Personal Development Environment)[0]. A term coined in the Neovim community that is pretty apt for Emacs too. Emacs can be pretty minimalist or maximalist depending on your preference, and it can be configured to have IDE-like features, though presented in a different way sometimes. Honestly, the big barrier to entry for Emacs is finding the time to configure it to your liking. The best way is to use it along with your IDE and existing tooling, slowly integrating Emacs into your workflow piece by piece and tinkering with it when you have a bit of time but always with a goal in mind i.e. window (pane in modern vernacular) management, showing symbol documentation in a hoverbox, adding spell checking to comments or inline git blame. And sure, there are lots of bits that you need to get used to at first, how copy and paste works out of the box without CUA-mode for one, but they're that big of a deal after a short while as some people make them out to be. I'll say this though, Emacs is like tiling window management, you either love it and extol its virtues everywhere or you look at its proponents like aliens from another galaxy. [0]: [this video]