Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I build a WebXR app at work. It's a virtual environment for taking foreign language classes. You travel around the world and talk about what you see in-language.


react-xr?


Hell no


Why not? Do you use vanilla WebXR?


Those... aren't the only two options. I use Three.js.

I never really saw what the hype was about React. It seems like most people who got really into it never really had much experience building componentized code before, so what they think of as being the "great" thing about React doesn't really need React at all.

Virtual DOM is overhead, overhead I can't really afford. I have to hit 120FPS on the Quest 2 with an immediate-mode renderer, when React's V-DOM was designed for a 60FPS retained-mode environment. It's just... too much of a leaky abstraction to deal with when I have about 8 milliseconds to do absolutely everything. And yes, I hit 120FPS.

Honestly, managing 3D objects is one of the smallest parts of my job. Some days, it can be all consuming, but other times, I can go weeks without touching the graphics. The biggest concern I have is with data management and efficient transmission and decoding of assets.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: