3 ms·

This really feels like trying to use Go for a purpose that it is inherently not designed for: absolute performance. Go is a fantastic case study in "good enoug

This really feels like trying to use Go for a purpose that it is inherently not designed for: absolute performance. Go is a fantastic case study in "good enough" practical engineering. And sometimes that means you can't wring out the absolute max performance and that's okay. It's frustrating, but it is fulfilling it's goals. It's goals just aren't yours.

callc 1y ago
After using Go for large and medium projects, with hundreds and < 10 people respectively, I’m left with a desire for a better language. I enjoy the simplicity of Go, but the tradeoff of Go’s imposed limitations (concurrency model, no subtype polymorphism in place of parametric polymorphism, no methods on external types, etc) feel like strict limitations without much benefit. (Minus labels and gotos, that’s great design) The speed I don’t care about The model of loose global functions for fundamental operations on built in data types is poor design. append(), delete(), close(), etc. How about make these methods on their respective types? Overall coding in Go feels like coding in a pre-alpha language. Syntax-wise, not the top notch tooling and packaging.