Scala Resurrection
degoes.net
Scala Resurrection
1–10 of 47 posts
Re: Scala Resurrection
#2Re: Scala Resurrection
#3Slow progress and change is good.
I think he would do well just calming down a little bit. He has some good critique, yes, but it's overblown in my opinion. I don't think the future of scala is as "uncertain" as he thinks.
I also think the scala community is fabulous, it full of great, smart people who work together. Just because there's heavy disagreements here and there, mostly just with a couple individuals, isn't necessarily a bad thing anyways, nor does it necessarily reflect the community as a whole.
Scala will never attract the mainstream, because its principals take too long to learn. There is nothing wrong with this, though. It's a language for long-time programmers who are interested in becoming super effecient.
Scala is awesome, and I'm excited for its future. Will it live 100 years, no, probably not, but there's nothing better in the next 10, 20 years.
Re: Scala Resurrection
#4To be honest, I think he is way-overly critical. It would seem like he thinks there needs to be some sudden changes or something. Scala is great today - there is nothing better (for experienced programmers) in my opinion (at least when it comes to backend development), and it's on a great path and trajectory. Slow progress and change is good. I think he would do well just calming down a little bit. He has some good c…
Re: Scala Resurrection
#5Re: Scala Resurrection
#6To be honest, I think he is way-overly critical. It would seem like he thinks there needs to be some sudden changes or something. Scala is great today - there is nothing better (for experienced programmers) in my opinion (at least when it comes to backend development), and it's on a great path and trajectory. Slow progress and change is good. I think he would do well just calming down a little bit. He has some good c…
From the article:
> The looming threat of a future radically different Scala 4 is the single greatest existential threat to Scala.
I think what prompted John to write this article is that there’s a huge commercial penalty in releasing a new major version of the language, and we should be focussing on making the existing language version(s) more commercially viable before we start another academically-led reinvention
Re: Scala Resurrection
#7Well, I think Scala is a nice niche language but with a lot of problems. I like it but the tooling sucks and it is slow to compile. Compared to other ecosystems like Java or Kotlin there are still things to be improved if this resurrection is to take place. We'll see.
It’s not a common language like Java, but I don’t mind that. It attracts smart developers who value the benefits of Scala over Java.
The Scala ecosystem has great libraries and platforms. It also gets the benefit of the entire Java ecosystem and the battle-hardened JVM.
Re: Scala Resurrection
#8To be honest, I think he is way-overly critical. It would seem like he thinks there needs to be some sudden changes or something. Scala is great today - there is nothing better (for experienced programmers) in my opinion (at least when it comes to backend development), and it's on a great path and trajectory. Slow progress and change is good. I think he would do well just calming down a little bit. He has some good c…
Would you recommend someone currently using F# to try out Scala?
Re: Scala Resurrection
#9Earlier quoted context omitted.
Would you recommend someone currently using F# to try out Scala?
Scala is both more functional than F# (type system has more features) and less functional (more emphasis on OOP). I don’t think it’s a net improvement tbh. Better JVM access is nice though.
Re: Scala Resurrection
#10They never contend with being better at using the existing platform, rather try to create an ecosystem of their own on top of the platform.
Idiomatic libraries to wrap existing ones, new IDE plugins, new build tooling, new package managers, introduce language features that only go one way, ....
Eventually they decide that targeting just that platform isn't enough so they go multi-platform, adding more design compromises to their abstraction layer for all platforms.
Meanwhile, the languages that are designed alongside the platform, evolve alongside it, no need for the added complexity, and eventually decisions are made that introduce forks in the road compared to the introduction of the guest language that create issues with those features.
Using the platform languages might not be hip, yet as long as the platform matters, they will matter, the guest languages, who knows.