Making Sense of React Server Components

Re:Making Sense of React Server Components by littlecranky67 on Wednesday September 06, 2023 @03:08PM (#37409662)

Agreed, but non-sequential execution is the nature of event-driven, async non-blocking code. Event-driven as Web Applications (not Websites!) mostly deal with events (user input or network events). As long as the JavaScript VM and the DOM uses non-blocking async models no framework - being it Vue, Angular, React or whatnot - will ever change that.

Sequential, blocking modells like i.e. batch ETL jobs are just not the domain of the browser.

[ Parent | on HN ]

Re:Making Sense of React Server Components by SahAssar on Thursday September 07, 2023 @07:49AM (#37417575)

> As long as the JavaScript VM and the DOM uses non-blocking async models

The DOM is almost entirely sync, all the operations on it are blocking operations (including things like replacing an entire document with innerHTML).

[ Parent | on HN ]

Re:Making Sense of React Server Components by littlecranky67 on Friday September 08, 2023 @02:51AM (#37430337)

While not strictly on "the DOM", a lot of modern APIs are within the browser's JS VM (Notification, Camera, Audio, QR scanning, etc.) and all of them are async to the core. My argument therefore stands.

[ Parent | on HN ]

Re:Making Sense of React Server Components by SahAssar on Monday September 11, 2023 @02:37PM (#37471646)

It does not, since most of those APIs are not directly called from the framework. What react and most other JS frameworks do is DOM modification (which is clearly sync) and delegate events (which is usually done via callbacks or binding).

[ Parent | on HN ]