This explains our thinking around <model> more than the "explainer" did.

Please try to avoid gating functionality on the string name of a GPU/vendor. You're locking out users who, in the future, get better hardware that doesn't match the name. There is always better hardware coming, and content is rarely updated. github.com/gpuweb/gpuweb/…

Running linux in a VM on macOS (there is also a document for macOS on macOS) developer.apple.com/documentation/…

WebKit's proposal for animations (screen updates) with a variable frame rate: github.com/WebKit/explain…

Surely people who miss-spell "colour" as "color" should also miss-spell "blue" as "ble". #csscolor5

Anyone got tips for converting a USDZ file to a glTF? (Not the other way around - I have that sorted)

Today I am proud to announce the formation of the World Wide Web 3.0 Consortium (W3C3). Meetings will take place in the metaverse. Member dues payable by Non-Fungusable Tokens. Operational structure will be a Decentralised Automobile Organisation.

Exciting!

2021: Metaverse 2022: Metachorus

Have you been having out-of-memory issues with canvas elements on iOS? I'd love feedback on how to best address the problem (I've given a few options): github.com/WebKit/WebKit/…

Reminder: @samweinig explained a lot of the thinking behind <model> here: x.com/samweinig/stat…

I can't find the tweet now, but someone suggested <model> was a way to own the Metaverse. 1. If you wanted to own something why would you try to develop it as an open standard that works with other technologies? 2. I don't know what the Metaverse is.