| > I think the issue is that people keep expecting something from React that React has specifically stated it does not do, which is handle everything. Ok, but people learning React - with no guidance from the library or its maintainers, as you said it's only the view - are going to search for "react how to route" or the like. They end up using things like react-router, and some of them run into problems like I did. You did ask originally what makes one easier to learn than the other. > to give people to freedom of choice to choose or omit other libraries or frameworks. [...] Those pieces of functionality were easy to implement on my own. And I listed some problems that I had using those other frameworks which were recommended to me. "Just do it yourself" isn't exactly helpful. > (Redux itself is incredibly small) Ok, but it has had some API churn as well - EDIT: I was wrong about this. See replies. There's definitely boilerplate that goes along with it. There are libraries that deal with that to an extent, but there are many. Which one does someone learning choose? > I remember working on Angular 1 projects... What's that got to do with Vue? Vue isn't Angular. > Personally, I think it's silly to use Vue. I mostly hear either minor grievances from the Vue crowd I gave you my examples. You seem to compare only the view layer functionality. I'm examining the ecosystem and preexisting examples of how to implement functionality, which is going to be important for someone new to the library. Of course you can write this yourself, but for people trying to learn React, only having the view layer makes it more difficult to figure out how to "implement it on your own". > I also don't think Flux was vague, it just lacked an implementation. Not having any public implementation is pretty vague! > There just seems to be a big fear in the JS community about writing code instead of pulling in a framework Well, again, my response was from the perspective of someone learning React and how one might architect a SPA using it. As stated, there was no official flux implementation in the beginning, just a diagram from Facebook and some hand-waving documentation. Vue has official and router library and state management library which are linked to from the official documentation. > React itself is just reactive functional programming. The sell of not writing it yourself is that you get to work with a nicer API while the React team improves the backend for you (a la Fiber). You can apply this your own argument. React is just reactive functional programming. Why just pull in a view library when you can just render using functions? Why not write it yourself, if you're writing everything else yourself? Are you afraid to? Why include a 240kb library to render functional components? What do you get out of using React over Vue, which also uses the virtual DOM and has functional components? |
Uh... what API churn? The Redux store API hasn't changed meaningfully since about a month after its 1.0 release. 3.0 came out around September 2015, and it's been the same since.
React-Redux has stayed API-consistent too, even though we rewrote the internals for 5.0.