He never actually spoke about type inference in my presence. He did teach me CCS (pi-calculus predecessor) a couple of years later, by which time I could appreciate him.

I did some work for Apricot at their Glenrothes factory around 1985-87. In my memory they went heavier on GEM than Windows. I never saw an Apricot running Windows prior to the PC-compatible models.

(Wondering if you never heard of it or if you don’t consider it commensurate).

I’d like to adjust this understanding. Kafka is the big new thing, but it’s optional. The previous way using gRPC still works.

I work on Mimir and other things at Grafana Labs.

1. In the cloud, it can be difficult to know the NUMA characteristics of your VMs. AWS, Google, etc., do not publish it. I found the ‘lscpu’ command helpful.

2. Tools like https://github.com/SoilRos/cpu-latency plot the core-to-core latency on a 2d grid. There are many example visualisations on that page; maybe you can find the chip you are using.

3. If you get to pick VM sizes, pick ones the same size as a NUMA node on the underlying hardware. Eg prefer 64-core m8g.16xlarge over 96-core m8g.24xlarge which will span two nodes.

    Apple I - July 1976
    Commodore PET - January 1977
    Apple II - June 1977
    C64 - January 1982

All four used the 6502.