3 ms·
Rabbit holes for you to chase[1][2][3][4][5] 1. https://github.com/golang/go/issues/29696 https://github.com/golang/go/issues/29696 2. https://github.com/gola
by komuW 6y ago
Rabbit holes for you to chase[1][2][3][4][5]
1. https://github.com/golang/go/issues/29696 https://github.com/golang/go/issues/29696
2. https://github.com/golang/go/issues/42430 https://github.com/golang/go/issues/42430
3. https://github.com/golang/go/issues/44167 https://github.com/golang/go/issues/44167
4. https://github.com/golang/go/issues/44309 https://github.com/golang/go/issues/44309
5. https://blog.twitch.tv/en/2019/04/10/go-memory-ballast-how-i-learnt-to-stop-worrying-and-love-the-heap-26c2462549a2/ https://blog.twitch.tv/en/2019/04/10/go-memory-ballast-how-i...
- hardwaresofton 6y agoWow. So I fully believe that Go will eventually solve this and be even more valuable, because if people are creating so much value with it right now it is likely to get exponentially better as the Golang team considers and takes on things they avoided in the past (ex. Generics). I've glanced at those holes but I don't want to go down them, I have written a large personal project in go in like 5 years and I probably won't ever again because Rust. Also if I really wanted to be productive I'd pick Typescript. I do have one for you, in kind[0]. [0]: https://github.com/kubernetes/kubernetes/issues/53533 https://github.com/kubernetes/kubernetes/issues/53533