Because I would need to see a UI paradigm prove it can handle performance before considering using it for UI.
react-three-fiber solves a lot of problems. React state is also perfectly in line with game loop architecture, r3f unifying the Three.js/React render loop is incredibly good for game dev.
But even for SaaS or whatever, I need to know that it can handle complex states of the UI - HTMX can't.
They are overselling it. It's not really a competitor to React, it's more like a competitor to Jade templating or HAML which nobody already uses anymore.
react-three-fiber solves a lot of problems. React state is also perfectly in line with game loop architecture, r3f unifying the Three.js/React render loop is incredibly good for game dev.
But even for SaaS or whatever, I need to know that it can handle complex states of the UI - HTMX can't.
They are overselling it. It's not really a competitor to React, it's more like a competitor to Jade templating or HAML which nobody already uses anymore.