Post

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/

I don't think web components are a good enough abstraction. If you're leveraging AI, you definitely want to be working with a higher abstraction so that it can make your application portable. The DOM should be purely seen as one of many render targets IMO.

The amount of times I've had to correct AI output because it doesn't quite understand control-flow around JSX is astonishing. I still feel like JSX in its current state isn't the ideal thing we should be using in 2025.

Svelte 5 fairs better, but then AI gets confused around template modules vs non template modules when it comes to runes. This might get better if Svelte opens up declaring state and other bits of logic in control-flow, but it's still not great.

Some carefully trained ember models do well with the component syntax. (Which is good because testing with inline components is amazing (jsx has this as well, and no ane else does?) Specific apis are still occasionally hallucinated tho, even if syntax is correct. And hopefully one day docs ..

I should probably play around with Vue and Solid with Cursor/Claude Code more to see how they fair. So far it's been a really frustrating experience to say the least, I'm just having to correct everything that they suggest changing each time.