IME marrying business logic so closely to presentation makes it very hard to change one without the other. Especially relevant for web apps, where you may want to re-use business logic for mobile apps, which becomes very difficult when they're tied to a react component.

Also makes it harder to test. There's a great paper called "Naked Objects" which I'd recommend for anyone doing GUIs, but powerful idea I got from it is make your presentation code so immediately obvious from your business objects that you can practically generate it automatically.

Pawson's Naked Objects thesis is absolutely brilliant.

It proposes a complete approach of which not all of the parts will be useful for any given project, but it is -very- much worth reading even so.

Hey, someone else on the internet who knows about it!

And yeah agreed, but I think we could all use some scantily clad objects at the very least.

Because it was implemented via inheritance. Which is why the argument is BS, nobody does react like this. They specifically tell you not to do it, and I think there's a bunch of stuff in there to stop it from working.