News for hackers. Stuff that matters.
Re:What's wrong with the default build tool for Scala by Fiahil on Monday November 20, 2017 @08:43AM (#15739795)
I had an interesting conversation once, in a Scala meetup. I was talking with someone about SBT being a gigantic pain in the ass, and their faire point was "I like SBT, it's better than Maven !".

While SBT might be better than Maven for the long Scala compilation time, it's nowhere near the user-friendliness of more recent build tools in languages like Go, Rust, Javascript, or [put your favorite lang here].

It strike me how close the Scala community is to Java's.

Re:What's wrong with the default build tool for Scala by camus2 on Monday November 20, 2017 @11:25AM (#15741045)
Go doesn't have a build tool like SBT or Gradle, it doesn't even have an official package manager.

Go has a compiler and that's all. You could argue Go is easier to build that Java, but it's because makes a lot of assumptions about how you organize your code on your HD which can be a hindrance if it doesn't fit the way your company operates. As always, Go is simple for simple use cases and get complicates as soon as you try straying from what go developers decided for you, there is no flexibility with that language.

Javascript has tons of build tools that are all clunky and horrible to use.

Re:What's wrong with the default build tool for Scala by merb on Monday November 20, 2017 @08:47AM (#15739806)
which build tool does go have? or JavaScript? Rust, yes. but the others are more glue than a real build tool. (and npm + gulp, grunt, webpack, browserify or whatever is way more painful than sbt, besides that there are better alternatives too all).
Re:What's wrong with the default build tool for Scala by eip on Monday November 20, 2017 @12:28PM (#15741534)
+"I like SBT, it's better than Maven !"+

That's debatable.