Comment by alexjplant
2 days ago
> brogrammers who judged you by whether you used vim or not
When I hear that term I usually think of people who brag about their job and sling copy-pasted untyped Python and JS from StackOverflow while being willfully ignorant of infrastructure, architecture, security, algorithmic efficiency, and anything else that makes maintainable software. Micro-dosing K and listening to too many Huberman podcasts are probably solid tells too. When I hear vim, however, I think about greybeards.
Did I miss the memo? There has been a non-zero amount of performative TUI obsession happening in the technical space for the past five or six years but I didn't think that using a fifty-year-old modal text editor was a shibboleth for being a brogrammer...
It’s putting tools and buzzwords ahead of actually building and creating. Does it matter more what you create or the editor you use, the language, etc… A lot of that dickwaving seems like it came in the past decade or two.
Vim experienced a revival in the late 2000s and 2010s due to influential Ruby on Rails people using it. The "editor wars" of old were won long ago—by vim; subsequent heats pit vim against JetBrains IDEs, Atom, and Visual Studio Code.
As IDE user since the MS-DOS days, having learnt vi on Xenix, adopting XEmacs in 1995 until UNIX got good IDEs, I missed that supposed vim victory in the 2000's.
Vim has plugins/extensions for all of those. Vim is a setting now. Even Obsidian I use with vim mode (obsidian plugin).
Maybe depends on industry? Working in finance during that time, the brogrammers were vim types, and super dogmatic about everything (first and foremost their workout regiment but also design patterns and algorithmic efficiency, to the point of exhaustion.)