5 ms·
Go is poorly designed. It has a mediocre type system, bad support for genericism, too much reliance on non-extensible language keywords (range, make, etc.). Wa
by wyager 13y ago
Go is poorly designed.
It has a mediocre type system, bad support for genericism, too much reliance on non-extensible language keywords (range, make, etc.). Want to range over a tree? Too bad. Or maybe wrap the tree with a chan and watch performance and simplicity go out the window.
I mean, come on, what modern language actually recommends casting to the top type? That would be like if idiomatic C++ involved casting things to void*, or if idiomatic java involved casting things to Object, just so you can write generic functions and types.
- coldtea 13y agoI like Go for some stuff, but yes, it's pretty restricted. Even for the design goals that are lauded (simplicity, being boring as a virtue, fast compilation speed, no magic, concurrency built-in etc), they could have achieved them with a little more flair. One could say that if we compare the team that worked on C and Plan 9 to the Rolling Stones, Go is like their nineties albums.
- cnbuff410 13y agoLot's people don't care if language x is "poorly" designed or language y has "perfect" design. They evaluate language using two things: 1 Is it joyful to write without too much cognitive load? 2 Is it getting things done? Go fits both for them.
- babawere 13y agoI think you are evaluating 'go' based on feature set rather than the amount of friction a developer experience when using it to develop a good product. C++ is fantastic but I personally experience far less friction when working with 'go' for most of my task.