Coming from swift, it's pretty refreshing to see a language that has decided to settle on the language itself pretty early and focused on improving all other aspects of the dev experience.

Last time i ran my go test suite on the CI i thought it had a bug because it was so fast compared to what i'm used to with swift.

I do still have a weird feeling of getting back to the stone age whenever i get a nil pointer panic though. i wish go devs could figure out a way of fixing those last quirks without impacting the rest too much.

In this regard Go has been the exact opposite of Rust.

Isn’t the Rust DX pretty good still?

Rust has very long compile time compared to Go

Rust could also have shorter compile times, if it gave up on a lot of the optimizations and features it currently does.

A massive source of compilation pain is that Rust just generally generates a lot of code - it always prefers specialization over dynamic dispatch unless the source specificies dynamic dispatch. Couple this with a culture of believing dynamic dispatch is always worse and lots of codegen for generics and you get one hell of a task for your linter. I wouldn't call this an optimization, but rather an almost cultural design decision.

Meanwhile OCaml and Haskell provide interpreters and REPL to ease the whole development experience.

Nothing prevents Rust of doing the same, other than resources.

evcxr does provide a hacky Rust REPL implementation: https://github.com/evcxr/evcxr

-Emily