You must log in or register to comment.
I switched from vi to vim in 1994 and found it immediately obvious how to quit — it was just like vi!
I guess I’ll never understand these memes.
POV: You open vim for the first time.
More like:
You cannot expect people to read, it’s unreasonable.
deleted by creator
Type
hfor “hello” does literally nothing… ok… thought this was a text editor why can’t I even write… mashescstill no response, try typing “hello” but no matter how many time I mashhnothing happens. Right let’s leave and find a guide. Right so closing a terminal program that’s usuallyCrtl -cnope that’s done nothing, erm, what else works, nano usesCtrl-xlet’s try that, nope. Ermkillnope nothing, fuck this I’m just closing my terminal. - my first vim experience.<esc>:q!This…this hits way to close to home.
Me:
Be in a professional job, have to use crappy corporate software that takes weeks of training to use because it’s UX is absolute trash.
Decide, ‘fuck this, why would we waste all this time training people to use unintuitive interfaces when we can just make intuitive interfaces?’, spend months teaching myself coding, convince my company to pay me to write scripts so I can do it full time.
A few years later, finally transition fully into the world of software development by taking an intermediate dev job at a well known major company… only to find my colleagues building our dev environments around VIM and not seeing an issue with it :/
Are you guys actual programmers? What’s wrong with using Vim for development?
Yes, ones who value time and efficiency.
Why would you waste time teaching your devs a series of arcane commands to accomplish basic tasks that GUIs make obvious?
I get it when you’re a sysadmin or embedded hardware dev who needs to access the file system in CLI only environments, but outside of that it’s just waste of training time and resources to build your standard dev environment around unintuitive tooling when stuff like vscodium exists.
That’s fine and you don’t need to. But don’t knock it if you haven’t even taken time to learn it.
Yesterday I needed to insert a tab character on every line from 2 to 31,000 something. I made the line selection keystrokes in Cursor - it immediately crashed so hard I had to restart my PC.
Vim did it in a few milliseconds.
That’s fine and you don’t need to. But don’t knock it if you haven’t even taken time to learn it.
The literal entire crux of my point is that core processes at a company should have intuitive software that doesn’t require weeks of training.
So yes, I will knock VIM if you decide to use it as your company’s baseline coding environment. It raises the floor for no reason and forces everyone through a bunch of training when they don’t need it to actually do their job if their software was intuitive.
If you want to personally use it to do something powerful I have no issue with that, same way I have no issue with devs writing themselves bash or node scripts, what I have an issue with, is using it as the baseline. It literally requires training just for most devs to be able to exit it, and again, this is when tools like VSCodium have existed for years and are perfectly capable of handling large files.
You always have to learn the processes in a new company, this is just part of that. And if they don’t give you the explanations, training and time to learn, that’s a good sign you wouldn’t want to be at this company.
Maybe also speak to some of your new colleagues, whether they had similar trouble and see if you can improve the process for the next person.
You always have to learn the processes in a new company, this is just part of that.
This thread seems entirely filled with people who seem to not grasp my core point.
Yes you do, but in most cases, no you shouldn’t have to. Software should be intuitive. If it’s not, it’s more efficient to write software that is, rather than waste time constantly training everyone on inefficient software. This is literally one of the core tenants of the agile manifesto.
I agree with your core point, but no software is intuitive.
You can learn enough Vim to be productive in it in about 3 minutes.
You can install some plugins; your experienced coworkers have probably figured that out for you.
It’s ok to be a junior, but you should investigate things from time to time. You may even surprise yourself.
But you do you.
What’s that? A programmer who focuses on using arcane bullshit to gatekeep and feel high and mighty?
How unique and original!
Try focusing on shipping software rather than being an archinaut. Your customers and coworkers will like you better.
Last post from me. I have given you accurate information in good faith. Since you’ve decided to become aggressive and hostile, I can tell that you’re an unpleasant person and I’m glad you’re not on my team.
Good luck and have fun out there.
I mean, just type
:helpand then use your arrow keys to scroll around and read how to use vim/neovim.Learning how to use documentation should be the first thing you do when you try the Linux terminal.
man vim, Vim page on the archwiki, etc.
I have accidentally opened it so many times. I have to look how to close it every time
