5 ms·

I've got the same feeling but with bad connotation. React is easy the same way jQuery is. Easy, unstructured, foggy, too much permissive tool. Far too easy to

by nkjoep 8y ago

I've got the same feeling but with bad connotation. React is easy the same way jQuery is. Easy, unstructured, foggy, too much permissive tool. Far too easy to end-up with spaghetti-code. I prefer not using it, Angular is far more organized.

tracker1 8y ago
Like another reply. // MyHello.jsx import React from 'react'; export default ({name}) => <p>Hello {name}</p>; Now do the same in Angular.
- _Tev 8y ago
  I cannot speak for GP but for me the complexity comes from stitching dozens of libraries to get similar "base" to build the app on. Ember/Angular have way more stuff baked in or standardized, while in React you have to handle ball of ever changing dependencies ... For seniors it's ok(-ish) tradeoff (you get much more choice / control), for juniors it is hell on earth. But that is more of an issue for projects maintained for a long time. If you want to crank out small apps fast, your "example" is relevant, and React definitely is the better option.
  - tracker1 8y ago
    What do you need that isn't in the box with React? Aside from fetch, which is in all modern browsers? The new Context component interface pretty much flushes out the last of what you are likely to need. As much so as what you get in the box with Angular. Even then, with Angular you'll usually need at least a visual component library, and with React, disparate components tend to work together with less friction comparatively.
    - _Tev 8y ago
      Well if you focus on components only in your app then sure, not much needed. But complex apps need much more, like testing infrastructure, routing, data layer, service layer, tons of utility functions (last time I toyed with React it did not even have debounce ... Library for UI w/o it seems weird for me) and likely something else. But hey, most apps are simple, so no need for all the above. I would say Ng/Ember are more specialized / niche.
- BjoernKW 8y ago
  "Hello world!" programs or their slightly more sophisticated variation, the to-do list app, aren't a realistic measure when it comes to actual real-world software that has to solve real-world problems.

by nkjoep 8y ago

tracker1 8y ago

Like another reply. // MyHello.jsx import React from 'react'; export default ({name}) => <p>Hello {name}</p>; Now do the same in Angular.

_Tev 8y ago
I cannot speak for GP but for me the complexity comes from stitching dozens of libraries to get similar "base" to build the app on. Ember/Angular have way more stuff baked in or standardized, while in React you have to handle ball of ever changing dependencies ... For seniors it's ok(-ish) tradeoff (you get much more choice / control), for juniors it is hell on earth. But that is more of an issue for projects maintained for a long time. If you want to crank out small apps fast, your "example" is relevant, and React definitely is the better option.
- tracker1 8y ago
  What do you need that isn't in the box with React? Aside from fetch, which is in all modern browsers? The new Context component interface pretty much flushes out the last of what you are likely to need. As much so as what you get in the box with Angular. Even then, with Angular you'll usually need at least a visual component library, and with React, disparate components tend to work together with less friction comparatively.
  - _Tev 8y ago
    Well if you focus on components only in your app then sure, not much needed. But complex apps need much more, like testing infrastructure, routing, data layer, service layer, tons of utility functions (last time I toyed with React it did not even have debounce ... Library for UI w/o it seems weird for me) and likely something else. But hey, most apps are simple, so no need for all the above. I would say Ng/Ember are more specialized / niche.
BjoernKW 8y ago
"Hello world!" programs or their slightly more sophisticated variation, the to-do list app, aren't a realistic measure when it comes to actual real-world software that has to solve real-world problems.