codium > code
this post was submitted on 09 Jan 2025
526 points (100.0% liked)
linuxmemes
23841 readers
456 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.
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.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
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
The full name is VScodium. https://vscodium.com/
Codium is a genus of edible green macroalgae.
load more comments
(3 replies)
load more comments
(1 replies)
helix gang anyone?
: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.
load more comments
(1 replies)
π present!
load more comments
(1 replies)
Meanwhile, James rocks up with Notepad++
The Fiat Panda of text editors
I always edit my code in microsoft word. Not only can it highlight syntax, it can use different fonts for different function names.
Definitely the most fully featured IDE Iβve ever used.
I use vim btw
I use neovim btw
I use vim, aliased to vi, on Arch btw.
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
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.
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.
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.
load more comments
(2 replies)
Fair. But to a sysadmin or devops engineer availability is pretty important.
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.
I feel like Iβm the only person using KDevelop
laughs in Emacs
I switched to zed too. It's not perfect but it's just nice to use a different editor that is not sluggish.
load more comments
(1 replies)
Ewww not even vscodium
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.
load more comments
(1 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)
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.
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) π€·ββοΈ
load more comments
(1 replies)
"But guys, gtfomp" - emacs
Code and intellij have plugins available to use vim keybindings on them. I like this approach to get the best of both worlds
the vim plugins are so bad... they only support the super basic stuff, as soon as you want flags with your search or chaining of commands they are useless
The neovim plugin for VSCode uses the actual nvim binary as a backend and supports all features.
that's a pretty neat solution
It's not the same. Granted it's been years since I used the vim plugin but last time I tried it couldn't even do standard find and replace.
load more comments
(1 replies)
That can't be right, the red car has a service manual and too many functioning assemblies for it to be VS.
view more: next βΊ