4 ms·
Ok, so I've built stuff in Vue.js, React and Angular and I need to understand all the rage. I mean, Vue.js is just like Angular but with less features? I like t
by Kiro 10y ago
Ok, so I've built stuff in Vue.js, React and Angular and I need to understand all the rage. I mean, Vue.js is just like Angular but with less features? I like that it's slimmer, don't get me wrong, but I just don't understand the "woah, Vue.js is the shit!" when we've had Angular for so long.
I put this in contrast to React where it's a completely new concept.
- memonkey 10y agoWhoa! Thank you for this. I think this is exactly what I am thinking. I have done exactly what you did and I'm trying to figure out what the rage is as well. I want to find a framework that works for me without all the intricacies and nuances of something so complicated... something that gives me the errors that I need to know to debug the issues I'm having.
- welanes 10y agoPersonally, it's the lack of pain when getting started. React has an unfamiliar syntax and the cognitive load to "get it" while not huge, was going to take time. Angular seemed fine but a little verbose and a new version was coming out that diverged from Angular 1 in a way that caused more than a few headaches, apparently. With Vue.js I read through the excellently presented guide and started building my app, instantly. I view building an app (or app based business) as lego. Join all the pieces together and yay, you have a product. Vue's component based approach matches that perfectly. Then you look at the small number of open issues on Github, the large number of Vue.js components available (https://github.com/vuejs/awesome-vue https://github.com/vuejs/awesome-vue), the well-thought-out error messages, documentation and chrome dev extension. That adds up to a refreshingly pain-free dev experience. As I've mentioned here before, it's so simple it feels like cheating.
- jnbiche 10y ago> React has an unfamiliar syntax and the cognitive load to "get it" while not huge, was going to take time. Maybe because I have a background in functional programming, it only took me an hour or two to get React itself. The basic concept is dead simple declarative programming: declare a React component some state, and it renders it. The lifecycle adds a bit more to understand, but most of us have dealt with lifecycles somewhere, whether in WordPress, Android, etc. And then there's local component `state`. But that's it. However, what's commonly accepted as the React ecosystem (meaning webpack, babel, flux/redux, eslint, sometimes flow etc.) takes a lot longer to understand. And can be quite (perhaps overly) complex.
- a-saleh 10y agoIt might be that productivity and maintainability of "more polished" and "simpler" beats "new concept". It beats angular, because it is both more polished and simpler. It beats React, at least in short term, because it is both simpler and you don't have to learn new concepts. People betting on react are hoping that after they internalize those new concepts, it would make it simpler/more maintainable for them in the long run.
- kls 10y agoReact is not a new concept, it is moving back to tried and true basics, honestly it's one of the few JS frameworks that has been built by people that learned from past mistakes, from former implementations: https://bitquabit.com/post/the-more-things-change/ https://bitquabit.com/post/the-more-things-change/
- losvedir 10y agoAgreed, I feel like I'm missing something here. I had thought that react "won" over angular because people generally preferred one-way data flow vs. angular's two-way data bindings. At least for me, that's one of the biggest reasons why I feel like I understand react better than angular. It's a little verbose at times, but it does make it pretty easy to follow. And it looks like Vue.js is a two-way data binding framework? I won't write it off without trying it, but that's a point against it for me.
- YCode 10y agoIn React the idea that the state controls the app and as long as you maintain control of your state your app becomes nearly deterministic is powerful. In this way Vue or more specifically two-way data binding struck me as a step back. Or am I misrepresenting Vue?
- applecrazy 10y agoActually, Vue has one way binding by default when dealing with Components, in that way, it's very similar to React: http://vuejs.org/guide/components.html#One-Way-Data-Flow http://vuejs.org/guide/components.html#One-Way-Data-Flow
- snuxoll 10y agoVue.js is multi-paradigm. It supports the MVC model of Angular/Ember/Etc. but with Vuex you can use the Flux model encouraged by React or the Elm Architecture, and it works great.