However, I think the debate about the value of the (alleged!) overhead of static typing is sometimes a red herring. If you widen the issue to other overheads such as Java's thrall to OO and Patterns then the debate gets different. These to me are bigger conceptual overheads than typing. Bruce Eckel makes an interesting argument by looking at the difference in opening a file in Java versus python. Basically, the latter needs one memorable line of code, whilst Java requires a lot of invocation and boilerplate code that is difficult to remember. I do think patterns and OO are overdone, or at least unquestioned as paradigms. Everything has to pay its way, and in this sense the argument the Eckel makes doesn't really have anything to with data typing (but everything to do with finger-typing!).
Of course language is not just lines of code. Really what we are talking about are wholes suites of technologies that play nice together. A language is generally part of a whole technological stack that includes development tools, web servers, databases, operating systems, even hardware. And of course you have to have people in that stack too - so a company may choose a language because of the number or the quality of the developers who are skilled in it for example.
All in all I think this means that the situation will become more complex and more languages will arise and gain traction but big languages will persist with huge market share. So the good news is that language wars are here to stay!
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=16538978-0cfa-4e22-b241-13da9d24cfff)

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=e1d33941-afe7-4cc6-81e0-3735878f4a68)