The Linux kernel can be configured at build time to expose its own headers as /proc/kheaders.tar.xz. Not sure if distribution kernels generally have this option enabled or not.
This is pretty much how clojure atoms [0] work. It's basically a Clojure wrapper around a Java AtomicReference, but Clojure's immutable data structures make an atomic reference type really useful because it is very cheap to read a "snapshot". It doesn't do upfront allocation, because like you mentioned, that requires you to have some knowledge about how the accessing code works. Additionally, whatever you are doing in Clojure is pretty likely to allocate memory anyway, so it probably wouldn't be that beneficial.
Oh neat, thanks! Yup, that sounds like a more general/flexible version of what I was trying to do.
I was focused on situations with just one writer (and originally also one reader), with the main thing being avoiding allocations. The situation where future values actually depend on past values, and specifically the current past value with other writers in the mix, is definitely trickier.
Some years ago I worked at a technology-oriented summer camp where I personally taught several bright young children to program. Minecraft mods were an incredibly popular project and a big driver of interest for many of the kids. Many of my counselor colleagues got into programming themselves modding Warcraft III and other games of that era. The absolute conversion rate may be low because the playerbase is so huge, but I think something like Minecraft is definitely the first (or zero-th) step in the journey of a lot of kids these days who become interested in technology and will later develop into the next generation of programmers & technologists.
Except that Weak DH only needs one prime - not two. It sounds like the author conflated RSA with DH somehow. It's very rare for real in-the-wild RSA keys to share factors (barring stupid errors like Debian's randomization fail).
In Clojure unresolved names are a compile failure, and Spec would not be involved. Spec is just a nice library for writing runtime assertions about data. An example would be calling a third-party API and then validating the response with Spec to make sure it matches your expectations, or even validating the responses you are about to return from your own API. Similar to a type system the Spec can also serve as a sort of documentation about what's in the data structure.
Wow, I really can't imagine an acquisition that I would less rather learn about than FB hypothetically buying reddit. Considering how FB has all the money in the world it is probably wise to start editing/deleting all my reddit comments now because once FB slurp the whole DB it's already over - the fact that I would never visit reddit again wouldn't save me.
To expand on the debugging bit, Datomic knows and can tell you the exact transaction responsible for every piece of data in the database. You can also see the complete state of the DB as of any transaction, but the complete history is more useful. It's like git blame for the database.
I think the strongest point in the article is this: "After the next breakthrough [in AI], we still won’t know how many more breakthroughs are needed, leaving us in pretty much the same epistemic state as before." That means that if we aren't prepared to start work on AI alignment now, there's not likely to be any sort of future event that will convince us of that.
