Vue

“so long as your needs largely overlap with the community, the benefits of working with the community are real”

“It was always pretty easy to make a wrapper component and hook whatever library up to the lifecycle”

“It ported a Rails 7, Vue 2, vuetify 2, vuex app to Rails 8 (ok, easy, I did it myself at least once), Vue 3”

“with Vue SSR. That all enables me to write old-school MVC with Vue as a template engine for views.”

“I kind of like Svelte and Vue in that regard, where your CSS, HTML and JS lives all together”

“I'm surprised how good Vue Vapor mode is from the performance comparison table.”

“it just works, behaves as you'd expect, and doing anything just isn't that difficult”

“bloated Vue/React shops I've seen where every change requires a 10 second frontend compile pipeline”

“bloated frameworks like react, angular and vue with their dreaded hydration and ssr approaches”

“don't use React, Vue or Svelte (and similar), it's horrible and always slow”

“I am so very grateful for the beautiful frameworks/tooling Evan and his team have cranked out over the years.”

“Vue has always handled things well when dealing with cross framework stuff”

“The non-backwards-compatible move from Vue 2 to Vue 3 burned a lot of the current devs”

“I prefer the Vue model where the component runs once and sets up its reactive tree.”

“The same kind of bugs don't happen in Vue because the framework handles them for you.”

“Vue templates mean learning Vue's custom syntax for if statements, loops, dynamic attribute syntax”

“solves them worse if you have to learn all their proprietary files and DSLs instead of JSX”

“The original component architecture with the html template, JavaScript state and css styles in vue was so nice.”

“Vue and Svelte typically require compilation steps and framework-specific tooling”

“Vue provides a computed feature that acts as a buffer layer between the view and the state”

“the framework continues to improve performance without forcing you to adopt new syntax”

“I've primarily used Vue.js where most state is relatively local and we don't try to re-render the world on every input.”

“One thing I've been very glad for in all the years I've been using TS+Vue is that I'm not forced into JavaScript's craptastical OOP system”

“This helps developers build complex UIs faster, but it adds extra memory and runtime overhead compared to simpler approaches.”

“Reactive UI (in the sense of React, Vue, ...), the greatest innovation in UI programming ever”

“The thing I enjoy the most about writing UIs with Vue 3 is that I'm not forced into JavaScript's insane OOP mechanics”

“Having to keep upgrading and changing libraries just cause the devs of the libraries get bored should not be a thing.”

“I've yet to see a large Solid/Vue project that is more performant than React.”

“Vue, Svelte, and Surface manage to do this without forcing you to inline all your styles”

“Vue interops better with webcomponents and non-framework code than React in my experience.”

“the "big ones" (angular/react/vue/svelte) have been around for YEARS at this point and IMO mostly stablized”

“stuff like custom directives that are nonstandard html, not as explicit about event handling and data flow”

“Due to how Vue 3 works, it's even easy to share state & routing between them when required.”

“Vue's downside is not being able to store off template fragments in variables.”

“Vue's granular lifecycle hooks which give you all the control you need without workarounds”

“Your examples, Vue and Svelte, give you build-time predictable output with scoped CSS without Tailwind.”

“Without its "progressive" affordances, I don't think I would have gotten anything off the ground.”

“Its API so far feels like an acceptable cognitive overhead over the raw DOM.”

“Vue is much easier to tame, it's reactivity model does not require a PhD in hooks”

“in Vue3, if a ref is only used in an html tag the compiler will optimize it to not recalculate the whole virtual dom.”