Hacker News new | ask | show | jobs
by ng12 3147 days ago
I don't understand your argument -- wouldn't it follow then that Vue devs converge on learning VueX? VueX is very similar to Redux, I don't see how that's a point in Vue's favor if our metric is time spent learning.
1 comments

It's roughly a bajillion times easier to learn. And that counts for a lot.

You have to take yourself out of the "experienced React+Redux dev" mindset and put yourself in the shoes of "Experienced dev looking to invest in one of two ecosystems" mindset. Which one is the path of least resistance?

The point is, React+Redux people would love to believe that it's "Vue+VueX." But in reality, it feels like "just vue." A sword is stronger as a single piece, and Vue+VueX feels like a single piece.

It's up to people to learn both and decide for themselves, but my argument is simply this: it's a mistake to underestimate the traction Vue is gaining.

There's a strong temptation to blame the dev: They're not smart enough, they should have been able to pick up Redux easier, Vue+VueX is the same as React+Redux. But all I can do is report my experiences, and an honest survey of the ecosystem would lead us to conclude that Vue+VueX is far easier to learn without sacrificing any flexibility for your company in the long run.

I think you've made several assertions about Vue which reflect an inherent bias. VueX and Redux are _remarkably_ similar libraries and I think your assertion that VueX is easier to learn (egregious hyperbole aside) is a pretty weak argument.

To be clear: I like both React and Vue and am fundamentally skeptical of arguments that one is significantly better/worse/different than the other.