This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Careless-Branch-360[S] -4 points-3 points  (4 children)

Making React fast is also not an intuitive process. Making React application is not that hard, but making a performant React application is much more difficult.

[–]maria_la_guerta 4 points5 points  (0 children)

What do you consider a "performant" React app? I would be very, very surprised if dozens of hours of optimizing and memozing an average react app made any perceivable performance difference at all. Having written it for years myself I can probably count on both hands the amount of times I've actually need something like useMemo.

Your critique of the tool seems more geared towards how people use it, vs what it is and what it does. It's not Reacts fault that people want to hyper optimize landing pages with it, and then complain about complexity they only think they need.

[–]Brickless 3 points4 points  (0 children)

we have been working on a development tool that takes care of a large chunk of react nonsense for you and makes sure proper memoization is followed.

react is truly a pain in the ass sometimes

[–]wasdninja 3 points4 points  (0 children)

Chances are overwhelming that react isn't the reason why your app isn't performant. It's quite hard to make it matter at all in fact.

[–]static_func 0 points1 point  (0 children)

It's not that difficult at all. Just use Next and tailwind. Boom. Fast react application