[rethab]

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?

[AheadOfTime295]

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.

[spir]

I've worked with Dotty a bit and read about it a lot.

I am very excited about Scala 3 :)

Scala 3 isn't a python2/python3 situation. It will take years for large codebases to be upgraded to Scala 3. However, the tools to migrate code from Scala 2 to Scala 3 will be reliable and highly automated, due to Scala's strong type system. Most popular Scala libraries and frameworks will be available on Scala 3 right from the get-go. I expect that most Scala programmers and companies will want to write Scala 3 code asap.

Within the Scala community, the only truly divisive aspect of Scala 3 afaik is the introduction of optional python-style and Haskell-style syntax with significant whitespace. I was stridently against significant whitespace and now prefer it after having tried coding Scala 3 for awhile.

[jmeister]

Thanks for this info, very useful and exciting.

I stopped using scala around 5 years back, want to get back to it. Would you recommend jumping straight to dotty? I’ve been doing a mostly python and a bit of Haskell in the meantime.

[spir]

I'd jump straight to dotty! You may as well learn the latest 'n greatest.

[jane_red]

> It will take years for large codebases to be upgraded to Scala 3

Which for production level code bases means never. I can't even imagine what we are going to do with our 7 year old Scala code base.

[vvillena]

It's the Java 1.4/Java 6/Java 8 problem all over again. Big companies refuse to keep up with the base languages, and important parts of the ecosystem (e.g. Spark) fall behind the language.

[maddening]

2.14 was supposed to be a stepping stone between 2 and 3, released only so that migration could be easier. They skipped it because apparently source code differences between valid 2.13 and 3.0 aren't that great. From what I saw it is mostly about migrating macros, the rest most likely would still work.