I'd take the abstraction over compile times, but not having near-instant feedback is a huge compromise. But I've never known it to miss it.
-
-
Replying to @propensive
Is it first compile only that's slow, or all subsequent compilation? What times are we talking, roughly?
1 reply 0 retweets 0 likes -
Replying to @owickstrom @propensive
I'm not using Scala, so I have no insight into this, but it's interesting nonetheless.
2 replies 0 retweets 1 like -
Replying to @owickstrom
Hard to give meaningful figures, but a "small" project can take 2-3 seconds to compile; a 1000 person-year project, maybe 30-60 mins.
2 replies 0 retweets 0 likes -
Replying to @propensive
Yeah, of course. I can see how that's a problem. :/ I recall something about Go compiling its standard lib in ~1s.
2 replies 0 retweets 0 likes -
Replying to @owickstrom
There are some things on the horizon which should make it better, but we're looking at ~2-4x improvement in total over the next 5-10 years.
1 reply 0 retweets 0 likes -
Replying to @propensive
Nice! Do you think it's inherit complexity in the language design, or more accidental complexity in compiler impl?
1 reply 0 retweets 0 likes -
Replying to @owickstrom
It's a combination of both, and both are being "fixed" in the new Dotty compiler. The rest of my ~2-4x guess is from smarter parallelism.
2 replies 0 retweets 0 likes
I think there's also a lot of mostly-untapped potential from better code structuring, but not really a fix to force you to code differently.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.