1. 4

    Nice article! I just have a few minor suggestions that might avoid confusion for those learning from it:

    The browser selects the memory region normally reserved for the address bar.

    Just to note that “memory region” has a specific meaning that doesn’t apply here (ie. the equivalent of Linux’s vm_area_struct). Maybe “virtual memory address” would suit? Also, modern browsers don’t usually have a single address dedicated to the contents of the address bar (which seemed to be implied by “the memory […]”), because it’s not MT-Safe, which is fairly important nowadays with a separate main thread, UI thread, background task threads, etc.

    I also wonder if it might be worth mentioning SNI, since otherwise there appears to be a gap in the information in your TLS section (eg. “how can an abstract load balancer know which certificate to present before decryption?”). :-)

    1. 1

      This almost reminds me of a modern version of Terminus, which I have used for the last 15 years or so. Unfortunately now I’m spoiled to run at 6x12, and “smoothness” somewhat hinders in that kind of size.

      Also coincidentally I’ve been looking for a programming font like Terminus with CJK support, and now I see variant Sarasa Gothic linked in the readme. Interesting!

      1. 3

        FWIW, we (systemd) have also seen a number of problems with RDRAND as well. Probably the most notable was this issue where it was broken on some subset of AMD CPUs, which eventually was fixed by a microcode update. There’s a lot of good discussion in that issue about its uses, non-uses, and edge cases, with a good coverage of a lot of points of view on the subject.