DEV Community

Discussion on: Stop Using React

 
ender_minyard profile image
ender minyard • Edited
No... no it doesn't. This has nothing to do with what React is or is not.
What does it even mean? Stream? What?

You were confused by what a stream is, so I shared some helpful links.

React is just a wrapper API around the native DOM. So is the native DOM fighting against the natural flow of the internet, too? Or JavaScript?

React downloads all resources for a SPA at once. React needs to download resources for seconds at a time, blocking the main thread. Read the article again, perhaps?

Thread Thread
 
matthewpardini profile image
Matthew Pardini

Dude... react doesn’t do that. And the internet is NOT a readable stream. In fact, 99% of all resources are loaded NOT as streams which come off the response.body(), which you must attach a stream reader to in order to read the stream.

This is painful. Client side rendered apps will hit the browser, and turn around and go back to a server for the javascript bundle. That is true, unless you do ssr, in which case the react app hits the browser with the first view already built as html.

AFTER the first screen is built, the react code then turns around and makes more calls to “lazy load” the rest. In older react, it was handled in componentDidMount. Today it’s done in useEffect(). These run AFTER the first render.

It’s obvious you don’t know a lick about react

Some comments have been hidden by the post's author - find out more