Echo JS 0.11.0

<~>
tracker1 1843 days ago. link 2 points
While the article is largely factually correct, it's definitely biased towards Vue.  React (core) is largely about the view/rendering engine and less about state management or application structure.  It works very well with the broader community and resources in the npm ecosystem.

Regarding state, there are other options for React that are closer to VueX, such as MobX, and GraphQL has been gaining popularity as well.  Not to mention React's Context (Provider/Consumer) options and the newer Hooks for state.

In my opinion and experience, React is much better for building larger applications with teams of developers.  This has been the case compared to every other framework that I've worked with and that's been a lot including Angular, AngularJS, Vue, Backbone, Ember, and others going back over two decades.  React + Material UI and JSS has been a far nicer experience for developing web based applications than any other set of tooling I have ever used by a large margin.

That doesn't mean don't look at alternatives... Blazor is interesting, even if the default directory structure is ugly (you can adjust it) as well as other WebAssembly targetted options... Yew (Rust) is really cool, though my own knowledge of Rust is really shallow.  Always consider alternatives... There was a lightweight framework a few days ago that was pretty cool.  It really depends on what your needs are.

If I were trying to enhance a mostly static application already in place, I might reach for Vue or something even lighter.  If I have to build an application with a dozen other developers, it's React hands down.  On Angular, I'd rather use TypeScript with React than deal with Angular's overly prescriptive complexity.  I like a code-base that is largely discoverable and as simple to use/enhance as possible, Angular doesn't allow for that.

Replies