VS Codium.
It's VS Code, minus the Microsoft bullshit.
Source code is MIT licensed.
this post was submitted on 19 Oct 2023
77 points (91.4% liked)
Asklemmy
43826 readers
870 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
I really wish the WSL extension wasn't locked behind VS Code. My workflow is heavily reliant on it which locks me into the proprietary IDE.
You should be able to setup WSLg then run the Linux Codium in WSL. Regular VS Code will work that way, it just gives a little "hey, you know you could use remote WSL right?" message then keeps chugging.
load more comments
(5 replies)
when I install codium (with yay, because I use Arch... btw) there is a package that just makes the plugin store the same as Microsoft's. I found one that wasn't working and that was MS pylance, I use pyright now.
load more comments
(6 replies)
load more comments
(1 replies)
load more comments
(9 replies)
It's probably Emacs, but I'm a Neovim user, so I'm going to go with that.
Same here. Emacs is a solid choice, if you wanna get lispy. I just tend to prefer the vim way of things and don't have the time and energy to try learning Emacs again at the moment.
Depends on the language doesn't it?
Unless it's something like an HDL for a proprietary FPGA suite, in my experience, not really, no. Just need a good LSP, Treesitter grammar, and the rest is just QOL. Not having to switch tools is a perk.
Emacs, because it's so configurable that if it isn't the best FOSS IDE it's your own fault for not configuring it right.
In Emacs, you are the IDE
Well nvim, obviously. It's pretty much fully featured. With LSP plugins you get all the code completion, hints, type info, docs and so on. You also get typical navigation like 'go to declaration' and some basic refactoring. And all inside the best editor there is. I'm using it for C, JS, JSX and Rust and all works great. I honestly prefer it to IntelliJ, it loads faster and is more responsive.
My favorite is Kate because it's less of an IDE and more of a text editor with side panes for the project tree and a terminal to run the program. Easy enough to set up a hot key to save-build-run. I think that's all I need?
Right there with you, I'm on the admin side of things, so the time it takes the app to start is a bigger deal to me than the full featured-ness of VS Codium, but provides contextual highlighting and some quality-of-life coding features that you won't find it text editors.
Lots of replies mentioning Emacs but Emacs out of the box is gonna be essentially a text editor (insert obligatory: Emacs isn't a text editor; it's a LISP interpreter).
However, install Doom Emacs, and you have a full IDE experience for essentially any language you could ask for. I highly recommend it.
Emacs is a life style
How about VSCodium? I don't think I should explain why VS Code is best editor.
You might need to explain to me. I've been having so many issues just using vscodium, took me forever to figure out I need to build and compile the code myself and not run it using the play button like Visual Studio in school (I'm a second year comp sci student).
This is only the case if vscodium is not bundled with your distribution
load more comments
(1 replies)
load more comments
(5 replies)
VSCodium, emacs, vim/neovim, helix.
Helix is pretty slick, but it’s not very extensible. Very easy to use and if the out of the box features are good enough for you then it’s a fine IDE.
Neovim is my preference unless I’m working with Jupyter notebooks, in which case I switch to vscodium. It’s a pain in the ass to set up. I took the easy way out with LazyVim. It’s fast to work with and I can use it for almost everything.
I dabbled with emacs many years ago. It’s like vim but completely different. You can make it do anything. Personally, I don’t care for the keyboard shortcuts. It’s probably easier to pick up than vim, but all the key chords and sequences are too much for me. In any case, anyone willing to look at vim should also take a look at emacs.
VSCodium is accessible and extensible. You can’t go wrong with this one. It can’t refactor like the Jetbrains stuff, but if there’s anything else it can’t do then I don’t know what it is. It’s a great IDE.
Really, any of these can do just about any job and do it very well. There’s no choice that clearly stands above the others. It really comes down to personal preference.
Helix is pretty slick, but it’s not very extensible.
Bruh, thanks for the compliment, but I can be very flexible.
Helix. This is the one that could potentially be the successor to vim.
I could never be a successor to vim. However micro is a pretty good editor.
I love helix, I just wish the development was a bit faster. The main developers are all quite busy and I would love nothing more for them to be able to use some of the open collective money to pay themselves to work on it full time for a bit. I think in a year or two it will be amazing.
I love helix
Woah woah, not so fast.
Love you too
Intellij IDEA Community Edition
Emacs because it lets you configure everything exactly the way you want it. You can also go with Neovim, but it only runs in the terminal.
load more comments
(4 replies)
micro + makefiles. It's very very fast.
VSCodium is OK aswell, has lots of extensions, but a bit slow. I can work with it way better than with IntelliJ products though.
load more comments
(1 replies)
view more: next ›