4 ms·
I joined a company that had two fairly simple internal web apps, one in Angular and the other one in React. Both had been written and maintained by a number of
by Udik 7y ago
I joined a company that had two fairly simple internal web apps, one in Angular and the other one in React. Both had been written and maintained by a number of devs, each on the task for a few weeks or months. Both had several issues and blunders that needed to be fixed. However, while the Angular app had a very obvious, predictable structure, with issues confined inside single components or services, the react app was a totally obscure jam of javascript and html with more javascript and more html interspersed within, tons of redux boilerplate and properties passed down three or four levels of nested components. The stuff was such a wild spaghetti mess that editing a form in a foreground modal made the text in a background static page jump around when the number of characters in the form was even.
So no, I didn't enjoy the ride, at all.
- crubier 7y agoAnecdotal evidence. This is just the result of bad practices. React is less opinionated than Angular I'll give you that, so I guess that subpar angular might be preferable to subpar react. Well-managed react is incomparable in power. Try to make a library like react-three-fiber using Angular, in less than 500lines of code.
- andrewjrhill 7y ago> Well-managed react is incomparable in power. Unfounded opinion. > Try to make a library like react-three-fiber using Angular, in less than 500lines of code. react-three-fiber is much bigger than 500 lines of code.
- crubier 7y agoOpinion founded on several examples such as the react-three-fiber one I just gave. And no, the initial implementation which was just as powerful (but lacked typescript typing) was mostly 2 files of 250 lines of code each. Look it up. I am waiting for the angular or vue counterparts. And also the angular and vue equivalents of react native.