If you are interested there is a great repo to get you up an running on neovim without messing with anything. I got LSP support out of the box and took me less than a week to fully transition away from vscode. It’s called kickstart and is maintained by one the neovim contributors. I’ve done minimal tweaking months later.

My spelling errors only come into existence after I commit.

I’ve had this thought and felt it was so profound I should write a short story about it. Now I see this meme and I feel dumb.

A group of seals is a pod!

Lol I like your writing. The amount of headless boxes I work on has definitely contributed to my desire to get proficient at vim. Now I feel confident when I have to edit some text on a server, rather than hoping the server has nano and the file isn’t too big.

And that 3 days was how long it took until I was moving faster in neovim than vscode after 4 years of use. Though it’s still perfectly valid to use vim motions in any editor you want. Theres a reason most every editor has vim motions.

I personally die a little every time I need to take my fingers off the keyboard and reach for the mouse.

You ain’t understanding it dog

The Primeagon and Rene Rebe come to mind. Tsoding uses emacs and flys around. I’m still new to neovim and can say the speed at which I can transfer my ideas into the editor is significantly higher.

approximately nobody is competent in Vim because it isn’t worth learning

Come on, you really think its a giant conspiracy from elitists lying about their experience? You think thousands of developers are handicapping themselves for bragging rights?

Go watch a dev who is competent with vim/emacs and you will feel like a 7 year old on a tablet. I didn’t give neovim a try until I was thoroughly embarrassed with my ability as a professional text editor (software dev).

Is it the motions you don’t like or the editor itself? After 3 days with the motions I could never go back.

I started a CS club in college and it was crazy how many members would tell me this. They would ask me questions like I hadn’t picked up programming the year before and taught myself via the internet. If you want it, it’s out there.

This is lovely and I am a huge fan of your artwork! Keep them coming.

I hate that the convention for naming React.useState variables is [color, setColor], rather than [color, colorSet]. After I declare ‘color’, I want to copy/paste that variable and append ‘Set’, rather than copy the variable then writing ‘set’ then pasting then navigating to the 4th character then flipping the case.

Granted there could be some ambiguity if there was a variable containing a unique collection (aka set) but that is far less common than declaring a useState variable. I’d even settle for appending ‘SET’ to quell the confusion.

deleted by creator

There’s two types of programming languages, the ones people complain about and the ones nobody uses. Go is still my most productive language and is killer for building webservers. I basically use it as a scripting language since it’s so fast to write, compile, and execute.

deleted by creator

Thank you very much, I’m definitely going to take this for a spin! Can I ask if you or someone you know uses this? I’m curious what the experience is like and if theres any downfalls.

Its an effort to keep large code bases clean. I think they should allow them when running go run but not when building.

I don’t think its inherently bad but it feels jarring when the language allows you reference nill pointers. It’s so effective in its hand holding otherwise that blowing things up should not be so easy.

deleted by creator

Step 1: Remove the LSP from IDE.mod

Step 2: Run go mod tidy