Earlier quoted context omitted.
Exactly, it's wild! If anyone wants to have a look: https://www.youtube.com/watch?v=IXBC85SGC0Q Correction, the driver is specifically for Apple Xserve front-panel
What is also wild is that the video has 2.5M views, very odd.
The vi family
181–190 of 198 posts
Re: The vi family
#182Earlier quoted context omitted.
I’ve been a long time vim user, and I honestly never really bought into the efficiency claims. That gets repeated over and over, but If you’re a slow typer then no editor can really make much of a difference. Little by little your movements become more complex and efficient, and the journey to figuring that out is fun and interesting. The slight contradiction in your comment has a lot of truth in it. It’s just fun, a…
> practicing this game makes you better at any number of tasks that are relevant to your daily work. Vi key bindings don't apply outside of vi
Re: The vi family
#183One thing I noticed that with Claude Code and Codex running in the terminal, I tend to use VS Code much less than before, and found myself opening files in vim more often. It just looks like, for me, the agent development brings me back to using the basic tools, like many years ago, before VS Code existed.
This is interesting to me. vim was my main editor since the start of my career and I was very fast with it, much faster than my peers with an editor. at the outset of llm’s, I ended up using a plugin that would utilize bindings to help me edit faster. with claude code, and how fast it is making changes across many files, I almost never use vim anymore, or vi, unless I need to inspect files in a container/server.
Re: The vi family
#184I’ve been a long time vim user, and I honestly never really bought into the efficiency claims. That gets repeated over and over, but If you’re a slow typer then no editor can really make much of a difference, and development in reality is a lot of reading code and thinking about code when it comes down to it. I’ve never used it because I thought it would make me some lightning fast super developer. I’ve always used i…
I like vi/vim, but it gets me all too frequently because I'm not precise enough of a typist. I'm busy typing away and I hit the wrong modifier key or hitting caps lock and I end up pulling things up or making changes that I never intended to make. Worse, in the split second after it happens and my muscle memory tries to correct it my immediate intuition of what mode I was in is wrong or which modifier key I'm pressin…
Re: The vi family
#185Re: The vi family
#186I’ve been a long time vim user, and I honestly never really bought into the efficiency claims. That gets repeated over and over, but If you’re a slow typer then no editor can really make much of a difference, and development in reality is a lot of reading code and thinking about code when it comes down to it. I’ve never used it because I thought it would make me some lightning fast super developer. I’ve always used i…
My fingers just love it. Every time I need to jump to a non-modal editor my muscle memory screams: "WTF?!"
Re: The vi family
#187I wonder if people who stuck with vi(m) know about Xerox PARC, wysiwyg, gui and nomodes.
When I started at Red Hat in 2014, they asked if I liked Vim or Emacs, and what was my favourite IRC client. They were boggled when the answers were "neither" and "I can't remember."
I hadn't used IRC since the 1990s or so, and after learning the basics of Vi on SCO Xenix and IBM AIX in 1988-1989 I'd barely looked at it again. I was amazed to find passionate Vi advocates born since the last time I opened vi. It was very strange.
For me, editors moved past the bad old days of 1970s UI in the early 1990s and I've never looked back.
In the '80s I knew dozens of text editor UIs and was fast in all of them. In the 1990s I switched to CUA and never looked back.
My muscle memory is for CUA, and the great thing about it is not only blinding fast text editing, it means I can control the entire OS with the same keystrokes. I don't really need a pointing device at all on a Linux or Windows machine, except for using a web browser.
I use one, because it's always there now, but I can live happily without. My first close blind friend was amazed by the fact that I could operate his PC quite happily. He doesn't own a mouse, because he can't see the pointer. He only has screens on some of his computers so he can watch videos with friends; his UI is 100% speech.
I do need a screen -- I am not very skilled with a screen reader -- but give me a screen and a keyboard and I'm mostly set.
This is for me the selling point of CUA: it's not just an efficient UI and set of keystrokes for a text editor, it also lets me use any compliant app, GUI or text mode, on any platform. Windows 3 to Windows 11, and Xfce, and LXDE, and to a large extent in MATE or Cinnamon or LXQt, on Linux or xBSD.
Re: The vi family
#188I have nothing against Vi or Emacs, but since I strongly prefer GUI and mouse over terminal I use GUI editors. When I don't have a GUI available, I use micro, nano, joe.
I'd use any of them in preference to Vim.
But you might find you like Tilde.
Re: The vi family
#189Earlier quoted context omitted.
Funny, because the only reason I fire up VSCode is to chat up the bots because we are AI-compliant now and the customers pay for it. I tried nvim integration but it was half-baked and I can't even use nvim as an editor because they removed cscope support. nvi back in the day also dropped support for cscope because it wasn't vi enough. Hell, there is barely a working source repository for it. Only vim supports it out…
Why cscope and not an LSP?
I knew there were more visual studio type plugins that may also fit my needs but as I said I do not use plugins. If I install "vim" and it isn't in it, I most likely am not going to use it.
A "language server" also sounds all kinds of wrong although I suppose the function is the same.
Re: The vi family
#190I didn't know about vim-classic, I've switched to it now. I can't really notice much of a difference except themes are missing... and fzf needed a fix.