3 ms·
I find that Scala is pretty successful if you are already a seasoned Java developer. Coming from other ecosystems, simple questions like "How do I use an execut
by phamilton 11y ago
I find that Scala is pretty successful if you are already a seasoned Java developer. Coming from other ecosystems, simple questions like "How do I use an execution context other than the global one?" are answered in terms of established Java practices. ("Just call this with an Executor.") And down the rabbit hole you must go. That plus a ton of leaky abstractions (also requiring a knowledge of standard Java practices) has been a big source of frustration for me. But I suppose that if you were already dealing with these quirks in Java, Scala is a nice improvement.
- anentropic 11y agoI had a similar experience learning a bit of Groovy recently on the surface it looks quite Ruby-esque, but a bunch of surprises lurking in wait because it's Java underneath
- muraiki 11y agoThis was one of my largest barriers in learning Scala. It seems that one needs to learn Java first because you're going to have to understand how it and Scala interact at some point.
- Scarbutt 11y agoSame for Clojure, I had to go down to the java rabbit hole. I guess it applies to any JVM language if you want to run production software.