3 ms·
I wonder if this is overstated. Anecdotally, we use Vue at work and Claude and Codex handle it just fine. I'd expect Vue to be the third best-represented after
by crabmusket 22d ago
I wonder if this is overstated. Anecdotally, we use Vue at work and Claude and Codex handle it just fine. I'd expect Vue to be the third best-represented after React and Angular, but even then, we feel absolutely no need to change things up to get better results.
Vue's reactivity is quite similar to Solid's, AFAIK, so I wonder why there would be so many issues with Solid.
We have also started to have success getting LLMs to create custom lints for us to handle tricky edge cases. For example, discovering deep watches or tricky interactions - you can get a fair way asking an LLM to create a lint using a codemod library (in our case, vue-morph) that fires on this example but not on that example.
- zmmmmm 22d agoVue had a good tenure as a solid #2 to React, so I think it probably has got a lot of representation in training data. Things really splitered after that but it got a good foothold.
- gunalx 22d agoThe problem I see with vue is what vue patterns are you using. And the llms may be trained on more outdated ones more than current practices.
- zmmmmm 22d agoAgree. It wasn't as drastic but I think Vue did the 2=>3 update at an unfortunate time. They lost a lot of users along the way but they also confused a lot of the LLM training too, I am sure. Still, I have great success with it, especially with Typescript.