Depends what you are building and what you mean by high performance but generally yes, there are lots of 3D games built with Three.js and there is also some info in the Angular Three docs on Angular Three specific performance considerations if you are interested: angularthree.netlify.app/core/advanced/performance/
performance wise: nothing can really pass vanilla THREE.js but the DX can be up for debate for vanillla THREE.js versus a framework integration like Angular Three (Angular) or React Three Fiber (React) or TresJS (Vue)
I'm curious, is there a point in using this library? Or would it make more sense to just use a more maintained react-three-fiber component, that we render in angular when we need three.js in an angular app?
Disclaimer: I've never used R3F, but unless I am missing some context here I'd say the point of this library is so that you can use Angular instead of React to build your scenes - the point of NGT is pretty much to bring R3F to Angular. Technically I think you could use R3F to create a custom element or something and then render that in your Angular application, but it doesn't seem ideal.
I thought about that as well and considered it as a general 3D solution for Angular devs. However, it becomes more of a hassle to access services, using Angular features like directives/control-flow from within the 3D scene graph. You'd have to drill everything into the React world via Context or something global which might or might not bring a good DX for the Angular devs.
I've got a tip for using materialize and dematerialize for error handling in RxJS going out in the newsletter tomorrow: mobirony.ck.page/4a331b9076
Felt like the video ended as soon as it started to get interesting 😅
Great video Josh I definitely want to see more
Are we in the Tesseract? 😅
So now we can create 3d games high on performance. Right?
Depends what you are building and what you mean by high performance but generally yes, there are lots of 3D games built with Three.js and there is also some info in the Angular Three docs on Angular Three specific performance considerations if you are interested: angularthree.netlify.app/core/advanced/performance/
performance wise: nothing can really pass vanilla THREE.js but the DX can be up for debate for vanillla THREE.js versus a framework integration like Angular Three (Angular) or React Three Fiber (React) or TresJS (Vue)
I'm curious, is there a point in using this library? Or would it make more sense to just use a more maintained react-three-fiber component, that we render in angular when we need three.js in an angular app?
Disclaimer: I've never used R3F, but unless I am missing some context here I'd say the point of this library is so that you can use Angular instead of React to build your scenes - the point of NGT is pretty much to bring R3F to Angular. Technically I think you could use R3F to create a custom element or something and then render that in your Angular application, but it doesn't seem ideal.
I thought about that as well and considered it as a general 3D solution for Angular devs. However, it becomes more of a hassle to access services, using Angular features like directives/control-flow from within the 3D scene graph. You'd have to drill everything into the React world via Context or something global which might or might not bring a good DX for the Angular devs.
I thought angular three wasnt supoorted anymore… are you using an poder versión of angular?
This is latest Angular and the beta v2 version of Angular Three: angularthree.netlify.app/ (Chau is actively working on it)
@@JoshuaMorony Those are fantastic news!, really excited to try this library now that is supported :)
@BrandonRobertsDev lol😂
@josh yes please, do it before chau releases v2