New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better docs on why we need Whitestorm over Three.js? #399
Comments
@trusktr Sure, coming soon. Currently we're hardly working on whs.js v3 release! |
@trusktr , a bit of a late response, but to complement Alex's answer:
The core benefit really is, a framework for creating component based webGL applications. Keeping your code neat, your logic re-usable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I see the "Welcome" doc page mentions "component system", but it is very vague. Can you describe what are all the reasons that I'd want to use Whitestorm over plain Three.js, f.e. what are all the things I get that Three.js does no offer, so that I can better understand?
Thanks!
The text was updated successfully, but these errors were encountered: