> it took significant effort to e.g. get clang to compile the Linux kernel (needing patches in both projects).

Tell me about it. :-)

I spent a bit of time implementing parts of a C runtime for the brief tenure I had maintaining LLVM's libc. I quickly came the realization that a lot of the interfaces that made it all the way to standardization were trash. How the language is standardized is still comical to me. I agree with TFA that C style strings are trash.

In this day and age, the value of C standard library is approaching zero. Is is basically an unfirm looping trajectory of CS thought left over 50 years. That amount of code can be recreated pretty quick today. So why bother. Unless it is a syscall or somehow specially treated by the compiler (memcpy etc), there is no special value in it.

Good then that Amazon sells it by the 55 gal drum then.

https://www.amazon.com/Passion-Lubes-Natural-Water-Based-Lub...

> This product is out of stock

Ah, shoot, there go my weekend plans. Bummer.

I find it ironic; George Orwell was English!

It's a shame we never got a package manager for C (or C++).

EDIT: perhaps I should have been clearer; by not having one early on, we now have multiple competing package managers, with no clear winner. Responses prove that point.

Although vcpkg is probably the most popular, I’m a fan of https://conan.io/center

Never used this? https://vcpkg.io/en/

A long time ago, I wrote a small chapter in a WebGL book on asm.js.

https://webglinsights.github.io/

It was fun to see the rise of asm.js, which was a precursor to Web Assembly. Some of the early demos were so cool to see; Unreal Engine running in the browser. :) Bitter sweet to see the sun set here, but it did lead to much better things.

Dig the posters in the background; I just saw Burning Ambition in theaters last week. Up the irons, Earth dog! Ghost opened for Iron Maiden a few years ago; I saw them all together in Oakland.

There was a recent class action suit against GM for this.

Interesting. This past weekend, I got a chance to speak with Corvette's chief engineer Josh Holder at Chevrolet's Corvette Corral for the IMSA race at Laguna Seca.

I asked him if we'd see an all electric Corvette in the C8 timeframe, or would have to wait until the C9?

He confirmed (to the group) there would not be an all electric C8.

GM has long done "crate" engines, where people swap their cars OE engine for one of GM's small block v8s (an "LS or LT swap") frequently found in Corvettes, Escalades, and probably Silverado/large trucks/SUVs.

Seeing an electric crate engine from GM shows me that they plan to do the same with an electrified power train. Cool.

It hasn't turned out that way with Ford, who's been selling the Mach-E motor for years. It's useless because they don't sell any of the other necessary hardware. A battery, for instance.

I run it in a docker container behind traefik in another container. Getting that wired up and working in podman was quite the challenge. Docker container mounts my media as read only.

i didn't have much trouble

    services:
      jellyfin:
        build:
          dockerfile: jellyfin.Dockerfile
        container_name: jellyfin
        group_add:
          - 44
          - 993
        environment:
          - TZ=<redacted>
          - JELLYFIN_PublishedServerUrl=<redacted>
          - DOMAIN_NAME=<redacted>
        ports:
          - 8096:8096
          - 8920:8920
          - "7359:7359/udp"
        volumes:
          - ./config:/config
          - ./cache:/cache
          - ./config/index.html:/jellyfin/jellyfin-web/index.html
          - type: bind
            source: /mnt/storage/Video
            target: /media
        restart: always
        devices:
          - /dev/dri:/dev/dri

the device and group_add were for integrated graphics passthrough for transcoding (very highly recommend if you're containerized)

i also recommend seerr to pair with jellyfin: https://seerr.dev/

my wife logs into the seerr ui with her jellyfin account, makes requests, they get grabbed by sonarr/radarr, which in turn place them in the correct library, and they're identified & labeled correctly on import