Place where goldstein dumps his links so she doesn’t have 500 tabs ever again.
Tags are structured like this:
is- tags are about medium. Books, papers, blog posts, interactive explanations etc.
about- tags are about about. What’s this post topic or what’s this project is/for.
to- tags are about reason. Why did I even save this?
for- tags are about connections. Where can I use it?
a really fun (albeit somewhat impractical) way to compress webpages when all you have is browser APIs
one of my favourite RFCs probably
Allows you to find Unicode characters by drawing them.
The Rust language has incrementally grown a set of patterns to support control-flow effects including error handling, iteration, and asynchronous I/O. In The registers of Rust, boats lays out four aspects of this pattern shared by Rust’s three effects. Today these effects are typically used in isolation, or at most combined in bespoke ways, but the Rust project has been working on ways to integrate them more deeply with each other, such as async gen blocks.
The theory of algebraic effects and handlers has explored this design space and offers answers to many of the questions that the Rust project has encountered during this work. This post will relate the patterns employed by Rust to the terminology and semantics of effects, to help build a shared vocabulary and understanding of the implications of combining multiple effects.
This post is all about speculative compilation, or just speculation for short, in the context of the JavaScriptCore virtual machine.
Another take on io_uring in Rust. Doesn’t bring its own runtime, instead choosing to integrate with tokio.
About why free functions are important. I find verb/noun framework from this article quite useful.
How to spin before sleeping so that it actually helps and not harms?
The [board] game is about creating a small shellcode in memory by copying existing instructions and then exploiting a buffer overflow to jump into it, so that you can overwrite your opponent’s return address to force them to go to the game_over() function.There are other mechanics as well and more layers of strategy (like setting the exception handler or monkeypatching).
Detailed explanation of futexes, including some possible pitfalls.
Paper about how IT in healthcare in general and IT security in particular is done by people who don’t actually use it, listing different problems and workarounds that end up being used in the field.
Sacrificing convenience for security leads you to having neither security nor convenience.
Explanation of provenance, uninitialized memory and stuff like that. Useful as an entry point into realization that we don’t live in PDP-11 world anymore.