I work at a place where developers have no problem switching between different OS’es. If you have multiple files then you can choose to omit the file name and git will let you decide on each hunk for each file. I don’t find VS Code to be a good text editor in the sense of a tool to wrangle text: the keyboard shortcuts are rather arbitrary and don’t seem to be logically organised, and it seems not to have learnt much from eg modern text editors like Sublime Text (even Sublime compatibility isn’t as good as the real thing). You’ll know whether it works for you. Quickfix, help, and terminal buffers behave differently, but the vast majority of buffers are just associated with open files. I used Emacs back then because compared to many other editors and IDE it allowed me to work faster, but VSCode despite all its shortcomings has done the very same thing Emacs did for me previously. What I really appreciate on Linux tho is workspace ordering and switching. Other than Richard Stallman, I don’t think I’ve ever heard anyone talk about how their personal values determine what software they will use. Or in the way that it's this mundane tool for the production of money-points that they can then exchange for money. Try them out on magit, you'll see the difference. In that respect everyone who is not a core maintainer is an outsider. I’d love for it to receive a bit of love so it’s a better at wrangling text out-of-the-box, however. Regarding mixed-DPI displays and scaling, I have not had issues with GNOME on Wayland. Are you suggesting that most of the existing Windows SW out there could be developed on Linux and would just run fine on Windows? You don't have to use pyls. Has 3 lanes, and the Dragon, Rift Herald and Baron Nashor bosses. I used WSL1 a little while back. It inevitably seeps into things unrelated to doing the actual work (even performance reviews via 360 feedback). That’s exactly what it felt like in 1991: “eight megabytes and constantly swapping!”. I have run into all the same problems as the parent of this and more, I have tried different desktop environments including Gnome, KDE, Mate, Cinnaman, and XFCE. Sometimes I don't go back -- it's all a matter of taste, really. But as a working developer it’s really worth the effort, if given the option, to invest in learning Linux and developing on it. We model everything in our stack using Terraform. You can perform whatever CLI operations you want in here, and even use the window navigation keys to switch between your editing windows and the CLI window. This shows that convenience or "easiness" is in fact just one of several values, weighted differently in different contexts. > Maintaining Emacs on windows takes considerable effort. In VSCode, you can selectively stage lines in files too, just select them in the diff, right-click, "stage selected" - I love being able to do that so easily within such a nice UI. On windows, there's no choice. I removed all the bloatware on the laptop and multiple times things are re-enabled after an update. What I often hear is more about Emacs on windows having performance issues in some areas, magit comes to mind. Not great for your career IMO unless you plan on making a quick exit from the dev side of things. True, but those are still exotic edge-cases. But, yeah, that muscle memory is a loss. When I decide to use software, move to a new location, purchase cereal at the grocery store, buy music, and a variety of other daily activities, these are choices I make based on my values. You press âCtrlâ and âxâ at the same time, then release them, then press âCtrlâ and âcâ at the same time and then release them and voila, you are in the process of exiting Emacs. The great thing about Emacs is that everything is a buffer, you get the full editing power afforded by a buffer, not some second-class input field, especially for something as important as commit messages. Also, your original complain was that the shortcuts are "arbitrary and don’t seem to be logically organised". > Shortcuts in VS Code are a setting. Which is not so different from when the OP article talks about emacs prioritizing "stability" really. It's a great filter and training mechanism. I don't feel like I'm missing much. So I try it. I don't think that he was trying to make a 'witty' or snarky comment, just pointing out that anyone who wants to can be 'inside' Emacs development simply by firing up Emacs and running ielm (the interactive Emacs Lisp mode). I absolutely refuse to buy stuff from nestle. Every time I get a shitty modal with some text I can't copy paste, every time I have a crappy edit box lacking basic editing capabilities, every time I get some large text dump I can't search through with normal editing commands, every single time that happens I pray to the altar of RMS for him to smite the heathens and bring us to the age of enlightenment. > I'm not sure I can say the same about Kakoune, for example, which is a certainly a promising project but hasn't yet convinced me to jump the fence. I made the switch from Vim to Neovim as soon as I felt confident that (1) the project was going to be around for a while, and (2) it was on track to "overtake" Vim (you may choose to disagree with me on this, I found built-in LSP to be a compelling selling point, but the specifics aren't really related to the point I'm trying to make). You should be able to make the folder and add an init.el file for yourself as well, pointing to one or two projects that you would like to be editing with Emacs. Bluetooth audio works. Damage. I use (neo)vim daily, but there are certainly still lots of ways I can improve my workflow. Chromium works ok, but I don’t like using chromium. When using GUIs with sidebars showing what files changed, etc. Once youâre back in normal mode, you can navigate to other files within the same project by using the sequence: This opens up the already familiar navigator and lets you pick another file to switch to within the same project. On large codebases the performance of completion frameworks is for me often abysmal, language server connections sometimes give in without discernible reason and I need to restart. One of the highest learning curves I have ever had to deal with was getting into Emacs. It wasn't a mouse, but I fiddled about with a foot pedal input device back then. I still use Emacs every day at work just for Magit, but whenever Emacs freeze just for a few seconds every time I perform a big merge I just feel like finishing up the task in VSCode. I don't think its as easy imo. cam they run/debug the compiled artifact under Linux? I use VSCode for my day to day coding, so I have nothing against it, but explain to me how I can 'do' Magit and the like in VSCode...? Since we use âSPC o tâ for the terminal and âSPC o nâ for neotree, you can probably guess that âoâ is the category for opening popup windows.