With vanilla JS, I would have to add the item to the list, then get the parent element, then create a div containing a bunch of hardcoded stuff, give it an id, keep track of that id, insert the item, then when I remove the item I would have to remove the item from the list.
That could double the amount of cod e needed in most stuff I do.
Overall, Vue is honest. React is decidedly not.
It's not a framework I would use by choice, I've been working with Vue for many years, and I've also done some minor Lit and Svelte work.
But it does seem like it's still very widely used, so I assume there must be something about it people really like.
At the very least, the ecosystem and legacy stuff seems like enough to justify using it on some projects, although Vue seems to have caught up.
this is very dangerous and flawed reasoning. There are many examples of where this goes horribly wrong. One of the nice ones is something called normalcy bias. but hey, let's just vote to murder Socrates again because he acknowledged that he was intentionally triggering us as an act of love.
I assume all the devs at the large companies know what they're doing with react, since I rarely hear that much complaining, so I suppose it's well suited for very large projects.