No OP, but I've also used Angular, React, Vue, Solid and Svelte in real world projects and my default choice is Vue, because it's on par with Solid and Svelte (and with Vue Vapor those three are basically the same) but with the larger ecosystem (vuerouter, vueuse, nuxt, nuxt-ui, primevue, nuxt-content, ...). I must also say that React was by far the most unpleasant and unproductive to use.
I keep reading unpleasant without any arguments. React is simple by nature, what made it unpleasant and unproductive?
Granted I mostly do work on Shopify apps, so most of the heavy work has been done for me, I just put components together. This works fine, and I'd rather do this in React than e.g. Angular due to the small scale of the apps. Then again web components would've also been fine.
I've stopped being interested in frontend frameworks after Vue/React but I agree. I find JSX with its mix of JS and HTML rather weird. I prefer Vue's abstractions and the readability of its template syntax. It's also rather easy to add it without a compilation step for some interactivity or app-like behaviour on a web page. More complex applications using a bundler work as well as our company is developing and maintaining a 100k LOC webapp too. In the end I'd prefer it if browser would provide a native API for two-way binding, components or templating and maybe state management as well.
I have by far the most experience with Vue, but I'm a bit ambivalent about Vue3, and often still write in a Vue2 style.
Svelte looked pretty nice, but before I had a chance to really proficient, that codebase got re-written in Solid. Solid seemed to have the benefits of React-compatibility without so much brain-hurt.
WuxiFingerHold|5 months ago
unknown|5 months ago
[deleted]
ramon156|5 months ago
j1436go|5 months ago
stevage|5 months ago
Svelte looked pretty nice, but before I had a chance to really proficient, that codebase got re-written in Solid. Solid seemed to have the benefits of React-compatibility without so much brain-hurt.