2 ms·
Yet, like most Go design decisions, they will end up retrofiting what should have been there. Kotlin has the issue of being a guest language, and wanting to pl
by pjmlp 2y ago
Yet, like most Go design decisions, they will end up retrofiting what should have been there.
Kotlin has the issue of being a guest language, and wanting to play in many playgrounds, eventually it will diverge as it always happens.
As it is already happening, like now how will Kotlin async deal with virtual threads expectations, including writing portable code that doesn't suffer from runtime semantics, depending on the target platform.
- MarkMarine 2y agoSomething better than making everyone take context as the first arg in every function? It’s go’s own brute force way of function coloring, except you have to write it yourself and drag this arbitrary bag of data through every function, what a horrible stapled-on mess.