←back to thread

Scala 3 slowed us down?

(kmaliszewski9.github.io)
261 points kmaliszewski | 4 comments | 07 Dec 25 15:08 UTC | HN request time: 0s | source
Show context
pjmlp ◴[07 Dec 25 16:44 UTC] No.46183020[source]▶
The only issue I have with Scala 3 is Python envy, they should not have come up with a second syntax, and pushing it as the future.

If anything is slowly down Scala 3 is that, including the tooling ecosystem that needs to be updated to deal with it.

replies(4): >>46183121 #>>46183318 #>>46184223 #>>46187857 #
noelwelsh ◴[07 Dec 25 19:16 UTC] No.46184223[source]▶
Everything is up to date with the new syntax as far as I'm aware. Also, the compiler and scalafmt can rewrite one to the other. A project can pick whatever style it wants and have CI reformat code to that style.
replies(2): >>46184694 #>>46187179 #
pjmlp ◴[07 Dec 25 20:11 UTC] No.46184694[source]▶
When I checked a year ago, the IDE tooling still wasn't quite there.
replies(2): >>46185357 #>>46187641 #
1. spockz ◴[07 Dec 25 21:31 UTC] No.46185357[source]▶
What I don’t get because there is LSP and BSP support. What else is needed to get support for scala 3 from an IDE? Obviously, Kotlin coming from Jetbrains will make it receive a lot more love and first class support.
replies(1): >>46185852 #
2. pjmlp ◴[07 Dec 25 22:21 UTC] No.46185852[source]▶
Parity with Scala 2 development experience, which was lacking a year ago.
replies(2): >>46195231 #>>46210558 #
3. theCodeStig ◴[08 Dec 25 17:40 UTC] No.46195231[source]▶
With Metals the Scala 3 development experience is better; plus one is no-longer tied to one specific IDE.
4. still_grokking ◴[09 Dec 25 20:58 UTC] No.46210558[source]▶
What are you missing currently?