Post

I still think there's a missed opportunity to create a frontend framework that works really well with AI tooling.

Personally I think WebComponents could really be such a huge leap forward for AI. A single layer versus having to understand how code aggregates to the broader HTML. Especially with invokers / commands: now we have some standards with which we can wire the web declaratively!

I thought Catalyst was very very good for this before. Basically maintenance mode now. But @keithamus.social went on to do a huge amount of the work to spec out Invokers / Commands so yay for that. github.github.io/catalyst/

A crafty custom element (CE) lib could be portable. CE libs that have SSR have a different output on the server (strings instead of DOM, using a lightweight DOM phonyfill, or no fill at all). This can be made to output to native components instead, if desired. Just the same a Svelte, Vue, or Solid.

I fail to see what structure or content would make any other approach significantly different. Everyone is gleeful to hate on the DOM but we have yet to see a single competitor come anywhere near it.