The amount of time my classmates have spent dealing with vscode crashing, freezing, breaking, etc is way beyond negligible. And yet, I'm the weird guy apparently for preferring vim and GCC.
this post was submitted on 09 Jan 2025
13 points (93.3% liked)
linuxmemes
22141 readers
1290 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
codium > code
The full name is VScodium. https://vscodium.com/
Codium is a genus of edible green macroalgae.
That sounds tasty, where do I buy it?
(In homer Simpsons voice) Mmmmmm. Macroalgae.
load more comments
(1 replies)
Ooooh thank you for reminding me I need to make this switch
To you, @toothpaste_ostrich@feddit.nl, and anyone else planning to do the switch:
Back when I was still a VSC(odium) user, you needed to perform a small tweak to regain access to the quite useful extensions marketplace (in the sense of, paste the extension ID, see the same results as a M$ VSCode user*): There is a file named product.json which allows you to “regain” access if you populate it with the following values:
{
"extensionsGallery": {
"serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
"itemUrl": "https://marketplace.visualstudio.com/items",
"cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
"controlUrl": ""
}
}
(Taken from my old dotfiles, so this may be outdated, not sure. Also, you’ll have to look up the location of this file, it will differ depending on OS. On macOS it goes in ~/Library/Application Support/VSCodium.)
*If you do not need this 1:1 identical functionality, you may try the Open VSX marketplace. But especially in a class setting, I found this very useful, since all the tutorials/instructions will work without needing adaptation.
Good to know, thanks for passing this on!
Hadn't heard of this, but I'm going to switch now!
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 ;)
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 ;)
Vim needs are met by using Evil-Mode. You don't have to leave Emacs for this.
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
*stealthily closes nano window and closes laptop lid...
I feel like I’m the only person using KDevelop
Meanwhile, James rocks up with Notepad++
The Fiat Panda of text editors
load more comments
(1 replies)
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.
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.
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, tree works just fine anyway.
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).
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.
Professional software engineer here, using vim as my primary editor.
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.
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.
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. ;-)
load more comments
(1 replies)
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.
load more comments
(1 replies)
laughs in Emacs
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.
load more comments
(2 replies)
My professor was always trying to get us to use vim or eMacs over an IDE to write our C programs. I’m sorry, I like using a mouse. I know, I know, blasphemy. I’m taking a shortcut. I’m a noob.
When I absolutely have to, I go for vim, mostly because I know a few of the key bindings for it, but otherwise avoid it.
I’m taking a shortcut
more like a longcut. I save so much time and effort not having to switch my right hand between the mouse and keyboard constantly
I keep my hands on my laptop and use my thumb on the track pad. My hands don’t leave the keyboard. I actually never use extra mice or extra keyboards.
track pad
it's okay, we're gonna make a plan and get you to safety. Pretend you're ordering a pizza. How many people are currently holding you captive?
load more comments
(1 replies)
load more comments
(1 replies)
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) 🤷♂️
but how do people have the patience to deal with all of that in the beginning?
Whenever I was frustrated with a stupid undecipherable error message, I would just tweak my vim config a bit.
Within a few minutes, my rage at the error would be completely replaced with rage toward vimscript.
Then I would revert my vim config change, and return to the undecipherable error message with a fresh perspective. mainly relief that at least it's not vimscript.
Joking aside, I really did learn vim mostly during coffee breaks or while waiting on some long running build process.
I feel like I need to learn VIM at some point because various system tools have a habit of using it. (rpmrebuild and the man pages come to mind) It just comes up here and there even if you don't care for it.
view more: next ›