Netflix HBO Max will be amazingly easy to remember name.

Then of course LLM's write TypeScript against the functions defined, that's what they are now doing with Python, but without input and output types it will be always worse than TypeScript.

I've been following MCPs too, most of those could be replaced with "d.ts" files, like:

"my-order-system.d.ts"
"some-cool-functions.d.ts"

It would contain just the API, and LLMs seem to be good at interpreting TypeScript interfaces.

It doesn't have implementation of course, but that is the point.

There is a neat hack though, defining interfaces and then using `satifises` with import("./foo"). It's a bit cumbersome though.

Yes, it can easily take ~50GB of memory with just ~5 projects open. I keep trying all the WGPU/GUI crates, and I've nearly OOMed myself too.

I liked that. Best part was where Matt screwed the physical demonstration at the end... doing it on a slippery surface was almost deemed to fail.

React / Svelte community etc, seems to be in eternally stuck with fiddling state management and bundling. It's so frustrating, where as WordPress seems to do everything worse, but deliver user experience that is "good enough".

Is it shaped like an origami snowflake?

It's now over 80k, as someone called Murasaki donated $10 000, with a note: "From an old man, so young kids can maybe dream of something big. Please make it awesome."

Smithay Client toolkit is just an example how to run a Wayland window, so it doesn't have font rendering loaded etc. But it can render some stuff anyway.

One would think there is a way to minimize memory usage from 100MB...

ease at which Claude generates tests, I figured, I don't even commit those for the moment. Not sure what good approach is.

In closed source app, one does commit tests, but this is my own project so whatever