Threejs vs Pex
You may think that this is just another framework like Babylon which is also a better project than the Threejs framework. With all respect to the creator of the Threejs framework who is an awesome guy, the whole structure of Threejs is a mess, the documentation is also a mess.
The main issue with Babylonjs and Threejs is that you have to get along with all the bundles that will include the project that you don’t ever use. It’s almost impossible to use ECS with both of the frameworks. On the other hand, pex is very modular, if you need to load an asset file, you need to include pex-io library , if you need renderer , you include pex-renderer , if you need math , pex-math, pex-fx , pex-gltf, pex-gui,pex-audio, etc
Splitting the framework into micro libraries makes it easy to maintain and people can contribute more easily, something that is tough in Threejs. It’s almost a year that I’m using Threejs and I’m using it every day. The framework has any feature that you can think of, and it’s getting bigger and bigger every day. When you include Threejs into your project you may wonder why it’s so big and that’s what I mean. You want to create a simple 3d app, but your code already filled with features likes Augmented reality, Raycasting, PBR materials, Tonemapping, Image-based Lighting, etc
We hope that one day, compilers, module bundlers, minifers, and these kinds of tools clean our mess. We need to stop writing messy code. We have to start writing more modular code, think of maintainable structure but don’t fall to overengineering traps like C# and Java developers, you guys I hate the most. You corrupted developers, Those are hordes in World of Development. Though I love the hordes.
