4 ms·
"Why do all articles about how wonderful vi is end with condescension?" Because one way to get someone over the initial learning hump is to "encourage" them by
by jerf 15y ago
"Why do all articles about how wonderful vi is end with condescension?"
Because one way to get someone over the initial learning hump is to "encourage" them by challenging their manhood. Same principle behind a boot camp sergeant telling every single incoming group that they are the worst bunch of nambypamby girliemen he's ever seen and he's been in this army for 25 years and that he will consider it a personal failure if he doesn't cause each and every one of you to quit in a crying mess. You're supposed to be motivated to try your best in the hope that he'll begrudgingly concede at the end that you didn't suck after all.
It works, but it has the side effect of creating a strong tribal identity among those who pass the bar, an "us" who are good enough to make it and the "them" who didn't. The military deliberately exploits this side effect; I'm less convinced it's a good idea in a programmer context.
- kstenerud 15y agoMy response to this approach has always been the middle finger. If someone can't afford me even the minimal level of respect, I'll leave. My worth is not dependent upon what other people think.
- vacri 15y agoSo a 4000 word article that includes character-by-character examples for newbies doesn't count as 'the minimal level of respect'?
- kstenerud 15y agoThat's fine, but ending on a disrespectful tone is generally a bad idea.
- vacri 15y agoI don't see the above quote as particularly disrespectful in context. It's a bit like a friend who has just spent half an hour talking you into going for that new wonderful job, and says 'or you could stay in your crummy current job'.
- kstenerud 15y agoBasically he's saying: "I think this way of doing things is awesome. Here's how to do it my way. Your way of doing it is crappy compared to mine, but hey it's your choice to continue being a substandard performer." Even your example is riddled with condescension, with your judgment from on high that your friend's job is "crummy". It's not only disrespectful; it betrays an unsavory vanity on your part.
- donaq 15y agoIf your worth is independent of what he thinks or says, why not listen to him and make decisions based on the merits of his argument instead of letting the emotional content throw you off? I'm not saying I'm capable of doing that, just that it's what I'm striving for. :)
- kstenerud 15y agoI'd still listen to what they have to say, but I'd consider it to be untrustworthy information, as their insult against those who do things differently would tell me that they have a strong enough emotional investment in their decision that they're unable to rationally consider the alternatives. Either that or they're being manipulative, which is also a big red flag.
- kahawe 15y agoComparing vi to an IDE is like comparing a screwdriver to a fully automated car assembly line... it is completely beside the point and they each have their purpose and downsides.
- ckg 15y agoScrewdriver - quick, cheap, easy to use, intuitive. Can be learned once and carried around with you. Car assembly line - lots of initial capital, specific to one kind of car, lots of time to learn. Seems like a valid comparison.
- kahawe 15y agoThe point is: these comparisons always try to make vi seem like the always better choice INSTEAD of an IDE and this is were I completely disagree. And you make it look just like that with adjusting the comparison in favor of vi, the screwdriver. This is just wrong. Let's see, you could also say: Screwdriver: specific to only one type of screw, limited to only a couple of similar sizes and all you can do is drive screws in and out or maybe stab someone. Assembly line: way more complex and needs some setup time but you can do WAY more things with it, way faster, way more efficient once setup, especially on a larger scale. It can drive screws in and out, solder, cut, fold, package etcetcetcetc. Pretty much anything you set it up to. So, vi is a horrible replacement or alternative to use in the typical huge Java (or what have you) e.g. web app projects where things like auto completion and easily getting from one class to another, built-in compiling, debugging, refactoring, source control etcetcetcetc really start to make your life easier. vi on its own cannot offer you that, not even remotely... then you need a shell and other programs to do all that. And there are no alternatives to most of the tasks an IDE can offer you help with. vi is definitely nice for editing files especially on a slow line and as a general purpose editor - but it is no replacement for an IDE and the comparison that it is "better than an IDE" might only apply for exactly one task: editing files. IDEs offer you tons of other things. So it is just wrong to compare to two or present one as a replacement for the other.
- sofal 15y ago