←back to thread

Scala 3 slowed us down?

(kmaliszewski9.github.io)
261 points kmaliszewski | 1 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 #
lmm ◴[08 Dec 25 01:08 UTC] No.46187179[source]▶
> Everything is up to date with the new syntax as far as I'm aware.

The Eclipse plugin isn't, and none of the newer IDE integrations is reliable.

replies(1): >>46210541 #
still_grokking ◴[09 Dec 25 20:56 UTC] No.46210541[source]▶
There's still a working Eclipse plugin? Does Eclipse now support LSP servers?

The most reliable Scala IDE is currently Metals (in VSCode, but other editors work, too). Metals uses directly the compiler for all code intelligence so it's as reliable as the compiler itself.

https://scalameta.org/metals/

https://scalameta.org/metals/docs/#editor-support

replies(1): >>46212900 #
1. lmm ◴[10 Dec 25 01:14 UTC] No.46212900[source]▶
> There's still a working Eclipse plugin?

For Scala 2, yes, or there was the last I looked. Still the best Scala development experience by some margin, sadly.

> Metals uses directly the compiler for all code intelligence so it's as reliable as the compiler itself.

Not my experience; maybe it theoretically should be but the integration/bridging piece is still flaky.