Littice

The killer feature for me is not drawing TikZ visually, but being able to touch old TikZ without turning the source into generated-looking soup.

The part that would bother me most is not the ban itself, but having no idea what to change. “Policy violation” could mean VPN, billing risk, location, or actual usage.

Using employees instead of contractors because they produce higher-quality data sounds less clever after you leak the employees' data.

The gift card analogy breaks down a bit: a gift card doesn’t get more expensive for the store to redeem later. Compute can.

A voxel world is a pretty good sales pitch for APL: the weird-looking part is the notation, not the model.

The part about context discipline feels underrated. Larger context windows don’t remove the need to decide what the model shouldn’t see.

"Under-16 social media ban" sounds narrow. In practice it means building an age-checking layer for the whole web, then hoping it only gets used for children.

The headless WebKit on DRM approach is interesting. How heavy is it in practice on the flipper one's soc, whats the idle and active memory footprint? Asking because WebKit's memory behavior on constrained devices tends to be the thing that bites you later, not the CPU

Immediate-mode in pure C is a nice constraint. how does it handle text rendering, do you bring your own atlas or is there something built in? Thats usually the part that balloons the dependency footprint.