That's just bad usage of a language feature don't you think. I'm still trying to figure out whether to blame the language because of the way programmers use it.

Personally, I like the object + static typing + first class functions as it eliminates 90% of errors at compile time. If any error occurs at run time, am pretty sure it's logical. This is a huge plus. The only drawback - the ridiculous amount of type specific code you have to write for mundane changes/updates.

Reality is: https://departmentfortransport.files.wordpress.com/2013/03/i...

> The other programmers were like type casting to Any or whatever that generalize highest type was (unified type theory).

As a Scala dev, that is absolutely terrifying. I can't even begin to think of a good reason for that.

It sounds like a Haskell programmer using unsafePerformIO everywhere. Or, perhaps a more apt example would be using Data.Dynamic for everything.

Yeah, casting to Any isn't a "grey area" in Scala's OO/Functional mix, it's just plain crazy.

Those are still pretty safe to do. OTOH, Any drops everything on the floor

unsafePerformIO is for quiche eaters. Real programmers use accursedUnutterablePerformIO.

(Ok, but in all seriousness... don't.)

Scala with mediocre programmers (CommodityScrumDrones writing FactoryVisitor classes) is an outright disaster.

The Java community has its flaws (oh boy, does it) but it has adapted to the hordes of mediocrities. Give Scala to mediocre engineers (who typecast to Any, use null instead of Option[T]) and you have the Java hell with worse IDE support and 5x compile times.

It's quite easy to disallow all of that.

Yeah, pretty sure you could get WartRemover or one of the other static analysis tools to disallow these sort of egregious violations.