4 ms·
What's the Scala community think about this development? I would think this would affect them quite a lot. Google is not helping.
by hinkley 3y ago
What's the Scala community think about this development? I would think this would affect them quite a lot.
Google is not helping.
- discodachshund 3y agoThe Typelevel folks on Discord are of the opinion it's not of much interest to them
- hinkley 3y agoI wonder if that's "not interesting" or "we already fixed this another way"
- dionian 3y agoIt's great, but irrelevant since Scala is already so far ahead. I will start to care if i am ever forced to do java again. I love how much better Java is getting! Most of these things we have had in scala for a long time already, and much better versions.
- rr808 3y agoScala community always thinks they're the best tool. The size of the community is at best static though, Kotlin and re-energized Java took away most of the reasons for using it. I know in my company the teams that went the Scala route complain of huge compile times and really struggle to find people, I think we'll probably port back to Java.
- vips7L 3y agoScala is just too complex, the tooling too slow, and the community had way too many breaking changes.
- hinkley 3y agoI went through a Scala book with a reading group. Lots of incredulity all around. Much more than the Java concurrency book, which wasn't easy either. An 'academic' language if ever there was one. But I recall it as the first vaguely Erlang-like language on the JVM, so whenever something about threading comes up I recall it. I'm learning Elixir instead.