Comment Re:Interpreter flaws, not language flaws! (Score 1) 100
If you're using an interpreted language, you've already made the decision that you don't really give the slightest shit about speed. Interpreted languages as a rule run 10-50x slower than compiled and also require a runtime be installed. Nobody who is doing any serious programming cares about this.
Most code written today doesn't need to be 10-50x faster, so interpreted code is perfectly acceptable. For those few routines that need to be blazingly fast, feel free to optimize them in whatever fashion is appropriate -- whether that's writing them as libraries in real languages or even implementing them in hardware.
It's all a matter of economics. I can hire as many developers as I want at $30 to $50/hr that can code in the interpreted languages and then hire only one or two experts at $100 to $150/hr that know real languages. The interpreted language devs and work on things like data validation and pushing data in and out of a database while the lower level devs work on key proprietary routines.