4 ms·
As someone who was within recent memory a "young programmer", I find this somewhat of an untrue statement. At the risk of defending my argument with anecdote,
by existencebox 13y ago
As someone who was within recent memory a "young programmer", I find this somewhat of an untrue statement. At the risk of defending my argument with anecdote, VIM was the tool of choice for my entire circle of friends in my undergraduate/graduate, and many of them now sit at MS, Google, and prestigious universities, I would not consider their (or my) careers crippled by this choice, rather facilitated by a tool which has worked well for our needs, and in application (and yes, I have tried other editors) I have not found lacking.
I would not say I "write Fortran" (given that soon to be father in law does, and I would be an embarassment to his competencies) I am familiar with it, and even so would not argue maintaining huge truckloads of legacy code. There does need to be lines for when you "burn it down" or realize that you've been accumulating technical debt that just maintaining compatibility for and of is only contributing to. I would not say that modern vim falls under this category at this point in time.