Honestly, you might need therapy. But definitely an unpopular opinion, I'll give you that.
New York City is located in the southeastern corner of the state, so "upstate NY" means basically everything north/west of the NYC metro area. It's a word that is pretty much exclusively used for New York.
There were thousands lining O street in Lincoln, Nebraska today, which is a small college town of ~300k people. Definitely has to be in the millions.
It's definitely not faster than vim, fwiw.
Yeah the city is progressive. Tornadoes... Not as much as you would think. There was one last year that hit the outskirts of town a bit. Last one to do any damage before that was like 2017.
Have you ever been to southeastern Nebraska? Like... Where most people in the state live? It's nothing like western Nebraska. I live in Lincoln and it's a great place to live: progressive, lots of parks, great school system, nice downtown area, beautiful university campus, etc. Nothing like you're describing. Nebraskans don't actually go to western Nebraska very much.
Most of the population lives in the southeastern corner of the state, in Omaha, Lincoln, Nebraska City, and some surrounding counties. I live in Lincoln and it's a very nice place to live. Western Nebraska is completely different and not many people live there, and most people in the state don't go there either unless they are driving through.
There's no feeding going on. We're simply laughing at their expense.
Nobody sane uses vim as an IDE
True, same people use unix as their IDE and vim as the editor therein.
What do you mean "build our dev environments around vim"? If you mean they write dev tooling in vimscript and explicitly require everyone to use it, I actually agree with you. I don't believe employers should really ever force any particular editor or IDE if the work is getting done. I would be equally annoyed by a workplace forcing me to use vscode instead of vim. It would slow me down way too much.
If you are just complaining that they build dev tooling as a CLI, hard disagree. That is absolutely what dev tooling should use because it's actually universal and can be used regardless of your editor choice.
At my workplace, our dev tooling is done via CLI and our developers use vim, emacs, and vscode. Because it's all CLI, it's easy for individual developers to add their own scripts to automate parts of their workflow as they see fit (and if such automations are deemed useful by the group at large, it will get merged into our shared devtools repo). We even have some editor-specific stuff in there people have written that they find useful, but it's entirely optional.
Vscode definitely can't handle large files like vim can. I can open files that are multiple GBs in vim without issue. Vscode definitely cannot.
I'm millennial and have never heard of that one.