I enjoyed Scala, but I enjoy F# much more. .NET Core is a healthy cross-plat ecosystem, many of the VSCode/F# tooling issues have been eliminated over the past few years (IntelliJ was really one of the core reasons I preferred Scala), plus Akka.NET has F# bindings. Come on in, the water's warm:
Scala isn't fun anymore
201–210 of 394 posts
Re: Scala isn't fun anymore
#202Earlier quoted context omitted.
True, BEAM is a platform on its own. Scala can use Akka which is also awesome, but doesn't have all the nice things builtin like BEAM. I guess a merge of Scala as the language (because honestly, Erlang & co suck) and BEAM as the platform would be awesome!
A statically-typed language running on BEAM? Sounds like Gleam: https://gleam.run/ (Disclaimer: I haven't used Gleam, I just know it exists.)
I think as a Scala developer, my expectations/demands can't be matched by Gleam unfortunately. But if it could, then yes!
Re: Scala isn't fun anymore
#203Earlier quoted context omitted.
> You could never come up with the "one true solution" from the very beginning. I think I can! I mean, that's what science is for, right?
I'm not so sure. The problem is that the world is moving, including hardware, software, interfaces but also people and process. Languages have to optimize against a moving target. So naturally it's a good idea to optimize for something moving and not something static. This is what makes Scala good. The language itself is not very complex actually, but it enables complex and powerful libraries.
We are still in the phase where concepts are settling. Pretty sure nobody in a 100 years will think that Monads are a good idea.
Re: Scala isn't fun anymore
#204Earlier quoted context omitted.
I have personally spent so much time fussing with runtime ClassDefNotFound and MethodNotFound errors in Java that I am no longer able to respond to assertions that Java is type-safe with anything but an incoherent stream of cursing and rage tears. But Scala somehow seems to take all of that and intensify it. I have heard that Scala 3 is supposed to improve this, but I don't anticipate being able to adopt Scala 3 befo…
Not sure what you're doing with Java but that's not a common problem at all. Are you just aggressively stripping code and dealing with the fallout?
Working on projects that involve big frameworks with deep and ever-shifting dependency trees. So upgrading an existing dependency or taking a new one could often be a risky move.
Ground zero for most of them was Guava, which I unfortunately could not avoid due to it being a transitive dependency. And, even more unfortunately, Guava types were being exposed on the direct dependency's public API, so package relocation was not an easy option.
Re: Scala isn't fun anymore
#205good riddance. the only use case for scala is spark and i'm starting to switch to the JavaRDD. Scala should have never entered the enterprise space.
Anyone thinking about porting Play to another framework?
Re: Scala isn't fun anymore
#206Earlier quoted context omitted.
I'm not so sure. The problem is that the world is moving, including hardware, software, interfaces but also people and process. Languages have to optimize against a moving target. So naturally it's a good idea to optimize for something moving and not something static. This is what makes Scala good. The language itself is not very complex actually, but it enables complex and powerful libraries.
We are still in the phase where concepts are settling. Pretty sure nobody in a 100 years will think that Monads are a good idea.
Monads are like numbers. You can think they are not a good idea, but they are just a matter of fact and existence.
Also, in a 100 years maybe our brains will be completely different. How do you optimize your programming language for that? I don't think you can.
Re: Scala isn't fun anymore
#207Earlier quoted context omitted.
I really wonder why every time Scala is discussed on HN, someone wants to rewrite history about some mythical synergy with the Android ecosystem. This is so bizarre. In what world would Typesafe/Lightbend have found the money and resources to pull off even a fraction of what Jetbrains did with Kotlin? Let alone convince Google. On the other hand I'm very happy Scala isn't tied to the Android runtime.
> In what world would Typesafe/Lightbend have found the money and resources to pull off even a fraction of what Jetbrains did with Kotlin? Let alone convince Google. What did Jetbrains do with Kotlin that required money and resources outside of Scala's community reach? (Also, what do you mean about convincing Google?) I learned Scala a few years back and am working with Kotlin this year. I use Android Studio - I expe…
JetBrains employs 70 people working on Kotlins core.
> Today, 70+ people work on the core Kotlin project team at JetBrains
https://kotlinlang.org/assets/kotlin-media-kit.pdf
Plus a bunch of Google employees working on Kotlin stuff like the new K2 compiler.
Re: Scala isn't fun anymore
#208I'm starting to worry, I had a bet that Flex (Flash based UI component library) would be the future, then I got hyped by Ruby, then I fell in love with Scala, I'm worried about getting hyped about a technology again.
Re: Scala isn't fun anymore
#209Earlier quoted context omitted.
Error handling and Go doesn’t mix well.
That's a matter of opinion. Many, me included, very much like the current, very explicit, approach. I understand why people who like monadic constructs don't like it though.
I don’t know — I don’t claim that algebraic datatypes are the only proper way to handle errors, I’m okay with exceptions as well (even checked ones). But what go has is only very slightly better than C’s attempt, so I’m not sure it is that subjective.
Re: Scala isn't fun anymore
#210Earlier quoted context omitted.
I have personally spent so much time fussing with runtime ClassDefNotFound and MethodNotFound errors in Java that I am no longer able to respond to assertions that Java is type-safe with anything but an incoherent stream of cursing and rage tears. But Scala somehow seems to take all of that and intensify it. I have heard that Scala 3 is supposed to improve this, but I don't anticipate being able to adopt Scala 3 befo…
Not sure what you're doing with Java but that's not a common problem at all. Are you just aggressively stripping code and dealing with the fallout?
Incompatible versions of transitive dependencies, incompatible libs that your web server added, this is the default in Java unless you pay close attention to your dependencies.