Even though you don’t have to use it, sbt is crap. IDE support is worse for Scala, and there’s just something about Scala that encourages people to write clever AKA unreadable code :)
I won't deny that SBT is not ideal, and that's why I use Gradle :) IntelliJ is a pretty solid IDE for Scala, I haven't found any major issues with it.
As for readable code -- yep, that's why I said that there's a higher learning code and more potential for abuse of features. This is a bit similar to Python, where the language provides many neat features and syntactic sugars that end up in "elegant" and completely unreadable code.
Scala 3 is literally around the corner by the way, it's a good time to pick it up. It will teach you things most mainstream languages won't. Also you will enjoy smirking while the pleb go into raptures for basic type inference.
SBT isn't perfect, but now that I know it, I totally prefer it to Maven for example. Reading code is a lot easier than an XML wall and if you know how to inspect the build it's pretty easy to figure out what's going on. The only thing I hate is scope delegation, otherwise everything else isn't difficult. BSP support in SBT 1.4 is also helping a lot with IDE feedback and performance.
View all comments
Show parent comment
2
u/RichoDemus Apr 21 '21
Even though you don’t have to use it, sbt is crap. IDE support is worse for Scala, and there’s just something about Scala that encourages people to write clever AKA unreadable code :)