I like VScodium and VIM although I have also been using Kate and nano as of late.
If Vim is so good, then why can’t you browse Lemmy from it?
This meme was made by the Emacs gang.
Because unlike emacs gang, we don’t need to build an OS to browse Lemmy.
How bout you go back and let your friends know that if they’re in need of a good editor, try Vim ;)
Vim needs are met by using Evil-Mode. You don’t have to leave Emacs for this.
*stealthily closes nano window and closes laptop lid…
As a poke at Emacs’ creeping featurism, vi advocates have been known to describe Emacs as “a great operating system, lacking only a decent editor”.
https://en.wikipedia.org/wiki/Editor_war
:P
How bout you go back and let your friends know that if they’re in need of a good editor, try Vim ;)
If my friends wanted a good editor, then I wouldn’t recommend a Vimitor, I’d recommend ed, the standard text EDitor :p
Haha, y’all are welcome to try that ;)
laughs in Emacs
I would argue that vim is fantastic for a lot of editing and coding tasks, just not all of them.
Where it utterly fails is with deep trees of files in codebases, like you see in Java or some Javascript/Typescript apps. Even with a robust suite of add-ons, you wind up backing into full-bore IDE territory to manage that much filesystem complexity. Only difference is that navigating and managing a large file tree w/o a mouse is kind of torture.
File-based navigation is often inefficient anyway (symbolic navigation is much better when you can), but if you do need it, that’s what fuzzy finders are for. Blows any mouse-based navigation out of the water.
The only time a visual structure is useful is when you are actually just interested in learning how things are structured for whatever reason, but for that task,
treeworks just fine anyway.Fuzzy finding really shine for this use case, no need for a mouse.
Once I got used to single-directory filetree browsing plus fuzzy finding, I have never been able to comfortably use a traditional filetree anymore. most of them are not designed for efficient keyboard use (vscode and intellij at least) and don’t really help understanding the structure of the project imo (unless there arent that many files). For massive projects I find it easier to spend the initial effort of learning a few directory names and the vague structure using oil.nvim, and then eventually I can just find what I need almost instantly by fuzzy finding.
codium > code
Ooooh thank you for reminding me I need to make this switch
tbh, one of the essential things vim gets right for me is that it’s designed as a text editor, not (only) a code editor. I use it for so much non-code text as well, but it feels weird opening a coding tool for such things.
It’s great to use an editor designed and built when vietnam and leaded gas were all the rage.
Exactly! It’s rare to find such old things that are still excellent today
The comparison is bad. It’s more like comparing a kind of crappy car to a nice unicycle once you factor in UX. Not everyone likes to punch in key combinations so complicated it’s making game cheats look simple in comparison.
helix gang anyone?
epic editor :3
Helix is much faster than neovim, but annoyingly it feels so limited. Can’t change anything about it.
But it’s supposed to get plugins at some point.
:3
👋 present!
Meanwhile, James rocks up with Notepad++
The Fiat Panda of text editors
smh real programmers use magnetized needles on tape
Couldn’t help myself
I feel like I’m the only person using KDevelop
I plan on moving to a nice Neovim setup eventually, but VSCodium is so convenient out of the box for a baby developer like me.
You’ll be glad to know that the difficulty comes from the syntax and very little from any programming skill level. You learn new ways of writing certain code structures like indented curly braces for example. Programming python might be easier than cpp in vim, not due to the language, but just cpp having more complex syntax to type.
Tldr, almost exactly the same amount of effort whether you’ve been coding for two weeks or two years.
Me with zed
It always surprises me how complicated some of the editor tooling sounds in threads like this. Obviously once you learn how to use these things they are powerful, but how do people have the patience to deal with all of that in the beginning? This is coming from a guy who writes scripts constantly to avoid doing tedious, error-prone things.
Also I keep seeing people say vscode is slow. One of the reasons I switched to it is that it’s insanely fast compared to other editors I used (even those with far-inferior featuresets) 🤷♂️
I use vim btw
I use neovim btw
I use vim, aliased to vi, on Arch btw.
Have been a professional software engineer for 8 years now. Have yet to find a reason to use vim for anything (other than availability of course, but if nano isn’t installed for some godforsaken reason I have other problems lol).
Professional software engineer here, using vim as my primary editor.
I’ve been in various forms of coding and administration for around fifteen years now. Despite trying lots of editors, I have yet to find a reason to use anything but vim.
I do like obsidian for note taking.
edit: Removed typo.
Vim is a way more competent editor than nano. If you spend a lot of time editing files via ssh, vim is amazing. And when you get bitten by it, you’re infected. ;-)
I used to think this way. Until I found that with emacs you can edit any file on an SSH enabled computer remotely. Meaning that not only are you no longer constrained by what the computer has installed. But you can use your personality configured editor while editing that file. It’s called tramp.
BTW, with Emacs you can use vim key bindings evil-mode, so don’t stress about that.
Tramp is more featured, but if all one cares about is being able to edit remote files using a local editor, vim can edit remote files with scp too: scp://user@server[:port]//remote/file.txt
I tried tramp-mode at some point, but I seem to remember some gotchas with LSP and pretty bleh latency, which didn’t make it all that useful to me… But I admittedly didn’t spend much time in emacs land.
I’ve also used sshfs to mount a remote directory and edit using my local editor/env.
You can do that with vscode too. And probably many IDEs.
The only real reason for which you would need to use vim in such cases is if the target computer can’t run the vscode server, which I’ve never encountered yet.
I’m talking about not needing anything installed on the server though. Like you don’t need sudo. If the server has ssh then you can use Emacs to edit a file on it
Don’t need sudo or anything pre installed for vscode either. It will send the server to the machine via SSH and then run it automagically.
Fair. But to a sysadmin or devops engineer availability is pretty important.
