3 ms·
The streaming/pipelining is the least of the issues here. The impossibility to define a generic compile time safe API makes these kind of projects useless in pr
by camus2 10y ago
The streaming/pipelining is the least of the issues here. The impossibility to define a generic compile time safe API makes these kind of projects useless in practice. It's just impossible to write abstractions in Go in a compile type safe way. These untyped API just feel dirty for a modern statically typed language.
- christophilus 10y agoYep. 100% agree. I think you have to treat Go as a dynamically typed system with some static typing thrown in, if you want to use it beyond its core use case.
- dgellow 10y agoYes! Thank you for saying this. If you think of go as a typed (and modern) Bash (the language, not the shell) everything makes sense :)