Mostly emacs, vi, or what IDE I happen to be using like Eclipse.
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
I use Emacs and love it. It's an amazingly frustrating (and just plain amazing) piece of software, but it's hard to move away from it because it's the only thing like it. Maybe if Lem every gets mature enough I might switch.
I probably wouldn't recommend it though as it doesn't sound like what you're looking for.
On windows i use vscodium, on linux neovim.
As others say i think helix is cool, but the limited customization is kind of meh for me. I love the keybinds for it though.
cat << EOF > file.txt
# [[content here]]
EOF
On a more serious note: Neovim for quick file-edits, doom-emacs as my IDE.
Doom-emacs does most of the stuff you are already using out of the box, is highly configurable and it lets you use vim-keybindings. It's also free (as in freedom) software!
I just use Vim out of habit. I've been using it as my main text editor since I was like 13 or so, maybe more like 10 I don't really remember. It works perfectly well for the vast majority of my use cases. I use Jetbrains IDEs if I feel I need the power of a full IDE. Jetbrains has an IdeaVim plugin if you want it to be a modal editor, or if your fingers are accustomed to Vim keybindings.
I use neovim but i think helix is honestly better ootb.
I took a look at Helix when I was trying to learn vim and found it very easy to get started with, but was concerned about missing out on learning more standard vim bindings and functionality.
I found LazyVim + NeoVim got me pretty much the same experience without diverging as much from vim. Mostly I appreciate having access to a cheatsheet for commands.
was concerned about missing out on learning more standard vim bindings and functionality.
What do you mean? Do the standard vim bindings have some specific quality that you are after? Or do you work with many different servers and would have to use what ever editor is installed there?
Well I was mostly looking to learn vim and was trying to use Helix as a way to do that because it looked like vim, but with a commands window that popped up to help learn the commands. They're upfront about making some breaking changes from vim though, and while I may not need to jump into a bunch of different machines that often I do like the flexibility of being able to hop into vi, vim, nvim, or some GUI editors with vim bindings relatively comfortably. So I found that LazyVim was more what I was looking for personally and nearly as easy to work with out of the box.
I am glad to see the project seems to be going strong. That was another minor concern of mine, there's little risk of vim going anywhere, but I remember being excited about the Atom editor a while back and that just kinda faded away. If it passes the test of time I'd be happy to try it again in the future. I figure it would be easier to go from vim -> helix than vice versa.
Throughout my career, I have used (in no particular order)
- Eclipse (as Android Studio)
- IntelliJ (as Android Studio)
- SublimeText
- VS Code
- IntelliJ (as IntelliJ)
- various CLI editors when sshing into servers (vim, nano, a few others)
Switching your muscle memory takes a long time, which is why you have things like spacemacs, or different keybind presets for almost all of these editors.
There is more value in understanding how to extend and customize your editor than in searching for a new one. Use whatever your workplace provides the best support for, and then customize it from there.
There is more value in understanding how to extend and customize your editor than in searching for a new one. Use whatever your workplace provides the best support for, and then customize it from there.
I think there's something to be said for shaking up your environment periodically as well and trying new things. Sure, there's a week where you edit at a snails pace, followed by a month where you edit a bit slower than normal, but different tools really do have different pros and cons.
For the code bases I've worked in, this evolved from necessity as the code files were so large many editors were struggling, the rules for the style so custom that editors can't be properly configured to match, or the editor performance in general was questionable.
I went through a journey of sorts from IDEs to Electron based editors to Emacs and currently am working with Kakoune (and I've passed over a bunch of other editors like Sublime, Helix, and Zed that couldn't meet my requirements or didn't match my sensibilities -- even though a thing or two here or there really was excellent). Pretty much every change has been the result of the editor pain points that couldn't be addressed without actually working on the editor itself.
VSCode with the Vim plugin most of the time. Vim if I'm just editing something small and was already in a terminal.
Every IDE worth trying has Vim mode or a plugin for it, you don't need to use actual Vim to benefit from it!
I've moved on from vim to neovim, and I think I'll continue using something in that family in the future. It's a pretty stable experience overall, but the inclusion of LSPs and tree-sitter have been good improvements too.
Ultimately editors are tools, similar to keyboards, os-es, screens, chairs, shoes and so on. There are some objective quality differences between a well-constructed tool and some slapdash nonsense, and there are a huge amount of subjective quality differences. What suits me may not suit you, and vice versa.
It's generally good to try out some new (to you) stuff and see if you like it. If you do, great; if you don't, well, now you know. I think my worst experience was with Acme (or Wily? can't remember), during a phase where I experimented with Plan 9 stuff. Ultimately very not my cup of tea, but apparently Rob Pike (who made it) and some other gophers still enjoy it? Which is good for them, just like it's good for me that I can choose not to use it. It's just personal tastes, and I still think it's good that I gave it a go.
The debate over holding down modifier keys vs modes is also a part of the Emacs vs vi debate from many decades ago. There might be some statistics for what works best for the most people now, but again, use what suits you. And try some new stuff when you get curious, it's generally good for you.
I use the godot integrated code editor, but i am debating switching to writing the code in google slides and copying the text into notepad in a virtual machine
Sublime text, vi, eclipse, emacs depending what I'm doing
I've used everything, vim, nvim, emacs, visual studio, vscode, sublime, codeblocks, android studio, xcode, bloodshed, intellij, eclipse, VB, geany, dreamweaver, qt, atom, and cursor (even though it’s really just a plugin)
It doesn't matter. It will never matter. I use vscode today because it handles everything I throw at it and it's easy to make extensions for. Or cursor if I'm feeling lazy, the agentic mode with claude is pretty damn good if your codebase is well established.
Don't get hung up on the editor, just use the tools available to get the job done, at the end of the day programming is converting concepts to text.
Doom Emacs
VS Code with your favorite plugins is pretty fantastic for any editing in my experience. I've tried others and they do seem to work well, but not well enough to warrant switching, and they often come with quirks that are just annoying enough to make me want to switch back.
I suggest trying others to know what's out there, even if you ultimately end up back on VS Code.
VS, VSCode, Sublime, Neovim,
I use Sublime for short scripts in Python, VSCode for angular|typescript, VS for c# and neovim for elixir, elm and all new stuff I learn on my own.
Dev of 25 years here: Cursor, for the LLM integration. It's based on VSCode, just way tighter AI integration. It's so good.
Zed, for the last few months, and happy with it (previously vscode) - I code in Scala, so Metals provides the complex hints / actions.
xfce text editor and sublime text, and vim but only when i want to work within the terminal
I use pycharm at work for most things. Work paid for it. It has some nice stuff i like. I'm sure other editors do all of this, too, but nothing's been causing me enough pain to switch
- Database integration. Little side panel shows me the tables, and I can do queries, view table structure, etc, right here
- Find usages/declaration is pretty good. Goes into library code, too.
- The autocomplete is pretty good. I think they have newfangled AI options now, but the traditional introspection autocomplete has been doing it for me.
- Can use the python interpreter inside the docker container
- The refactor functions are pretty good. Rename, move, etc
- Naive search is pretty good. Can limit it to folders, do regex, filter by file name, etc
It does have multiple cursors but I've rarely needed that.
I use sublime for quick note taking. Mostly I like that it has syntax highlighting, and it doesn't require me to explicitly save a tab for it to stay open
neovim. i much prefer the motions of helix, but there’s just some plugins i can’t live without.
Why do people use vscode over codium? (Minus the two people who actually know the answer)
Sublime Text.
The only thing I need from my editor is syntax highlighting and not be slow.
(Assembler, C, Python, Java and Bash are the languages I mostly work with)
I personally enjoy using pycharm and vscode, depending on what I'm working on and what tools I need/want.
Most code I write is Java and I use IntelliJ for that. When I write Python I use PyCharm, anything else, Visual Studio Code or VSCodium.
All of these have plugins for vim keybindings which are always the first thing I install. I almost never disable them.