If you use React use r3f, there is no reason not to. React and Three would be two different worlds and in scale hard to reconcile. React was quite literally made to deal with imperative systems like Three: https://twitter.com/0xca0a/status/1282999626782650368?s=19 All in all you will be learning Three much quicker and you will arrive at intended results faster and with less code. It’s basically the same as why you use React for the dom.
It seems like it isn’t a MUST to use react-three-fiber to work with both React and Three.js, is it?
Since I just wanna integrate between React and Three.js in my application, and I am new with React so I just wanna find the simple way to go.
there is no must, it would just be pointless. threejs is imperative, react is not. to make an imperative system, where everything is connected to everything else, work over a nested, self-contained component graph is not easy, essentially you will re-create some part of react-three-fiber.
if you are unsure, take those two examples and try to reproduce them in vanilla three, it’s a good learning practice as well: