Things I wish I knew before moving 50K lines of code to React Server Components

Post by CharlieDigital » Fri, Sep 01, 2023, 2:51 PM UTC

ttfkam wrote: post #320

CharlieDigital wrote: post #182

Earlier quoted context omitted.

Take this example: const { useState } = React; function Person(props) { console.log('Render Person'); return ( { props.identity.firstName } { props.identity.lastName } ); } function App (props) { console.log('Render Hello'); const [count, setCount] = useState(0); const einstein = { firstName: "Albert", lastName: "Einstein" }; return ( setCount(count + 1)}>Increment ); } ReactDOM.render( , document.getElementById('con…

After all this time, React's sheer tonnage of boilerplate still astonishes me. That abstraction leaks like useMemo(…) even need to exist in the first place… Folks want to solve their own problems, but they keep getting saddled with React's as well.

    > The pain and suffering of hooks all roots from the mismatch between a dogmatic belief in the superiority of immutability and the harsh reality of the host language that is JavaScript (Feb 25, 2023)

Post by solardev » Fri, Sep 01, 2023, 2:55 PM UTC

ttfkam wrote: post #316

solardev wrote: post #229

Earlier quoted context omitted.

As a different perspective, I'm also old enough to remember when CSS and Javascript were invented , and I've been making websites since that time. IMO web dev has never seen better tooling than today, and user experience has improved tremendously over the years. What we used to call AJAX has grown from a neat side toy to a basic part of everyday life in the form of client components and SPAs. The server is still as p…

Well, React certainly has succeeded in increasing the client-side complexity, that's for sure. They seem to be making good inroads on increasing server-side complexity as well. Kudos to their contributions to excess CO2 emissions! I have yet to see a React project with more than five contributors fail to turn into a big ball of mud within 18-24 months, requiring either a periodic rewrite or resigned acceptance of tru…

Post by laputan_machine » Fri, Sep 01, 2023, 2:57 PM UTC

uxp8u61q wrote: post #306

laputan_machine wrote: post #198

Earlier quoted context omitted.

[flagged]

> Because they are called "libraries" for a reason, it can do much more than "Hello, World", and they are routinely used for much more than that. There you go.

Post by ttfkam » Fri, Sep 01, 2023, 3:00 PM UTC

Cthulhu_ wrote: post #232

DigitalSea wrote: post #207

I'm old enough to remember when servers rendered everything and you used CSS and Javascript to enhance the pages after they were rendered. The web is in such a dark and overengineered place. It's almost unbelievable. It's why my approach to building apps is server-rendered first and then enhanced after the fact.

You guys are using Javascript? I jest; our first geocities page was just HTML with maybe a visitor counter, marquee and whatnot. Our first PHP application / project in school actually didn't use JS yet, it used frames for a static menu and header and just straight form submission to get data to the back-end. Those were the days. But when I did my first college level internship (1 year of internships is part of colleg…

Post by uxp8u61q » Fri, Sep 01, 2023, 3:02 PM UTC

laputan_machine wrote: post #335

uxp8u61q wrote: post #306

Earlier quoted context omitted.

> Because they are called "libraries" for a reason, it can do much more than "Hello, World", and they are routinely used for much more than that. There you go.

> When you're writing a specific program, e.g. it's never going to be anything more than "Hello, world!" , why would you use the fattest framework when you can write it in plain HTML? Emphasised the parts I think you should re-read