Re:Three Months of Go, from a Haskeller’s perspective (2016)
by cube2222 on Sunday March 19, 2017 @07:38AM
(#13906505)
Well, 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.
Re:Three Months of Go, from a Haskeller’s perspective (2016)
by AsyncAwait on Sunday March 19, 2017 @11:22AM
(#13907605)
If compile time is an issue, the new 'cargo check' tool may take some of the pain away.[1]
Re:Three Months of Go, from a Haskeller’s perspective (2016)
by cormacrelf on Sunday March 19, 2017 @03:53PM
(#13909252)
More 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.
Re:Three Months of Go, from a Haskeller’s perspective (2016)
by NateDad on Sunday March 19, 2017 @09:29AM
(#13906909)
Does kubernetes take 2 minutes to build? That seems super long. I csn compile juju (1mil LOC) in like 15 seconds.
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).