5 ms·
I very much respect and appreciate this perspective, however I think it's important to consider the context of what React is used for. It's made for things like
by JMTQp8lwXL 7y ago
I very much respect and appreciate this perspective, however I think it's important to consider the context of what React is used for. It's made for things like building store fronts and UIs for SaaS companies. Stuff that's list of things, and has some form input. It isn't really used for games. Not to say that React couldn't be used for that, but most people aren't using React while also placing extreme pressure on the GPU.
Also, I don't know if people want an e-shopping experience that has the visual complexity of feeling like they're playing a video game.
- HereBeBeasties 7y agoIt's also used quite extensively for data visualisation roles that D3 has traditionally been king of, in fact often alongside D3's libraries for calculating axis tick marks, colour scales, etc. To that end, you actually do end up with thousands of DOM nodes quite often.
- dragonwriter 7y ago> It isn't really used for games React VR is a thing, though.
- deltron3030 7y agoReact came out the same year they bought Oculus, so there might be a long term plan to first conquer the world of webdev, get the devs used to that paradigm and then integrate it with VR and funnel the devs to their own platform in the long run. This could explain the unneccessary complexity of the vdom for normal websites and apps. In VR you need high staedy framerates, the vdom could be used to shorten the round trip from client to server, as some kind of framebuffer.
- Jasper_ 7y agowhat? both the DOM and the VDOM are client-side data structures, what are you even talking about
- deltron3030 7y agoDon't they represent app state?