One of the things that puzzle me the most about our industry is why devs keep choosing React over Vue.
It’s bloated, produces poor UX, makes bigger demands on tooling, respects web standards less, and has significantly poorer DX…
Is it just ecosystem? But then how did it get there?
Is it because it came out of Facebook?
Is it because some of the frameworks around it actually have good DX?
Something else?
I …don’t get it. 🤷🏽♀️
See also, @slightlyoff’s controversial post: https://infrequently.org/2023/02/the-market-for-lemons/
@leaverou If I want to slap the debugger onto how Vue decides to render a template, how do I do that? Looks like I can attach to a callback, but I don’t see an easy way to monitor the rendering of <div :class="{ active: isActive }"></div>.
React makes rendering of components very explicit, which makes it easy to slap a debugger on it when it starts to go off the rails. I haven’t used Vue but I have used Angular, and my biggest grouse with it was all the implicit behavior that you couldn’t really see without building Angular from source and understanding its implementation. I find, generally, React makes that way simpler because it externalizes generation of component structure into the rendering functions.
@mtomczak You can use the Vue devtools, or a computed property. If it's on the app instance, I sometimes just expose it on globalThis temporarily just so I could play with it in the console