3 ms·
Doesn't this require a plugin, though? So it's basically an extension of Kotlin-the-language. To those who are using Arrow- why not Scala? Is it just because S
by ragnese 6y ago
Doesn't this require a plugin, though? So it's basically an extension of Kotlin-the-language.
To those who are using Arrow- why not Scala? Is it just because Scala has too much cruft? The only thing Kotlin has over Scala (AFAIK) is coroutines, which, honestly- I don't even love. They're very awkward to use and require unchecked exceptions for control-flow (and therefore have convention-based rules around using them).
- deleted 6y ago[deleted]
- valenterry 6y agoI think the answer is quite simple. You might start out with Kotlin and get familiar with it. But when you get thirsty for more, arrow is the logical next step. Going for Scala would require learning a lot of new stuff and once or even rewrite your things. It's the same for Scala and Haskell, which is why Scala is sometimes called Haskellator - I still would start a project in Scala because I'm more familiar with it.