mshroyer

https://x.com/filpizlo/status/2053351119095791995

And "Rust let’s you corrupt memory / Fil-C doesn’t.":

https://x.com/filpizlo/status/2079253367587737841

These are false claims. The following compiles and runs fine with Fil-C, happily corrupting memory in a way that a safer language like Rust would not allow:

    #include <stdint.h>
    #include <stdio.h>
    
    struct Account {
            unsigned char name[8];
            uint32_t privileged;
    };
    
    void write_name(struct Account *account, size_t index, char value)
    {
            account->name[index] = value;
    }
    
    int main(int argc, char* argv[])
    {
            struct Account acct = {
                    .name = "foobar",
                    .privileged = 42,
            };
    
            write_name(&acct, 8, 1);
    
            printf("privileged = %d\n", acct.privileged);
            return 0;
    }

FYI, the existing Framework 13 Intel motherboards do support Thunderbolt 4: https://knowledgebase.frame.work/usb-port-definition-matrix-... There's an additional, optional retimer update that's officially Thunderbolt certified, but I haven't bothered with that because my Thunderbolt dock was already working: https://knowledgebase.frame.work/en_us/framework-laptop-bios...

In the acknowledgments section,

> Thanks also to Ray Bradbury.