Skip to content
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

config: Add three.js to OSS Game Engines #1823

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

zalo
Copy link

@zalo zalo commented Dec 25, 2024

If raylib and the other WebGL and graphics library abstractions count, then three.js certainly counts!

It’s easily the most popular game engine (and 3D abstraction) on the web. 😄

If raylib and the other graphics library abstractions count, then three.js certainly counts!
@634750802
Copy link
Collaborator

The three.js library is a general-purpose tool for graphic rendering and is not specifically designed to function as a game engine. A game engine typically offers a broader range of features beyond graphic rendering.

@zalo
Copy link
Author

zalo commented Dec 31, 2024

three.js does much more than just graphic rendering

A few comparisons to Raylib (the most rapidly growing “game engine” on the current list):

  • three.js offers a well developed scene hierarchy abstraction, while Raylib is just a series of graphics and input API abstractions with no scene hierarchy.
  • three.js’s suite of features vastly eclipses Raylib’s (and most of the other engines on the list) because its examples are composed of reusable engine components (that are distributed with and meant to be used from the base npm package)): https://threejs.org/examples/

This is bolstered by the fact that these engine components (including skinning, lighting, nodes, physics, VR/AR etc.) can be found in its release changelist: https://github.com/mrdoob/three.js/releases/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants