In the current age of software, we spend way less time designing with any future thought whatsoever. In that respect, I concur - the article's position is damag

In the current age of software, we spend way less time designing with any future thought whatsoever. In that respect, I concur - the article's position is damaging. You can design slow crap in any language, but I'd rather use something that has the potential to be robust and fast for my problem domain so I don't have to rewrite the entire app in the future to language "X", when I could have easily started with "X". Make no mistake - if you do this, you made an upfront error in selecting your language for the business problem. It may not be an unrecoverable error, but it is a failure in judgement regardless.