Post

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.

0 reposts2 likes

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.

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.