Coders or lemmy, what editors do you use? Is it worth learning a new one?
-
Sublime text, vi, eclipse, emacs depending what I'm doing
-
-
Have you ever tried Rider? I found it such a pleasure to use in place of Visual Studio and I've never looked back.
Any times I've loaded VS since it just feels so slow in comparison.
-
Input speed is not "just" input speed. Note: I'm not about to argue for or against modal editors, I just want to answer: why is input speed really really really important, when (we agree) its not a big percent of total time.
5min at 80mph over a bumpy dirt path, ripping around turns is very very different than 5min of flat smooth straight driving.
A senior and junior dev could spend the same amount of time to rename a var across 15 files, move a function to a new file, comment out two blocks, comment one back in, etc. But. When I try to have a conversation while they do that, or when I change my mind and tell the junior to undo all that, its a massive emotional drain on them... because (if they're fast) they're driving 80mph over a crappy dirt road.
The input speed isn't a big deal because its a large chunk of time, it's a big deal because pausing a conversation/mental thread for 5 seconds while you wait for some typing to finish is incredibly disruptive/jarring to the thought process itself.
Those mental pause-and-resumes cause untold number of bugs, and THAT is where the real time sink happens.
If you're already at the point where there's no "pauses in the conversation" then I'd agree, there's not much benefit in increasing input speed on its own. BUT there's almost always some task, like converting all vars (but not imported methods) in a project to camel case from snake case, that are big enough to choke the conversation even for a senior dev. Increasing input speed is often decreasing how often the conversation gets interrupted.
-
-
Fresh from university I found a job with terrible keyboards. After about 4 months I started to feel constant pain in my wrists. I then switched to vim.
And it solved my wrists issue. But also, I discovered a way to edit text that was so much optimized fat beyond my expectations.
I wrote this article for people that would like to familiarize with vi keybindings.
https://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressively/
-
I personally enjoy using pycharm and vscode, depending on what I'm working on and what tools I need/want.
-
I get this, but an IDE should be invisible and grow as you ...
Why not "I get this, and an IDE should ..." ?
I don't think your idea goes against the idea of watching skilled devs to know what you are/are not missing
-
kate
I use Kate -- part of the KDE project ecosystem (for anyone else wondering) -- on all platforms, including Windows. So worth it.
-
Thanks, will take a look
-
Mostly emacs, vi, or what IDE I happen to be using like Eclipse.
-
I use Neovim. It feels like a second nature after using it for years. I love how effortless the interaction with the editor is after you have spent hundreds of hours learning it. I have no reasonable arguments to convince anyone to do that though. I just do it because I enjoy the hell of it
️ -
The main reason I like vi/vim is that if you're having to use multiple different computers (such as if one is a sysadmin, or in my case, does scientific computing), because if you're running on Linux, you can be confident that vi/vim will be on it.
For personal use, I've been using emacs, but I can't recommend that without feeling like I'm suggesting you try some heroin. I enjoy emacs because of it's complexity and how much power it gives me to modify it. It's very easy to fall into feature creep and over complexity though. That's why I can't recommend it — it's good for me because I am a chronic tinkerer, and having something to fuck around with is an outlet for that.
I would recommend learning the basics of vim though. As you highlight, getting back to your current level of productivity would take a while, even if you loved vim and committed to it wholeheartedly. It is possible to try it out with little commitment though, for the perspective. If you're on a machine that has vim installed already, try the
vimtutorcommand, which will start the ~30 min long inbuilt tutorial for vim. I liked it for giving me perspective on what on earth vim even was.I know you don't use it anymore, but I just want to fistbump you re: sublime text. I really loved that as a basic text editor that was, for me, just a slightly nicer notepad.
-
If I went back to the vi interface for some reason I'd at least use
ctrl-[. I dislike lifting my hand more than I dislike using modifiers. -
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
-
xfce text editor and sublime text, and vim but only when i want to work within the terminal
-
Zed, for the last few months, and happy with it (previously vscode) - I code in Scala, so Metals provides the complex hints / actions.
-
Dev of 25 years here: Cursor, for the LLM integration. It's based on VSCode, just way tighter AI integration. It's so good.
-
NeoVim plus tmux.
Great multi dimensional way of operating. You have access to the terminal and your ide.
It's beautiful
-
Doom Emacs
