r/angularjs • • Jun 30 '18

Why React is bad.

Here's why I think Angular is much better than React for creating SPAs.

React is not a framework like Angular is. It doesn't provide a comprehensive, one stop solution for all the things that you need for building an SPA. Often you will hear that React is 'un-opinionated' and that it allows developers the freedom to use whatever technologies they want alongside it. In practise, this means having to either constantly reinvent the wheel, or else employ a hotchpotch of third party libraries and be completely at the mercy of their maintainers.

Third party libraries may be buggy and there's no guarantee that fixes will be swift, if they even happen at all. Plus, they may be deprecated without any notice and you have to hope that they will work together successfully.

For state management Redux is the defacto standard. Redux is, in my view, seriously flawed. Firstly, why do you need to have a store in your client side at all? Is that not what the Database is for? In an SPA, the URL should be the single source of truth and the entire state of the app should be derived from this, using data fetched from a service. When you use Redux in an SPA, you need to work to keep the store in sync with the URL. This is a lot of work for no obvious benefit.

Another problem is that it risks storing stale data. Once the URL changes, all the existing data is potentially stale. There is no value in storing data across requests. If you want to cache data, the browser will cache your requests. Invalidating caches is notoriously difficult to do - why on earth do we bring this problem to client side development!

Redux also introduces Race conditions. If we make multiple requests to the server in quick succession, the Redux store has no way of knowing in what order these were made and given that they can return in any order, it is quite possible that the page we are looking at could be overwritten by the data from an old request! More detail about this problem here:http://blog.richardhunter.co.uk/index.php/13

The Redux store does NOT represent the current state of your app. It probably contains it, but it contains an awful lot besides and working out what is the current state and what is old state involves a lot of error prone work.

The next problem with React is that it does not support Dependency Injection. https://en.wikipedia.org/wiki/Dependency_injection DI is essential for building a complex enterprise grade application. The main benefits of DI are that it makes object creation a much cleaner process and it decouples dependencies from their implementation. If the last point is unclear, what it means that when you build an object you can supply completely different objects for any particular dependency. This is useful in testing where you can swap in mock objects for dependencies and thus test your objects in isolation from each other. With React, you have to rely on monkey patching or else test much larger chunks of your code at a time.

In React, you have to pass any dependencies down to components through props which can mean that a component has props that it doesn't actually use itself but just has them so it can pass them down to child components. You can use the Context for surfacing dependencies in a component but this is very much a poor man's DI imho.

There are other things about React that I don't like, but I don't want to extend this post too much. In particular PropTypes seem like an extremely feeble way of doing static typing and really typifies what is bad about React.

React isn't just different for not being a framework - it's worse. It is hopelessly inadequate for doing the job that it is supposed to and just results in messy, buggy, and inadequately tested applications.

I think the reason that React is more popular than Angular is because Angular lost a lot of good will during the shift from version 1 to 2. Maybe the Angular team didn't cover itself in glory, but I think the decision was the right one as the new Angular is much superior to the old one. It's irrational to dislike Angular because of these events but maybe a lot of developers are irrational.

0 Upvotes

122 comments sorted by

View all comments

Show parent comments

1

u/[deleted] Jun 30 '18

I actually have, but (yet again) you weren't paying attention.

1

u/prof_hobart Jun 30 '18

Have you? Where?

And (assuming you actually want to debate rather than play childish games) please don't say "look for it in my previous posts", as I clearly haven't seen it.

0

u/[deleted] Jun 30 '18

I'll leave the childish games to you, but you might try reading the very first post.

1

u/prof_hobart Jun 30 '18

Initially I'd thought you were just a junior dev who'd written a bug-ridden React and Redux app because you didn't full understand it, wanted to blame them for your errors and then quickly realised you were out of your depth but didn't know how to admit it.

But as there's absolutely no mention of how you think Redux is automatically triggering a navigation without you actively coding it anywhere in that first post it's clear you're now just trolling rather than even trying to have a real discussion, and I really can't be bothered with that. So ignore list it is.

Bye.

0

u/[deleted] Jun 30 '18

I get from reading your opinion of yourself that you're a programming genius (even if I probably wouldn't get it from your work) but it's a shame that you're too much of a React fanboy/cultist to consider any criticism of it.