React I love you, but you're bringing me down

Post by pier25 » Tue, Sep 20, 2022, 9:15 PM UTC

WHATDOESIT wrote: post #332

pier25 wrote: post #328

Earlier quoted context omitted.

There are literally dozens of libs/frameworks faster than React. https://krausest.github.io/js-framework-benchmark/current.ht...

Lol, you really think someone is going to stray off the well-supported path for apps like these for 1-10% gain? This app shows a loading indicator quite a lot. Speed is important but nobody cares about raw speed this much. What we care about is a well-maintained library with significant ecosystem that's still going to be there in 2030 and it's super-easy to find devs and/or get help. The libs there are beta quality a…

Post by fortyseven » Tue, Sep 20, 2022, 9:18 PM UTC

hnuser847 wrote: post #281

cosinetau wrote: post #271

Earlier quoted context omitted.

By the same extension, would you consider your comment worthy of the same classification of "cringey"? How you feel about the delivery is not relevant to the topic, and if you had opted not read to it, it would not be the person in the arena that would be at a loss because of it.

> By the same extension, would you consider your comment worthy of the same classification of "cringey"? No, but I think your comment falls squarely in that category.

Post by mzzter » Tue, Sep 20, 2022, 9:21 PM UTC

corytheboyd wrote: post #190

I've worked in a few roughly-the-same-size (~50 engineers) web development shops. It's always the same. Doesn't matter if it's React, Angular, Class based components, Functional components with hooks, Just Some HTML, PHP, Rails views, etc. The frontend just collects the cruft of a product organization changing course very frequently. There are always a dozen half-finished fix-the-world ideas conflicting with each oth…

Post by aarpmcgee » Tue, Sep 20, 2022, 9:33 PM UTC

bluefirebrand wrote: post #84

fabian2k wrote: post #22

Earlier quoted context omitted.

Context is useful for certain cases, but plain old useState/useReducers are the workhorses. I think the beta docs are pretty good about explaining the tradeoffs ( https://beta.reactjs.org/learn/passing-data-deeply-with-cont... ). To me one of the biggest issue is that almost everyone is deeply afraid of prop drilling. Passing props around and having some local state works very well for large parts of many application…

> To me one of the biggest issue is that almost everyone is deeply afraid of prop drilling. Prop Drilling is considered an anti-pattern for good reason. It very quickly turns your project into an absolute mess, making it impossible to determine where props are coming from and where data is actually set. Keeping that clean is one of the most important things you can do in a frontend codebase imo.

Post by yCombLinks » Tue, Sep 20, 2022, 9:43 PM UTC

xtracto wrote: post #213

rafale wrote: post #29

I prefer Angular. I never could accept writing css/html in my javascript. To be fair, my background is from XAML, so declaring the state separately and simply binding to it in my html template felt natural. The whole functional approach in React is overkill imo. It's okay if the state mutates in 90% of scenarios. Where there is really benefit from immutable states, I can enforce that on my own.

Yes yes yes! I´ve done some React at my job and also done some Angular/Ionic before. What I never understood of React is why did the creators decided to throw DECADES of Software Engineering development and comingle presentation layer with logic... To separate Views from Logics was an agreed good practice in Software Engineering since I was in undergard school 20 years ago.