A nice collection of versioning schemes. I definitely didn't know them all.
A nice zine introducing the topic of faults and failures in distributed systems.
If you needed to be reminded that allocating small blocks of memory is a bad idea... here is a paper explaining it.
This is bad for two reasons: 1) people clearly put too much trust in random CDNs to distribute their dependencies and 2) people don't track depencendies obsolescence properly.
I remember playing with this a long time again... but it's actually even older than I suspected.
Definitely not the rules you want to apply on your projects. Still it's interesting to know how the STL uses explicit.
A nice pattern to separate decision from actions in complex algorithms.
This is become an important industry. Regulation is needed to avoid consumers to be in a mouse trap. This is necessary to reap the benefits of those technologies.
This is a useful construct in Python which is often forgotten.
Interesting approach for using CRDT through a file sync application. Probably something to see somehow generalized on traditional desktop applications.
Very neat piece, shows quite well the problems with Chat Control like laws. It's been postponed this time, but expect it to comeback somehow.
A new type of attack targeting the CPU indirect branch predictor.
Further clues that transformer models can't learn logic from data.
Interesting paper showing a promising path to reduce the memory and workload of transformer models. This is much more interesting than the race to the gigantic size.
Nice reverse engineering of a NFC chip used in a disposable transportation ticket.
Another story of precursors in the tech space. They basically invented the palmtop and spawned Symbian which was very much dominant on mobile for a while. The end of the Nokia story is a bit oversimplified for my taste just glancing over Maemo, but it is forgivable since it wasn't the focus of this piece.
Interesting tool for diffing database tables. Should come in handy for tests.
Interesting case, when everything else gets faster, memory copies might start to become the bottleneck.
This is ignoring the energy consumption aspect. That said, it is spot on regarding the social and economics aspects of those transformer models. They have to be open and self hostable.
Oracle doing Oracle things I guess... The surprising bit to me is the fact that so many people still seem to use Java SE while there are other excellent alternatives.