LazyVim - Hackdot

Re:LazyVim by tzhenghao on Monday July 17, 2023 @02:24AM (#36754770)

I also went through this phase about a year ago, then just gave up and went with VSCode for its superior out of the box experience. That said, I still fire up vim to read files in a server or make one line config changes, but everything else....VSCode.

Related: Imagine having to remember the full scp / rsync command to sync source file(s) between your local machine and server, but it's just a drag and drop on VSCode.

I've just come around to accept that we've been blessed with great hardware over the years, and it's a waste if those extra CPU / GPU cycles aren't translating to significant dev productivity improvements. I'd take slower (~ ms) editor paint times over saving hours messing with vim configurations.

[ Parent | on HN ]

Re:LazyVim by xdennis on Monday July 17, 2023 @08:56AM (#36757701)

> Related: Imagine having to remember the full scp / rsync command to sync source file(s) between your local machine and server, but it's just a drag and drop on VSCode.

What's hard about this?

    rsync -a dir/ server:dir/

I'd much rather have commands in my terminal where I can search for them later than do things visually and have no record of what I did once and how to repeat it.

[ Parent | on HN ]