4 ms·
> With Go I feel like I am too bogged down in all of the unimportant implementation details. But then when people praise Python and Rust, getting bogged down w
by wahern 6y ago
> With Go I feel like I am too bogged down in all of the unimportant implementation details.
But then when people praise Python and Rust, getting bogged down with "unimportant implementation details" like specialized async typing and colored functions becomes an absolutely essential and useful aspect of the language.
There's just no accounting for taste...
- kevincox 6y agoI agree that async creating coloured functions is a compromise. However in practice I don't find it too distracting. At the very least it is less distracting then Go's error handling. (Although IIRC that is going away thankfully) However if you put N:M threading against 1:1 threading then you can argue about that all day. I think the implementations in Rust and Go are very effectively implementations of each model. The threading model difference is *not* something that I hold against Go. It is possible for a language to handle some things well but have other downsides that makes me prefer to avoid it.