Post

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

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.

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.

For context, they work really well outside of writing code outside of framework "template" logic. Like they're super powerful at fixing regexes and mundane tasks that would take me 20mins, but now takes me a few mins.

Isn't it at this point better to just vanilla the whole thing? Let AI worry about framework ux. In the context of AI training, standards are a safer bet than ever changing frameworks.

how old is the last syntactic change that you actually _really_ use these days? (std) libraries change all the time, i dont care about that so much. although i'll say this, at least for JS, they're evergreen backwards compatible. and that goes a long way. can't say the same for libraries

Evergreen won’t get you far though. Without libraries you’ll just create no better than jQuery fluff. CSS standards have changed dramatically over the last year too

I think the AI game changes that. Cross browser compat is less relevant today than it was in the jquery days. Same for base line browser (or node) api's. Lib UX is less relevant when it's the AI doing the coding. I think AI's opened space for a new breed of libraries; vibe friendly libraries. No?