this post was submitted on 19 Oct 2023
77 points (91.4% liked)

Asklemmy

43986 readers
770 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. 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.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 50 points 1 year ago* (last edited 1 year ago) (10 children)

VS Codium.

It's VS Code, minus the Microsoft bullshit.

Source code is MIT licensed.

[–] [email protected] 4 points 1 year ago (3 children)

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.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (5 children)

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)
[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] [email protected] 2 points 1 year ago (5 children)

What's the package called? Am on nix but might look into it later

load more comments (5 replies)
load more comments (1 replies)
load more comments (9 replies)
[–] [email protected] 39 points 1 year ago
[–] [email protected] 25 points 1 year ago (1 children)

It's probably Emacs, but I'm a Neovim user, so I'm going to go with that.

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] [email protected] 3 points 1 year ago (3 children)
load more comments (3 replies)
[–] [email protected] 22 points 1 year ago (3 children)
load more comments (3 replies)
[–] [email protected] 20 points 1 year ago (1 children)

Depends on the language doesn't it?

[–] [email protected] 4 points 1 year ago

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.

[–] [email protected] 18 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] [email protected] 7 points 1 year ago

In Emacs, you are the IDE

[–] [email protected] 16 points 1 year ago (2 children)

no love for jetbrains ides?

[–] [email protected] 11 points 1 year ago (1 children)
load more comments (1 replies)
[–] [email protected] 15 points 1 year ago* (last edited 1 year ago)

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.

[–] [email protected] 14 points 1 year ago (1 children)

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?

load more comments (1 replies)
[–] [email protected] 13 points 1 year ago (2 children)

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.

[–] [email protected] 6 points 1 year ago

Emacs is a life style

[–] [email protected] 3 points 1 year ago (15 children)

is there a flatpak of this?

[–] [email protected] 2 points 1 year ago

Following up from my previous comment, there is a Flatpak of Emacs available on Flathub. Here are the instructions for how to install, whilst enabling native compilation, which will offer a performance increase and allow you to use features such as vterm (the best terminal emulator for Emacs).

load more comments (14 replies)
[–] [email protected] 9 points 1 year ago* (last edited 1 year ago) (8 children)

How about VSCodium? I don't think I should explain why VS Code is best editor.

load more comments (8 replies)
[–] [email protected] 7 points 1 year ago (1 children)

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.

load more comments (1 replies)
[–] [email protected] 7 points 1 year ago (2 children)

Helix. This is the one that could potentially be the successor to vim.

[–] [email protected] 9 points 1 year ago

I could never be a successor to vim. However micro is a pretty good editor.

[–] [email protected] 4 points 1 year ago (1 children)

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.

[–] [email protected] 7 points 1 year ago (1 children)

I love helix

Woah woah, not so fast.

Love you too

[–] [email protected] 2 points 1 year ago (1 children)

how do you have that robot symbol beside you

load more comments (1 replies)
[–] [email protected] 7 points 1 year ago (4 children)

Neovim all the way, super fast and lends you heavy control.

load more comments (4 replies)
[–] [email protected] 6 points 1 year ago (4 children)

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)
[–] [email protected] 6 points 1 year ago

Intellij IDEA Community Edition

[–] [email protected] 4 points 1 year ago (1 children)

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)
[–] [email protected] 3 points 1 year ago (1 children)
load more comments (1 replies)
load more comments
view more: next ›