If you can fund it, I’ll sign up as a moderator.

This is a helpful perspective. Many would benefit from a longer form explanation of this. There is a LOT of non-browser stuff that people don’t think about.

Maybe there should be 3 adoption options.

1. Browsers
2. Other public pki, longer adoption window
3. Custom, private pki

The grey beards have always been vibing, getting high on their own supply.

In many states companies are still putting this stuff in employment contracts, even though they know it’s doubtful that they will ever litigate it. It’s intimidation, bullying, or just holdover from the past. Arguing to change at time of hire puts hiring timeline at risk… so it continues.

I was just looking at the oxide site and wishing there was a web framework for generating TUI-like web components, using ascii.

Is it worth making APIs from step functions? How to handle things like status codes, headers, errors, etc? Also, one step function per route? Examples?

Macintosh plus. I sometimes visited Dad at work, played Dungeons of Moria (roguelike). Got to level 49, and got stuck. Very few games did I not complete as a kid, and this stuck with me.

All these AI hardware posts bring me right back to 1999. Built a PC using the first Athlon and first GeForce. Everyone reported problems similar to these, but I got lucky and bought the only mobo that had updated drivers that actually worked.

Check out TypeSpec?

To go even more in the other direction, check out TypeSpec. I actually am warming up to this pattern. Design first, then generate from that.

I want TypeSpec to generate my OpenAPI, my Zod, my TypeScript types and my Hono Router.

Astro starlight is super nice!