The Go language has long lacked official support for SIMD instructions, which means it has been at a disadvantage in terms of performance optimization. In recent years, with Go 1.26, an experimental version of the SIMD/ArchSIMD packages was introduced for AMD64 architecture. With Go 1.27, a portable version of the SIMD package was also added. Now, we can fully utilize native SIMD instructions to optimize go program performance.
I think too many people get dismissive of reaching out to Assembly in other languages, while in C and C++, having to reach out to Assembly to do exactly the same is seen as an advantage versus other languages.
With the lowering of implementation barriers—approaching a near-zero entry threshold—more open-source software will emerge. But at the same time, more “one-off open-source” projects will also appear. Their characteristics are:
- They meet the localized needs of the original author or a certain subset of people.
- They very likely will not be continuously maintained.
And they'll reproduce virtually the same problems, because code was never a primary issue for output. Products reflect organizational problems, which AI can't solve.
It's in the May 2022 edition of ACM, so it is at least very, very new. New enough that the number of Go users and criticizers who have read it are currently a rounding error away from zero.
