This feature opens many doors for optimizing low-level performance in Go projects, that are already running multicore. IIRC there aren’t a lot of languages with built-in std lib support for SIMD and variants. Love the way Go is trying new stuff lately.
Besides the usual C and C++, we have Java, .NET, D, Zig, Julia, Swift, Rust.
So yeah, also appreciate having Go in the group instead of manually having to write Assembly.
However not many languages adopt ways to manually write SIMD, because most of us have no idea how to write good SIMD code in first place, I surely don't.
Even with languages that adopt ways to manually write SIMD, it’s mostly left to library maintainers rather than application developers.
I work for a C++ timeseries database startup that leverages SIMD about as much as we possibly can, and except for some extremely rare places we just use libraries.
Yeah, that is what I have heard from some NVidia folks as well, like Bryce Adelstein, use the libraries as much as possible, and leave the kernels for experts.
However even then, it depends on how the libraries API surface looks like.
But it’s not necessary at all, the whole point is that these utility libraries bring you more elegant code that work on all platforms without having to pollute your codebase with SIMD intrinsics.
Unless this was tongue in cheek, because this is in fact a problem with AI that it degrades your codebase in these types of ways.
We recently published another: <a href="https://github.com/google/highway/blob/master/g3doc/tutorial.md" rel="nofollow">https://github.com/google/highway/blob/master/g3doc/tutorial...
qprofyeh · · focus · HN ↗
abirch · · focus · HN ↗
mastermage · · focus · HN ↗
KeplerBoy · · focus · HN ↗
abirch · · focus · HN ↗
I'm grateful that Go a non-proprietary language offers these features.
pjmlp · · focus · HN ↗
So yeah, also appreciate having Go in the group instead of manually having to write Assembly.
However not many languages adopt ways to manually write SIMD, because most of us have no idea how to write good SIMD code in first place, I surely don't.
stingraycharles · · focus · HN ↗
I work for a C++ timeseries database startup that leverages SIMD about as much as we possibly can, and except for some extremely rare places we just use libraries.
pjmlp · · focus · HN ↗
However even then, it depends on how the libraries API surface looks like.
Thaxll · · focus · HN ↗
pjmlp · · focus · HN ↗
"CGO 2022 Keynote: Compiler 2.0"
<a href="https://www.youtube.com/watch?v=w_sX9aZoZxg" rel="nofollow">https://www.youtube.com/watch?v=w_sX9aZoZxg
stingraycharles · · focus · HN ↗
Unless this was tongue in cheek, because this is in fact a problem with AI that it degrades your codebase in these types of ways.
preisschild · · focus · HN ↗
vlod · · focus · HN ↗
[0] Mitchell Hashimoto: "Everyone Should Know SIMD" <a href="https://mitchellh.com/writing/everyone-should-know-simd" rel="nofollow">https://mitchellh.com/writing/everyone-should-know-simd
[1] <a href="https://news.ycombinator.com/item?id=49010648">https://news.ycombinator.com/item?id=49010648
janwas · · focus · HN ↗
setr · · focus · HN ↗
pjmlp · · focus · HN ↗