5 ms·

Totally agree with you. I was really into Scala and studying it and everything. I still remember all the scala bloggers I follow, Daniel, Tim MOrris, Paul Sniv

Totally agree with you. I was really into Scala and studying it and everything. I still remember all the scala bloggers I follow, Daniel, Tim MOrris, Paul Snively, etc... Eventually I landed into a scala job role. Oh boy was it different. The other programmers were like type casting to Any or whatever that generalize highest type was (unified type theory). The complexity is pretty high, it's great if you know it all but in all seriousness it was impeding...

saryant 12y ago
> 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.
- codygman 12y ago
  It sounds like a Haskell programmer using unsafePerformIO everywhere. Or, perhaps a more apt example would be using Data.Dynamic for everything.
  - saryant 12y ago
    Yeah, casting to Any isn't a "grey area" in Scala's OO/Functional mix, it's just plain crazy.
  - carterschonwald 12y ago
    Those are still pretty safe to do. OTOH, Any drops everything on the floor
  - michaelochurch 12y ago
    unsafePerformIO is for quiche eaters. Real programmers use accursedUnutterablePerformIO. (Ok, but in all seriousness... don't.)
deepGem 12y ago
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.
- disputin 12y ago
  Reality is: https://departmentfortransport.files.wordpress.com/2013/03/iwm-fence.jpg https://departmentfortransport.files.wordpress.com/2013/03/i...
michaelochurch 12y ago
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.
- frowaway001 12y ago
  It's quite easy to disallow all of that.
  - saryant 12y ago
    Yeah, pretty sure you could get WartRemover or one of the other static analysis tools to disallow these sort of egregious violations.

saryant 12y ago

> 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.

codygman 12y ago
It sounds like a Haskell programmer using unsafePerformIO everywhere. Or, perhaps a more apt example would be using Data.Dynamic for everything.
- saryant 12y ago
  Yeah, casting to Any isn't a "grey area" in Scala's OO/Functional mix, it's just plain crazy.
- carterschonwald 12y ago
  Those are still pretty safe to do. OTOH, Any drops everything on the floor
- michaelochurch 12y ago
  unsafePerformIO is for quiche eaters. Real programmers use accursedUnutterablePerformIO. (Ok, but in all seriousness... don't.)

deepGem 12y ago

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.

disputin 12y ago
Reality is: https://departmentfortransport.files.wordpress.com/2013/03/iwm-fence.jpg https://departmentfortransport.files.wordpress.com/2013/03/i...

michaelochurch 12y ago

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.

frowaway001 12y ago
It's quite easy to disallow all of that.
- saryant 12y ago
  Yeah, pretty sure you could get WartRemover or one of the other static analysis tools to disallow these sort of egregious violations.