>>8
that doesn't mean statically typed languages are horrid.
But they are. Work more to achieve the same. So I avoid them wherever I can.
Quite frankly, for large projects, a statically typed language like C, Java or (gasp) c# will own the equivalent dynamic - both in performance and in maintainability.
Not really
For small stuff, the dynamic languages will get you going faster
For big stuff they do as well. They are more productive, simple as that, so they are more productive for 1K lines and 1M lines.
Good for getting a prototype working really quickly.
Never understood why people speak of "rapid prototyping". I write the good stuff from the start, and if I fuck up, as long as everything was properly abstracted and your language has a proper, dynamic OO model, portions can be replaced with minimal impact. There's no such thing as prototypes, the application simply evolves, and if I need to rewrite it because it's too slow (never happened), that'll be version 2.0.