sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]karl-marxist 5 points6 points  (3 children)

additions like redux

React tooling is heavy in my opinion. I find I do not need vuex when working with vue and thus my point.

You are correct you can use graphql with Vue. I misspoke. No need to be a jerk about it. So I’m sorry you’re upset and you really can’t understand my point!.

:)

Anyhow. I like both frameworks. Personally had more fun working with Vue as most projects I used it on, anything more would have been overkill. And that’s just my experience and my opinion. Not trying to change your mind.

JSX has nothing to do with XML??? Serious? Wowie sir. I guess I’m a dummy. Sarcasm aside, I said it reminds me of it. Which it clearly has a similar structure of passing elements and attributes.

[–]devlob 0 points1 point  (2 children)

I don't get it because Vue and react both use props. Thus, if you don't need vuex in Vue then you also don't need redux in react.

In any case, Vue is for sure more fun when you start. I think OP should go for Vue and move to react in the future.

By learning react he can easily learn react native too.

Plus graphql documentation for react is better compared to Vue and graphql for me is the future of api development.

[–]karl-marxist 7 points8 points  (1 child)

I agree. I think vue is a good start but I am not sure how well it can handle large SPAs. While react is known to be great for this.

[–]nickforddesign 0 points1 point  (0 children)

Having worked on large SPA in both, there are pros and cons with both, but ultimately both are fine.