3 ms·
I think your idea of speeding up the DOM is the right one, but the view transitions API has almost nothing to do with it. That’s more for whole page changes, an
by nwienert 3y ago
I think your idea of speeding up the DOM is the right one, but the view transitions API has almost nothing to do with it. That’s more for whole page changes, and doesn’t solve the main issues which is that the DOM simply does way too much and is bloated to all hell, and that JS is single threaded.
I’d like to see a new mode introduced ala “use strict”. I know the big brains at the top hate this but we need a way to shake off some legacy especially in the DOM. A few changes to its semantics could dramatically speed it up. And then the second part would be a way to share events and DOM across workers so we can put React essentially off the main thread. These two changes together would make websites able to feel like native apps.
- bryanrasmussen 3y ago> DOM simply does way too much and is bloated to all hell, It's my observation that React and similar frameworks really help to bloat the DOM. Now someone will say it is how people misuse React and similar frameworks. and then I will say if large parts of the population using a technology make the same misuse of it, even people who know better, it seems like the technology supports that misuse and is to blame somehow.
- nwienert 3y agoI don’t agree at all, I don’t see any extra DOM due to React across many apps nor any fundamental reason why it’d cause it.