logoalt Hacker News

digitaltreestoday at 2:36 AM4 repliesview on HN

But why over vue? My biggest frustration has been how vue ends up moving in the direction of react. The original component architecture with the html template, JavaScript state and css styles in vue was so nice. Even the data fetching a url in the component was so intuitive.


Replies

robocattoday at 5:31 AM

A bit out of date, but I like the point-of-view of "The single most important factor that differentiates front-end frameworks" : https://mjswensen.com/blog/the-single-most-important-factor-...

lwansbroughtoday at 4:02 AM

I definitely sympathize with the feelings about the Composition API. Though I’ve moved past it because looking at React’s visible complexity (useMemo, useEffect - which apparently have changed names again since I last looked) - Vue has clearly chosen a superior API design.

show 1 reply
hajiletoday at 3:50 AM

Vue doesn't solve problems better than React (and solves them worse if you have to learn all their proprietary files and DSLs instead of JSX), so there's not much of a reason to switch.

The real discussion would be between React's vdom and something like Solid's signals.

show 1 reply
synergy20today at 3:01 AM

I'm using Vue and do not feel it's becoming react

show 1 reply