Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The vi family

lpar.ath0.com

Post reply on HN
Print view View original

131–140 of 198 posts

Re: The vi family

#131

Post by remix2000 »

yanis_t wrote: post #26

It’s funny how many forks aiming to keep it free from LLM-generated code. The luddites are present even in the most progressive parts of the population.

Luddites didn't protest against automation, but rather against inhumane working conditions in factories and smashing their machines just happened to be efficient at destroying profit. So in a way, you could say luddites acknowledge technology for what it is, it's just techbros who fail to comprehend basic facts about machine learning and pushing text compression models as a replacement for everything they (don't) know anything about.

Re: The vi family

#132

Post by agumonkey »

jmathai wrote: post #109
t43562 wrote: post #66

Earlier quoted context omitted.

He IS saying that. Vi is more efficient for him every hour every day because he has been able to learn it to the point where there is nearly zero effort in using it. To learn something else would be to throw away all that hardcoded memory and try to rebuild it.

Learning how to use a proper IDE is a change in workflow. I never made that switch. The muscle memory of 2 decades of using a software is under appreciated. For me, it is about preference for what to optimize for.

[dead]

Re: The vi family

#133

Post by bcjdjsndon »

mpalmer wrote: post #128
40four wrote: post #119

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, 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’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

#134

Post by ab71e5 »

avadodin wrote: post #77
ventana wrote: post #9

One 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.

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?

Re: The vi family

#136

Post by sys_64738 »

People in the early days developed enough vi skills to allow them to get by. You could always be sure vi was installed on a remote system you were trying to access in the 90s. You also couldn't install stuff on this system and maybe you were accessing it from an ASCII terminal hooked into the serial port. This typically happened in a data center when you're trying to awkwardly use the terminal due to lack of space. Today I doubt that holds.

Re: The vi family

#137

Post by mpalmer »

bcjdjsndon wrote: post #133
mpalmer wrote: post #128

Earlier 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

Thankfully my work applies inside vi.

Re: The vi family

#138

Post by ghtbircshotbe »

40four wrote: post #119

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, 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…

That's fair, although now and then I have to do some repetitive task and using bufdo or a macro has saved a decent amount of time. And compared to something like notepad, all the little details probably save time. My average time savings has probably increased significantly after I stopped spending a lot of time creating custom vim scripts and syntax files.

Re: The vi family

#139

Post by linsomniac »

asdfsa32 wrote: post #124
40four wrote: post #119

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, 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…

It is fun because it is fluent. vi has a language.

I like to think of it more like a bytecode.
Post reply on HN