Member-only story
WebGL Frameworks: Three.js vs Babylon.js
Battle for the Best WebGL Frameworks: the Story as I Told It
Probably you’ve researched on slack and Github, and you have gone through the long list of pros and cons, but you still cannot tell for sure what would work for you.
Then, you will just pick one. In many cases, it probably does not matter that much. As all roads lead to Rome, right?
That was what I did. I was brave to pick up a new development tool before a deadline for a visualization project on the bird migration path.
How to Choose
If you may agree, this is not a decision based on perfect information.
Just a very quick background on the decision theory. Chess is a game with perfect information; Texas Hold’em is not, as it has hidden information, the cards you are not revealed to the other players.
When the situation is complex, you will need to decide on what matters most to you, based on the imperfect information you have gathered. This means the decision you made may not really be the best; though, the more you know, the better your decision might be.
First Impressions
The website is considered the first impression for me. The landing page of threejs.org is clean, and it showcases some very impressive projects; the site for babylonjs.com is minimalist, showing the best features of real-time rendering but not immediately attractive.
Documentation
If you are somewhat serious about your project, you should pay attention to the documentation of the software tools. In fact, both three.js and babylon.js have very good documentation, after you locate what you’re looking for.
Three.js organize the documents in a way that you’ll expect, just like any other software; babylon.js has some innovative ideas, especially when…
