God bless @matthewdgreen.bsky.socialblog.cryptographyengineering.com/2024/08/25/t...
This blog is reserved for more serious things, and ordinarily I wouldn't spend time on questions like the above. But much as I'd like to spend my time writing about exciting topics, sometimes the worl...
Last year I wrote that “I want to use XAES-256-GCM, which has a number of nice properties and only the annoying defect of not existing.” Well, here we go. An easy to implement new extended-nonce AEAD designed for high-level APIs and FIPS 140 compliance. words.filippo.io/xaes-256-gcm...
XAES-256-GCM is a new AEAD extended-nonce algorithm designed for high-level APIs and FIPS 140 compliance.
I've finally moved to neovim (from vim). So far, I don't regret.
“Tell me what you like about Go”, I was asked. Here is an answer, focusing on the Ops perspective: lu.sagebl.eu/notes/what-i...#Golang
🎉🎉🎉The Go runtime team seems to be saying they are likely to update the builtin Go map based on the new SwissTable implementation from CockroachDB: github.com/golang/go/is... It's based on Abseil SwissTable but adds extensible hashing to keep core Go map behaviors, like incremental resizing costs.
Zstd compression is impressive. Had some 111M access log file that is now a zstd-ed 15M file, and it only took 0.6 sec. With Gzip it's 21M and it takes more than 1 sec. github.com/facebook/zstd
Zstandard - Fast real-time compression algorithm. Contribute to facebook/zstd development by creating an account on GitHub.
I wrote up a blog post on our findings with scaling Go to 192 cores per machine and the limits we ran into with the Go runtime here: jazco.dev/2024/01/10/g... It was a really interesting problem to investigate and had us scratching our heads for a little bit but the performance gains are huge.
Go’s atomic.CompareAndSwapT does not always compile to the equivalent CPU compare-and-swap instruction, because some architectures don’t have such instruction. So, what does Go do instead? I checked for Arm64 and RISC-V 64: lu.sagebl.eu/notes/go-cas/#golang#riscv
It’s almost 2024 in my TZ, I think it’s time to deliver JPEG XL images. At this time only up-to-date Safari users support them (without wizardry)—it turns out Safari Mobile is the first user agent visiting my website. I guess it’s worth the investment.