That doesn't mean that the process stops, it runs indefinitely because it has to.

The DOM does this. React does this.

Did you know CSS even invokes the GPU for certain tasks?

You guys really need more experience. I can't believe how many people apparently know nothing at all about web dev and computers.

> That doesn't mean that the process stops, it runs indefinitely because it has to.

The processes don't stop, no, but they do pause and go idle, waiting for the next event to come in. Not sure what that has to do with this.

> The DOM does this. React does this.

What does react have to do with any of this discussion, and what do you mean by "this"?

> Did you know CSS even invokes the GPU for certain tasks?

Whether the GPU or CPU does work is unrelated to how frequently and how much of the screen is rendered. Damage regions work just fine for GPU-based rendering.

> You guys really need more experience. I can't believe how many people apparently know nothing at all about web dev and computers.

Part of my job is maintaining a retained mode UI library. I've literally written some of the parts that handle damage regions, as well as the GPU-based rendering. But do go on about how I don't know how any of this works.

I get what you're saying.

These downvoters act like native JS doesn't do the exact same thing with event listening and observing the DOM. So does React and other FE frameworks.

Philip J Fry is either being disingenuous or genuinely doesn't know that game rendering has often several MB models, is often raycasting, maintaining camera calculus, and a lot more.

Braindead take.

A videogame is expensive to render because of several MB models, constantly moving camera, and other things.

The concept of observing elements is not even new.

> GPUs are expensive

Do you know that regular HTML and CSS use GPU all the time?

Nothing wrong with browsers using resources to do useful work. I'm just not a fan of bloat that eats resources because they're assumed to always be available.

That's what this thread is about, I thought.

You know nothing about software if you really think this.

He's right - the DOM also has observers.

The difference is what is rendered, not that observers are involved and the concept of looping.

Millions use React - you want to talk about performance?