Late career Unix engineers refuse to concede on decades long debate
jumboframeinternet.com
jumboframeinternet.com
I'm not a fanatic, I'm skeptical about the tools I use and I'm feeling like moving to an ide like Vscode because they seem being much more productive to working with large codebases(has built-in source code navigation tools, etc).
My pet peeve is that by default on most Linux distros nowadays, when I type in "vi" I get the Crayola® colours of Vim.
If I wanted Vim I would have typed in "vim". I'm editing a .conf file, not hacking the kernel source code.
(Also I have no need for all the colours of the default ls(1): a simple 'ls -F' will do for showing the characters "/@*" for their type. No need for the Technicolor®.)
http://www.billharlan.com/emacs/#:~:text=You%20can%20switch%....
Much cleaner, simpler experience compared to VSCode's SFTP plugin, that - for some reason - always logs an error, even though the upload completed successfully...
But do I care what someone else uses? Nope. Not a whit. Not even a little bit.
A colleague with whom I work very closely is VScode guy. He can make it do it impressive things. We chide each other from time to time.
But neither of us cares. What we care about is the code we write using these tools.
We both have our favourites in the garage as well, but those tools are irrelevant by the time we get to the rocks and camber. What matters is the work, not how the work was done.
I started to administer unix machines early 90's. Vi had always been a shitshow for me and I loved the editor joe. Then pico. Then nano. Then graphical ones. Today vscode.
I am amazed how people use vi and the speed they get from it (honestly). When I ssh or docker exec, I am happy to know i, a and :q! in vi.
What I do not like, though, is someone telling me that my editor is wrong and theirs is the right one.
Someone showing me their editor/font/ whatever useful software is a godsend. I learned so much from these people.
Heads up though, their stuff up to 1-2 years ago is a lot funnier than now. Also they’re a lot less active.
Like, "Rust evangelism strike force" was coined by ngate and we don't see them that often anymore
Is that because of self-moderation or is it because Rust isn't at the peak of its hype cycle anymore?
* The plugin system seems fairly decent, and given it's popularity, there's usually a plugin for most things. There's a decent vim-mode plugin, linters that would take me a while to get working in my .vimrc, etc.
* It is fundamentally closer to a text editor than an IDE, so it'll do sane things like give you the option to use the system's python installation rather than some janky, ancient built-in version.
I dunno. I tutor for an intro programming class, getting them to install anything or work on the command line can be an uphill battle, VSCode is the best editor that will get widespread adoption in that kind of environment I think.
install VSCode
brew install nvim
install XCode command line utils for clangd
alternatively, install clang with brew
in VSCode install the clangd VSCode extension
in VSCode install VSCode Neovim extension
What's VSCode providing here compared to something like a terminal with tmux?
That is becomming less and less common though with good deployment tools.
Not that I actually use it for anything substantial, I just prefer it over vi for quick edits
I get lost when working on centos.
-bash: nano: command not found
-bash: apt: command not found
~OS swap was highly effective, sysadmin is confused~
(Yes this is a joke)
I know this is satire, but the devotion to vi an emacs when things like Sublime Text exist is ridiculous.
But truthfully, I can't imagine life without vim. How do you read or edit files on remote servers? Or in a docker container locally?
How do you just open all recently edited files without vim -p $(git diff HEAD^ --name-only) ? I'd feel so lost without it.
It's sped me up a bit for sure, but even more importantly is that it's done wonders for my RSI. With the amount of time I've spent using non-ergonomic laptops over the past 12 years, even typing was pretty painful for a while. After minimizing my mouse usage, getting a Kenisis keyboard and my wrists starting getting better. The ergonomic keyboard helped, but VIM definitely has also. Whatever editor I work with, I configure it so I can use VIM bindings.
I got into Emacs because it seemed like a neat thing to do. I don’t proselytise people to Emacs because learning it is a time-sink and the return you get is only realised if you really embrace a fully text-based interface, which can be hard and sometimes feels pointless.
That being said, it is my IDE (lsp-mode) for all languages and my git client (magit), and while I have not been able to make effective use of most other features in Emacs (org-mode, email clients, eww, etc.), these two things alone pay for themselves in spades. The learning curve is real, but the idea that you have to spend ages configuring your text editor is only true if you don’t use one of the many excellent distributions out there like Spacemacs, Doom, and Prelude.
I also use Vi keybindings (evil) because Vim is ubiquitous, and all the things people said about modal editing being a boon to productivity and helping you prevent RSI (which Emacs keybindings did not help with at all). I think Nano is awesome, but I never made it my go-to because it didn’t come installed by default on the old RHEL VMs I managed, while an old version it Vim did - go figure.