3 ms·

Remember when Go proposed as a simple language? What a shitshow. Seems like Go's designers didn't know about interfaces, generics, and iterators when decided t

• vbezhenar 1y ago
  Market for simple language opened. Someone will fill it. Go failed expectations, by turning into C++.
• tapirl 1y ago
  It was also promoted as a language that prioritizes explicitness. But just look at the changes made in Go 1.22 (3-clause for-loop semantic change, [1]) and 1.23 (iterators, [2]). Magic implicitness was introduced in the two versions. Even worse, it was also promoted to keep backboard-compatibility seriously. But Go 1.22 broke the backward-compatibility so badly ([3] [1]). Despite this, the Go 1.22 release notes still claims "As always, the release maintains the Go 1 promise of compatibility". [1]: https://go101.org/blog/2024-03-01-for-loop-semantic-changes-in-go-1.22.html https://go101.org/blog/2024-03-01-for-loop-semantic-changes-... [2]: https://go101.org/blog/2025-03-15-some-facts-about-iterators.html https://go101.org/blog/2025-03-15-some-facts-about-iterators... [3]: https://go101.org/bugs/go-build-directive-not-work.html https://go101.org/bugs/go-build-directive-not-work.html And the change makers even have no interests to fix the problems caused by the changes: * https://github.com/golang/go/issues/66070#issuecomment-1981642904 https://github.com/golang/go/issues/66070#issuecomment-19816... * https://github.com/golang/go/issues/71830 https://github.com/golang/go/issues/71830 * https://github.com/spq/pkappa2/issues/238 https://github.com/spq/pkappa2/issues/238 * https://github.com/golang/go/issues/66388 https://github.com/golang/go/issues/66388 * https://github.com/golang/go/issues/71685 https://github.com/golang/go/issues/71685