What's Next for Scala

#1

Post by arbhassan » Fri, Apr 10, 2020, 7:24 AM UTC

Re: What's Next for Scala

#2

Post by rethab » Fri, Apr 10, 2020, 9:55 AM UTC

I'm particularly interested in how this plays out with dotty. My understanding was that lightbend was at some going to take over that compiler from EPFL, but taking over a compiler (the second, besides the current/old one) at the same time they are laying people off?

Re: What's Next for Scala

#3

Post by AheadOfTime295 » Fri, Apr 10, 2020, 6:24 PM UTC

rethab wrote: post #2

I'm particularly interested in how this plays out with dotty. My understanding was that lightbend was at some going to take over that compiler from EPFL, but taking over a compiler (the second, besides the current/old one) at the same time they are laying people off?

Announcement on Dotty as the future Scala 3 came from Scala Center (EPFL) not Typesafe/Lightbend.

AFAIK Typesafe/Lightbend has made no commitment to Scala 3.

Too bad the roadmap for Scala 2.14 has been scrapped.

Re: What's Next for Scala

#4

Post by totalperspectiv » Fri, Apr 10, 2020, 6:45 PM UTC

As one of those new people boosting recent numbers, Scala is great! I use vscode with Metals and had no jvm experience before. sbt is annoying, Mill seems super promising, and graalvm native images basically mean that if I was going to do it in python, I might as well use scala now.

Re: What's Next for Scala

#5

Post by AheadOfTime295 » Fri, Apr 10, 2020, 7:19 PM UTC

Farewells piling up:

Six years at Lightbend, by Eugene Yokota (Scala sbt, scalaxb, scopt) https://news.ycombinator.com/item?id=22836399

Re: What's Next for Scala

#6

Post by trevyn » Sat, Apr 11, 2020, 3:28 PM UTC

>it seemed to peak around 2016

https://trends.google.com/trends/explore?cat=5&date=all&geo=...

Early 2017, perhaps! Are Go and Rust seen as competitors to Scala?

Re: What's Next for Scala

#7

Post by AheadOfTime295 » Sat, Apr 11, 2020, 3:35 PM UTC

For context see

Lightbend secures 25MM funding round, proceeds to layoff Scala contributors https://news.ycombinator.com/item?id=22842166

Re: What's Next for Scala

#8

Post by _lbaq » Sat, Apr 11, 2020, 3:38 PM UTC

totalperspectiv wrote: post #4

As one of those new people boosting recent numbers, Scala is great! I use vscode with Metals and had no jvm experience before. sbt is annoying, Mill seems super promising, and graalvm native images basically mean that if I was going to do it in python, I might as well use scala now.

Scala 3 have a Python feeling over it with optional braces indentation (https://dotty.epfl.ch/docs/reference/other-new-features/inde...)

I wrote an example using this new (optional syntax) https://github.com/olofwalker/ting, if anyone wants to have a look.

Re: What's Next for Scala

#9

Post by pjmlp » Sat, Apr 11, 2020, 3:42 PM UTC

Since the post mentions Scala Native, all these guest language projects that eschew the platform that made them famous and try to pursue the dream of being their own platform, while building an ecosystem, GC and optimising compiler from scratch (even if they build on LLVM or compile via C/C++), would be much better taking advantage of AOT and JIT caches from several JVM implementations instead of pretending they don't exist.

Re: What's Next for Scala

#10

Post by tlarkworthy » Sat, Apr 11, 2020, 4:20 PM UTC

totalperspectiv wrote: post #4

As one of those new people boosting recent numbers, Scala is great! I use vscode with Metals and had no jvm experience before. sbt is annoying, Mill seems super promising, and graalvm native images basically mean that if I was going to do it in python, I might as well use scala now.

I just use maven for Scala compilation. I want to avoid Turing computable build tools (yes I know u can load plugins with maven but it is at least stiving for a declarative model)