6 ms·

I have used Vue in multiple projects, after having previously made multiple attempts to learn React. Coming from Angular 1 (too frustrated to bother learning An

by sjroot 9y ago

I have used Vue in multiple projects, after having previously made multiple attempts to learn React. Coming from Angular 1 (too frustrated to bother learning Angular 2), React was my initial preference due to name recognition and the size of its developer community. However, the steep learning curve ultimately prevented me from being productive. On the other hand, Vue's lightweight nature, as Evan describes, ended up being a breath of fresh air. I also find that the Vue component files help bring structure to more complex applications. I wouldn't say that Vue trumps React, however. At this point they are equivalent forces targeting two different audiences.

nolite 9y ago
Hanks for the review! I feel I have the same experiences as you in trying to learn react. What would you say the different audiences are for the two? And what drawbacks does vue have that prevent it from trumping react?
forgot-my-pw 9y ago
I much prefer Angular's and Vue's templates over JSX.
- ng12 9y ago
  Why? I love JSX because it's a single source of truth -- 100% of the logic is in JSX. You never have to hop back and forth between the template and code to figure out how something is rendered.
  - devoply 9y ago
    sort of like the good old days where you did have to hop back and forth between javascript, css, and html. it was all in one file all inline.
  - exclusiv 9y ago
    I think it's definitely a preference thing. Putting one language in another always feels dirty to me. On the other hand, many people feel sprinkling tags all over html is dirty and that the click handlers (v-on:click or ng-click) and other tags smell of yesteryear. For workflow I like to offload html/css production and when I get it back I can add VueJS or AngularJS tags to it and get busy. I don't have to chop it all up nearly as much. It seems much easier to have junior developers jump on VueJS templates too. While I prefer VueJS or AngularJS depending on the project, I'll probably try React on an upcoming project to get a feel for it and give it a shot.
    - tomwilson 9y ago
      I agree it's a preference. But to me, the custom tags for loops etc is even more putting another language inside another than JSX is.
      - exclusiv 9y ago
        Good point. I think that probably gets more of a pass because we used to have a lot of inline JS in the past. Doing it the other way was a lot sloppier before because HTML was such a chore to include in JS.
jug 9y ago
JSX doesn't feel "right" to me, it feels like it's taking Javascript and making it into what it isn't, just for convenience (everything in one place), because the JSX-free option of React at least seems terrible. I'm not sure if that says more about the limitations of Javascript or the design choices of React. Somehow, Evan You managed to design a perfectly clean, high performing alternative that follows common development practices, and still supporting componentization for growing projects. As for me and my workflow, I tend to gravitate towards the options impacting my workflow the least (where preprocessors will invariably do so) and getting me up and running the quickest, while not sacrificing good programming practices. I think VueJS fits that niche pretty well indeed.

by sjroot 9y ago

nolite 9y ago

Hanks for the review! I feel I have the same experiences as you in trying to learn react. What would you say the different audiences are for the two? And what drawbacks does vue have that prevent it from trumping react?

forgot-my-pw 9y ago

I much prefer Angular's and Vue's templates over JSX.

ng12 9y ago
Why? I love JSX because it's a single source of truth -- 100% of the logic is in JSX. You never have to hop back and forth between the template and code to figure out how something is rendered.
- devoply 9y ago
  sort of like the good old days where you did have to hop back and forth between javascript, css, and html. it was all in one file all inline.
- exclusiv 9y ago
  I think it's definitely a preference thing. Putting one language in another always feels dirty to me. On the other hand, many people feel sprinkling tags all over html is dirty and that the click handlers (v-on:click or ng-click) and other tags smell of yesteryear. For workflow I like to offload html/css production and when I get it back I can add VueJS or AngularJS tags to it and get busy. I don't have to chop it all up nearly as much. It seems much easier to have junior developers jump on VueJS templates too. While I prefer VueJS or AngularJS depending on the project, I'll probably try React on an upcoming project to get a feel for it and give it a shot.
  - tomwilson 9y ago
    I agree it's a preference. But to me, the custom tags for loops etc is even more putting another language inside another than JSX is.
    - exclusiv 9y ago
      Good point. I think that probably gets more of a pass because we used to have a lot of inline JS in the past. Doing it the other way was a lot sloppier before because HTML was such a chore to include in JS.

jug 9y ago

JSX doesn't feel "right" to me, it feels like it's taking Javascript and making it into what it isn't, just for convenience (everything in one place), because the JSX-free option of React at least seems terrible. I'm not sure if that says more about the limitations of Javascript or the design choices of React. Somehow, Evan You managed to design a perfectly clean, high performing alternative that follows common development practices, and still supporting componentization for growing projects. As for me and my workflow, I tend to gravitate towards the options impacting my workflow the least (where preprocessors will invariably do so) and getting me up and running the quickest, while not sacrificing good programming practices. I think VueJS fits that niche pretty well indeed.