5 ms·

If you already know react and are happy using it, then there's no reason to use Vue. But if (like me) you were never quite able to figure out how to use React

If you already know react and are happy using it, then there's no reason to use Vue. But if (like me) you were never quite able to figure out how to use React (especially all the build tooling that's suggested in every tutorial), then Vue is worth a look as it's incredibly simple to get started with and easier to learn. I find it especially appeals to people coming from a place of familiarity with html and css (whereas react seems to appeal to people with more of a straight-up programming background). YMMV

ng12 10y ago
> easier to learn I think this is problematic because people don't differentiate between React and the React ecosystem. Plain old React is just as easy (probably easier) than learning Vue. I always recommend the official React tutorial (https://facebook.github.io/react/tutorial/tutorial.html https://facebook.github.io/react/tutorial/tutorial.html) before even thinking about Redux or Webpack or whatever.
- therealmarv 10y ago
  That's true. React itself is also clean and simple... but things tend to be more complicated in React, the ecosystem when you go to the SPA direction.
  - zyxzkz 10y ago
    I sorta hate that React is so simple and the ecosystem is such a clusterf*ck. I wish they came out with a storage/persistence system as simple conceptually as the renderer. Maybe that's a lot to ask for though. React by itself gives me blue balls.
    - zmmmmm 10y ago
      I have a theory that every project eventually approaches a level of complexity reflecting the level at which a moderately intelligent person can't understand it any more. I think of it as a "complexity budget". So if you start with something simple (say, React) then people will just invent more layers of complexity around it to solve whatever the next layer of problems is (Redux, Webpack, etc). And they won't stop until the complexity budget is all used up.
    - spion 10y ago
      There is one, and its called MobX: https://mobx.js.org/getting-started.html https://mobx.js.org/getting-started.html
  - deleted 10y ago
    [deleted]
- jordanlev 10y ago
  Of course it's subjective, and different people coming from different backgrounds / experience levels find different things easier than others. But... that tutorial you say you like to show people utilizes jsx, which needs to be compiled with something (right? Or does react do the compilation automatically at runtime now and I missed that memo?). And for people coming from a place where they are very comfortable and familiar with html and css, and maybe a light sprinkling of jquery on top, Vue is way more approachable than the tutorial you linked to.
  - spicyj 10y ago
    create-react-app is our recommended way to build simple React apps (and some complex ones). It has no configuration and is designed to be very easy to set up. (My understanding is that Vue templates also need to be compiled -- is that incorrect?) I wrote the tutorial. Could you give any suggestions on how I could make it easier to get into?
    - tomstuart 10y ago
      Not the OP, but I'll state the obvious on their behalf. The number one thing that you (and Facebook) could do to help people learn React, and combat the perception that it requires overly complex tooling, is write a tutorial that shows how to use React entirely in-browser without any build toolchain. A static HTML file, some <script> tags pointing at a CDN — done. No distractions, nothing to download, nothing to install, nothing to run, just a JavaScript library that makes it easier to write view templates. It would make it even easier to get into if that tutorial were written entirely in ES5, but you could use babel-standalone if you felt that JSX and ES6 were important enough.
      - spicyj 10y ago
        Thanks for replying! Our official tutorial was actually exactly that for _years_, but it didn't seem to help much. I get the sentiment though and maybe we can find another way to make it work.
ergo14 10y ago
Then you should look at Polymer. It is just DOM nodes (custom elements_, you can however compose complex applications with it without any trouble. I feel its very straightforward way to build applications and most parts of it are handled by browser API's. It seems like a perfect middle ground between react/angular 2/vue - and you can still throw in redux or uniflow-polymer if you want.
- rk06 10y ago
  The major problem with polymer is that it does not support npm. It seems polymer 2 will support yarn. but until then, it is a no go.
  - ergo14 10y ago
    whats the problem with using bower (apart being "legacy"), it suddenly stopped working? Not all packages are on npm, i use mix of npm and bower without issues. When the JS community comes up with better npm will people stop using packages on npm?
thewhitetulip 10y ago
I had the same problem, couldn't figure out how to use React, I started learning VueJS and in a week I had built a fully working app, https://github.com/thewhitetulip/Tasks-vue https://github.com/thewhitetulip/Tasks-vue I started to write this tutorial, an example based guide, https://github.com/thewhitetulip/intro-to-vuejs https://github.com/thewhitetulip/intro-to-vuejs

ng12 10y ago

> easier to learn I think this is problematic because people don't differentiate between React and the React ecosystem. Plain old React is just as easy (probably easier) than learning Vue. I always recommend the official React tutorial (https://facebook.github.io/react/tutorial/tutorial.html https://facebook.github.io/react/tutorial/tutorial.html) before even thinking about Redux or Webpack or whatever.

therealmarv 10y ago
That's true. React itself is also clean and simple... but things tend to be more complicated in React, the ecosystem when you go to the SPA direction.
- zyxzkz 10y ago
  I sorta hate that React is so simple and the ecosystem is such a clusterf*ck. I wish they came out with a storage/persistence system as simple conceptually as the renderer. Maybe that's a lot to ask for though. React by itself gives me blue balls.
  - zmmmmm 10y ago
    I have a theory that every project eventually approaches a level of complexity reflecting the level at which a moderately intelligent person can't understand it any more. I think of it as a "complexity budget". So if you start with something simple (say, React) then people will just invent more layers of complexity around it to solve whatever the next layer of problems is (Redux, Webpack, etc). And they won't stop until the complexity budget is all used up.
  - spion 10y ago
    There is one, and its called MobX: https://mobx.js.org/getting-started.html https://mobx.js.org/getting-started.html
- deleted 10y ago
  [deleted]
jordanlev 10y ago
Of course it's subjective, and different people coming from different backgrounds / experience levels find different things easier than others. But... that tutorial you say you like to show people utilizes jsx, which needs to be compiled with something (right? Or does react do the compilation automatically at runtime now and I missed that memo?). And for people coming from a place where they are very comfortable and familiar with html and css, and maybe a light sprinkling of jquery on top, Vue is way more approachable than the tutorial you linked to.
- spicyj 10y ago
  create-react-app is our recommended way to build simple React apps (and some complex ones). It has no configuration and is designed to be very easy to set up. (My understanding is that Vue templates also need to be compiled -- is that incorrect?) I wrote the tutorial. Could you give any suggestions on how I could make it easier to get into?
  - tomstuart 10y ago
    Not the OP, but I'll state the obvious on their behalf. The number one thing that you (and Facebook) could do to help people learn React, and combat the perception that it requires overly complex tooling, is write a tutorial that shows how to use React entirely in-browser without any build toolchain. A static HTML file, some <script> tags pointing at a CDN — done. No distractions, nothing to download, nothing to install, nothing to run, just a JavaScript library that makes it easier to write view templates. It would make it even easier to get into if that tutorial were written entirely in ES5, but you could use babel-standalone if you felt that JSX and ES6 were important enough.
    - spicyj 10y ago
      Thanks for replying! Our official tutorial was actually exactly that for _years_, but it didn't seem to help much. I get the sentiment though and maybe we can find another way to make it work.

ergo14 10y ago

Then you should look at Polymer. It is just DOM nodes (custom elements_, you can however compose complex applications with it without any trouble. I feel its very straightforward way to build applications and most parts of it are handled by browser API's. It seems like a perfect middle ground between react/angular 2/vue - and you can still throw in redux or uniflow-polymer if you want.

rk06 10y ago
The major problem with polymer is that it does not support npm. It seems polymer 2 will support yarn. but until then, it is a no go.
- ergo14 10y ago
  whats the problem with using bower (apart being "legacy"), it suddenly stopped working? Not all packages are on npm, i use mix of npm and bower without issues. When the JS community comes up with better npm will people stop using packages on npm?

thewhitetulip 10y ago

I had the same problem, couldn't figure out how to use React, I started learning VueJS and in a week I had built a fully working app, https://github.com/thewhitetulip/Tasks-vue https://github.com/thewhitetulip/Tasks-vue I started to write this tutorial, an example based guide, https://github.com/thewhitetulip/intro-to-vuejs https://github.com/thewhitetulip/intro-to-vuejs