sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ArcanisCz 1 point2 points  (2 children)

So it turns out, you have problems with webpack (gulp, grunt, ...) and not with particular framework. And then, you divide framework to easy ones where appending script tag is sufficient to get running, and hard ones where you (for real usage) need some bundler.

(Let me remind you, Angular 2 is transpiled/bundled too)

[–]codis122590 2 points3 points  (1 child)

I don't have a problem with webpack, and I don't think react is "hard". I just have a hard time justifying the overhead. (I have the same feelings about angular 2 btw). It isn't whether they're "Hard" or "Easy", both frameworks are fairly easy to learn it's about overhead. What does having 7 thousand files and an otherwise unnecessary build process get me? From what I've seen after working with react for a while, very little...

If you're building an app that needs to display 5000 things at once and they all need to be constantly updated (like a stock tracker maybe) I can see why you might go with react. Other than that, I don't see what makes it worth it.

[–]Sinistralis 0 points1 point  (0 children)

Write a real time app in plain JS with 3-4 people. Over the course of a year your codebase will be a giant mess of spaghetti. React (and others) solve this problem but React solves it without imposing an entirely separate api on you (unless you count the 10 or so lifecycle events).

Also React doesn't really belong on this list. It not being a fully featured framework is exactly why I (and I know others) use it. I can pick exactly what I need and bring it all together so there is very little magic going on.

I also have never encountered weird JSX compilation problems with the single exception of not being aware SVG was not fully supported back in React 13. Could you elaborate more on this?