Tangentially related: I'm a Linux guy - it's been my primary OS for almost 20 years now. Sure, there are some that are wiz's because of it, but they're usually neutralized by those who become ideological and inflexible because of it. People are paid to do a job, and I've found that whether they love computing or not is mostly orthogonal. It inevitably seeps into things unrelated to doing the actual work (even performance reviews via 360 feedback). When I was younger, I wanted to work in places that had a passion for these types of things. > But these Windows jockeys I dunno I get the feeling they don't necessarily love computing?
But lemme crack open your head and pour in the magic y'know? I also am receiving the money-points and it is good. But these Windows jockeys I dunno I get the feeling they don't necessarily love computing? Or in the way that it's this mundane tool for the production of money-points that they can then exchange for money. I work in this industry because I love computing.
Or rather, I know the pain since I have occasionally dipped my toes back into that world of hurt.Ī non-WSL2 Windows person doesn't get the benefits of Nix, usually doesn't live life on the shell (since every Windows program is gui first), doesn't do dotfiles management (you can but paths for the git Atlassian method are non-obvious), ssh password protected keys are a PITA.good God I could go on ad nauseum.
We have an intake script for getting them up on WSL2 with our stack on top but man these graduates are CompSci people and they did 4 plus years of CompSci using Windows? I can only imagine the pain. At the company I work for everything is native to Linux-I am floored by the number of interns we get who are using Windows (it's all of them). I don't understand why people are moving Linux -> Windows.
Now, with LSP, perhaps Emacs could offer code completion and refactoring, but the Java app I work on builds with gradle, and I have no clue how to tell the Java/LSP thing about the class path. Some aspect here, some aspect there, and then you get pulled away from Emacs. I used Mercurial (hg) for a while and TortoiseHg was really nice, so I didn't feel the need to use Emacs for this.
I switched from Linux to Windows because the world around me was like that, and so I could help junior colleagues with their EOL problems. I did try to build the Eclipse "quickfix" thing in Emacs, but all I got done was to add a missing import (because JDEE, I think it was, provided that functionality).
I used it for development, then the Java software I worked on got too big to internalize all APIs and Eclipse completion and refactoring really helped. Maybe these days it's possible to read Outlook emails nicely in Emacs. (Of course, they were Outlook users.) Emacs did not show that orange color, so I didn't know. I used it for email, then I had to collaborate with people who wrote "please see my comments in orange below". I used Emacs for a long time, but slowly got weaned off it. I think VS Code is a nice coding environment with good defaults and many things done right (compare installing packages in VS Code to Sublime! What an improvement) but nowhere near the capabilities and the productivity of Emacs. I manage several projects with it and switch contexts with one key-combination: Vagrant box is started, project folder is changed, necessary files opened, ready to hack, build, deploy, do server restarts with a single key stroke. And I write the docu in Emacs in org-mode, with org-babel I can run shell-scripts / python-scripts and other code in my org-file and see the output underneath it (like Jupyter notebooks), link to code fragments in my org files etc What makes Emacs exceptional is you can link all these packages together, create your own workflows by scripting Emacs in Lisp. But even if you only use it for coding: Magit is the best git client I have used in years (coming from P圜harm + Git Tower App, which is nice), then there‘s Ztree-Diff (excellent folder diff tool previously using Kaleidoscope app), then Eshell for interacting with the server from within Emacs (programmatically if you like), Tramp for remote editing, excellent integration of ripgrep and silversearcher (ag) into Emacs for code navigation, yasnippet as an excellent templates/snippet manager, and many more packages. Emacs is so much more than just an editor. When you finally learn to master and config Emacs, you run circles around all other editors.