3 ms·
> How robust/mature is it as of yet? More importantly, how are compile speeds and how much of a priority are they to the compiler maintainers? I too find it qui
by merb 10y ago
> How robust/mature is it as of yet? More importantly, how are compile speeds and how much of a priority are they to the compiler maintainers? I too find it quite promising in terms of "a language aiming for the benefits of Go with the expressiveness and added easier correctness of FP".
I never get the compile time argument. Well I code a big Scala application and the most time it spents is integration testing. the 10 minute test suite would probably still run 9 minutes and 30 seconds on go.
we heavily rely on the database and cover a lot of concurrency/parallelism things in our tests.
some things which we would need to test in go, too.
the compile time argument always looks good on first, but later on it's just a dumb way to prefer a language since it never matters.
(Actually even the go maintainers didn't cared for a while about the compiler performance).
- cube2222 10y agoWell, the thing is, with compile times of 2 seconds I can run my unit tests as fast as possible. At the same time, I'd just use a mock database for most of the tests. It's great to be able to compile applications like kubernetes in 2 minutes.
- NateDad 10y agoDoes kubernetes take 2 minutes to build? That seems super long. I csn compile juju (1mil LOC) in like 15 seconds.
- AsyncAwait 10y agoIf compile time is an issue, the new 'cargo check' tool may take some of the pain away.[1] 1 - https://blog.rust-lang.org/2017/03/16/Rust-1.16.html https://blog.rust-lang.org/2017/03/16/Rust-1.16.html
- cormacrelf 10y agoMore to the point, Rust is trying pretty hard on the compile time front. They've almost got incremental compilation out the door, on top of this.