You can "brute force" scale pretty much anything just by throwing up more computing resources at the problem - but that means the language/framework/library is

You can "brute force" scale pretty much anything just by throwing up more computing resources at the problem - but that means the language/framework/library is less scalable than something else which requires less resources. If the different in scalability is large enough, I suppose one can claim that one of the alternatives is "not really scalable". I suppose that quote could use better wording.