Many people could talk for days about this. One of the biggest issues for me is the lack of Referential Transparency. You can perform arbitrary effects (IO, mutating global state) whereever you want, and the language doesn't try to stop you. Exceptions, nulls, brittle compiler...
-
-
Yeah, that makes sense but, using the correct libraries such as cats or similar, you can reduce that cons to almost zero. As I said, Scala is not Haskell (however Haskell also has Exceptions) but I think is still better than Python or Java.. Or JavaScript!
3 replies 0 retweets 1 like -
1. cats is a copy of scalaz because of petty politicians and their gullible corporate fan club. 2. I wrote scalaz. 3. None of this works.
2 replies 0 retweets 1 like -
I'd be curious what you think of the Eta Language project
1 reply 0 retweets 0 likes -
If: (a) the JVM is an asset, not a liability (b) importing Java libraries is a legitimate strength, not just marketing Then: (c) Eta is extremely valuable. Insert your own truth values for (a) and (b).
1 reply 0 retweets 0 likes -
Does really make sense use Eta instead of Haskell? I mean, in Eta, Java code must be run into an specific wrapper called Java (Monad?). This obviously will complicate the interaction with legacy code so... Does Eta make sense if using Java libraries is tricky?
1 reply 0 retweets 0 likes -
Actually, it's not tricky. It's how Java interop is done well.
1 reply 0 retweets 0 likes -
If you say so, I belive you
1 reply 0 retweets 0 likes -
If you'd like to see an example of Java interop done poorly, see Scala.
2 replies 0 retweets 0 likes -
You needed to say that, didn't you?


2 replies 0 retweets 0 likes
No. It just motivated the Eta design of java interop, to not screw it up.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.