Originally Posted by Philip M
rnd me regards static type languages as old-fashioned.
The difference is that the machine does the tedious work of type conversion in JS. Compared to older languages like C, C++, or even Java, JS does a lots of tedious work for you: memory management, auto local name closures, semi-colon insertion, automatic function hoisting, etc. If you are awesome, not over-worked and smart, you can probably do a better job yourself. This is not unlike the age-old debate of using jQurey -vs- hand-built code.
as with anything mechanical, trade offs result. A honda civic with a good driver and a stick shift can always undercut the quarter-mile time of the same driver driving a civic with an automatic transmission.
So which car is better?
In this context, i think it's an obvious opinion, and only a fool would claim otherwise.
you might have caught a typo or two earlier with strict types, but with modern IDEs like M$ VS2012 (and many more soon, just wait), you can see those errors as you type, before you even save, much less compile.
plus we have jslint and jshint, in some editors in real-time, to enforce the level of convention and control a project is slated for, including using "==" where "===" would work.
in those respects, weak typing is a new-fashion way of coding with some but increasingly fewer disadvantages to it's predecessors.