It's good to see websites acknowledging the grim irony that you need cookies to remember users' cookie preference.
I'm surprised that there isn't a microformat specification for this yet. If one browser enabled users to blanket hide all of these I think others would follow.
miniblog.
Related Posts
In LSP, a position is represented as a line number and a column offset (in Unicode code units): https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#position
This is pretty elegant. You'll get the correct line regardless of encoding bugs, and the editor already knows the line number so it's cheap to compute.
I still find C-style format strings to be more readable than Rust format strings.
"Player %s has score %d" vs "Player {} has score {}".
The former feels a little easier to visualise how it will look in practice.
Have I missed anything? Every format string specification I've ever looked at is surprisingly big.
TIL that the HDMI specification is not public, so it's hard to write OSS drivers:
