At work, I run into NEON/SIMD code fairly regularly and although I would not say I'm an expert at all, I find it entertaining, and wanted to share the fun. So I wrote up a tutorial.

I got permission to open it up, so that other people can share the fun too! Go and take a read: https://github.com/reMarkable/neon-tutorial/blob/master/neon.cpp

multibuild v0.0.2 is out.

New feature: output formats: https://github.com/rburchell/multibuild?tab=readme-ov-file#output-formats

So if you want to distribute tar.gz or zip, as well as, or instead of your #Golang binaries, that's now easily possible:

//go:multibuild:format=raw,zip,tar.gz

[master 0fae0d8b] pkg/irc: who cares?
6 files changed, 970 deletions(-)

RIP to some of the first #Golang I ever wrote. I don't think I've used it since 2021, and. the last *serious* use was probably 2014.

Hm, one of the few times I've noticed a missing piece in the #Golang stdlib: compress/bzip2 only has a decoder, no encoder. That's frustrating.

I wanted it for output formats for multibuild: https://github.com/rburchell/multibuild/pull/16

Seems it's quite an old issue:
https://github.com/golang/go/issues/4828

It blows my mind that #Github Actions doesn't have an officially supported action for creating releases.

Yes, I'm aware community actions for that exist, but I don't want to take unnecessary supply chain security risks.

I finally cracked the other day. Yet another small Go binary that I needed to test on a few different machines with different GOOS/GOARCH.

Meet multibuild: https://github.com/rburchell/multibuild

It's a simple way to make cross compilation of #Golang binaries easier. One command to build for many platforms.

And yes, I know that there are other options. But this one's mine.