top | item 21685813 (no title) aassddffasdf | 6 years ago Right. All this treating the DOM with kid gloves seems to be due to its pre-existing weaknesses. Why not just fix those? discuss order hn newest opencl|6 years ago Browser vendors have spent the past several decades trying to fix those weaknesses and haven't, it seems like a very strong indication that it is not exactly an easy thing to do. fulafel|6 years ago This might be just because most web apps never had a bottleneck on JS->DOM changes. load replies (1) kelnos|6 years ago Because you can't "just" fix them. It's a complex problem with no easy solutions. Don't you think it'd already be "fixed" if it was easy?
opencl|6 years ago Browser vendors have spent the past several decades trying to fix those weaknesses and haven't, it seems like a very strong indication that it is not exactly an easy thing to do. fulafel|6 years ago This might be just because most web apps never had a bottleneck on JS->DOM changes. load replies (1)
fulafel|6 years ago This might be just because most web apps never had a bottleneck on JS->DOM changes. load replies (1)
kelnos|6 years ago Because you can't "just" fix them. It's a complex problem with no easy solutions. Don't you think it'd already be "fixed" if it was easy?
opencl|6 years ago
fulafel|6 years ago
kelnos|6 years ago