3 ms·

You're commenting on a vim post in order to help lost young programmers understand that there are other options besides vim? Speaking about vim as though it's

by sofal 14y ago

You're commenting on a vim post in order to help lost young programmers understand that there are other options besides vim? Speaking about vim as though it's an obvious choice in 2013 would be like insisting that everyone code in Fortran in 2013. Oh, now talking about how to use vim effectively is like insisting that everyone uses an archaic programming language? I suppose if we were to have a post here talking about how to use the command line effectively, you'd feel obliged to educate young programmers that we've moved on from the 1970s.

lutusp 14y ago
> You're commenting on a vim post in order to help lost young programmers understand that there are other options besides vim? Yes, and what better place? > Oh, now talking about how to use vim effectively is like insisting that everyone uses an archaic programming language? Based on the number of objections to a discussion of vim's alternatives, yes -- that's a legitimate comparison. > I suppose if we were to have a post here talking about how to use the command line effectively, you'd feel obliged to educate young programmers that we've moved on from the 1970s. Only in the midst of an amazing discussion that included various "cheat-sheet" strategies to get around the behaviors of an editor that demands cheating to be productive. Given that context, saying that newer editors don't require you to cheat seems entirely topical.