3 ms·
As someone who decided to use Scala at his previous company (Foursquare), but chose to use Java at his current one (Hometeam) I will say that the overriding rea
by harryh 10y ago
As someone who decided to use Scala at his previous company (Foursquare), but chose to use Java at his current one (Hometeam) I will say that the overriding reason behind my personal decision was compile times.
Compile times became a huge drag at Foursquare and I did not want to repeat that experience. I love many many many things about Scala but having engineers sit around for huge periods of time waiting on their compiler just wasn't worth it.
Other's opinions may differ from mine in many ways. Just offering up a single data point.
- whateveracct 10y agoDid you use sbt incremental compilation?
- harryh 10y agoFor a while. Eventually we abandoned SBT in favor of pants which is, imho, a much better build tool. It also supports incremental compilation but it was still slow.
- JackFr 10y agoWhat was the value proposition of pants? I'm no fan of sbt, but having sunk the cost of getting comfortable with it, what can pants offer?
- harryh 10y agoSmall compilation units (generally a single directory of files) and a bottom up acyclic specification of dependencies between them.
- hocuspocus 10y agoYou can check out this talk, given by a Foursquare engineer: https://www.youtube.com/watch?v=ukqke8iTuH0 https://www.youtube.com/watch?v=ukqke8iTuH0 This is pretty much the same concept as Blaze/Bazel or Buck, but from Twitter.
- harryh 10y agoDon't capitalize the S!! (sorry. pet peeve.)
- hocuspocus 10y agoMy bad, fixed :)
- harryh 10y ago:)