Documenting compiler options was already mentioned a few times, but I think we need more emphasis regarding the profiler (-Yprofile-enabled and -Yprofile-trace). This is a wonderful feature that pretty much tells you how time is spent when you compile your project, and “Compile/build speed” has always one of the major complains of Scala developers over the years (still in 2026). The fact that it is only mentioned in a tiny release blog post from January 2025 is a missed opportunity.
It would be nice if scala docs pages had an embedded repl to test sample code and make sample modifications to run …and if by any chance the sample code would be more close to actual business domain ..it would turn scala doc a true source of learning
This is a loose point I made on reddit about a month ago, but wanted to reiterate here: that getting a working Scala project ASAP (and that fully works with an IDE) is an excellent goal to keep in mind when thinking about newcomers to the language.
I love Scala-CLI. But I still find that IntelliJ struggles to process Scala-CLI files correctly, and in my personal projects, I’ve had to quit, delete the `.idea` folder, re-run `scala-cli setup-ide .` and then re-open as a new project.
I’m guessing that’s an internal IntelliJ problem not a Scala one, but if people are used to their Python files having perfect formatting, highlighting, go-to-definition functionality out of the box, a language like Scala seems less professional when those things don’t work out of the box.
Just my two cents as someone who has little idea how these things work under the hood! Thanks for all the hard work by those who support the Scala community and deal with complainers like me ![]()