3 ms·
> JVM (especially paired with Kotlin) I agree the Go lang compiler/runtime needs "a Kotlin", with more null-safey build in, proper sum types, a std lib that ma
by cies 3y ago
> JVM (especially paired with Kotlin)
I agree the Go lang compiler/runtime needs "a Kotlin", with more null-safey build in, proper sum types, a std lib that makes heavy use of null-safety and sum types, better story for polymorphism, better ergonomics for writing stream pipelines, and additional compilation targets (like JS, WASM). This all while proving stellar interop with all Go code, obviously.
Kotlin is quite a sweet deal.
- chrisdinn 3y agoCurious to understand what you are suggesting here. What’s a better story for polymorphism than duck typing? What would (better?) null-safety look like in Go?
- cies 3y agoI'm saying that we need an XYZ to Go what Kotlin is to Java. The I name some ways that Kotlin improved upon Java that Go would also benefit from. > What’s a better story for polymorphism than duck typing? Something that give compiletime guarantees and has not runtime overhead. > What would (better?) null-safety look like in Go? https://kotlinlang.org/docs/java-to-kotlin-nullability-guide.html https://kotlinlang.org/docs/java-to-kotlin-nullability-guide...