[fleitz]

Because you don't end up breaking code in trivial ways, eg if you have a method that takes a string and change it to take an int it's fairly easy in a statically typed language to figure out all the places you broke the code.

Large teams should be hunted down and broken into smaller teams, it's a stupid idea to have such a large team anyway.

The biggest problems in Java are not static typing (although inferred typing is much better). They are the lack of first class constructors, functions, unsigned types, operator definition and overloading and closures. The one actual feature Java has that no one else has is ironically one that is also one of the worst things about Java: checked exceptions.

When java lets me write something like: let (|>) x y = y x is the day I'll consider using it again, btw the above code is the pipe operator which lets you do things like this.

  "Hello World!" |> puts

[jarin]

Ruby has a little different mentality (duck typing), for example both of the following work:

  "10".to_i #=> 10
  10.to_i   #=> 10

I can see how dynamic typing, lack of interfaces, etc. can seem to cause a bunch of confusing to someone who's used to static typing, but in my experience lack of code readability is far more troublesome.