scheduler-test | awsm-web | |
---|---|---|
2 | 1 | |
63 | 19 | |
- | - | |
0.0 | 4.3 | |
almost 3 years ago | about 2 months ago | |
JavaScript | Rust | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
scheduler-test
-
React Renderer for Three.js
this is the test you are referring to: https://github.com/drcmda/scheduler-test it tested against severe stress. the cubes had artifical runtime delay, which would clog the main thread. the github repo now contains a vanilla test that you can run, it will block your cpu for 1-2 seconds. this is repeated every 2 seconds. a vanilla app trying to get through this will consequently go to its knees, but react can schedule it away.
this btw, as absurd as it may seem to you, is a react feature. the upcoming react 18 release is pretty much based on it.
-
React Fiber - Yay or nay?
this is complete bs though, he merely removed the stress from the stress-test, the very thing it's testing against. the updated test is here: https://github.com/drcmda/scheduler-test it includes the stress test (500 instances of text geometry), re-created every 2 sec. simply creating them takes 1-2 seconds. svelte, like everything else is going to choke on this. react on the other hand can balance load.
awsm-web
-
React Renderer for Three.js
I wrote an opinionated WebGL wrapper in Rust/WASM here: https://github.com/dakom/awsm-web
The idea is that it does more cacheing of things like uniform locations and such so you do very fast in-memory lookups in WASM without hitting the JS Api as much.
In the future this will be obsolete since WebGPU has a more optimal API to begin with, and Rust/WASM won't need to go through the JS layer due to "interface types"
What are some alternatives?
shipyard - Entity Component System focused on usability and flexibility.
react-three-fiber - 🇨🇠A React renderer for Three.js
x_ite - X_ITE X3D Browser, view and manipulate X3D and VRML scenes in HTML.
beatmapper - A 3D editor for creating Beat Saber maps
shipyard-scenegraph
emscripten - Emscripten: An LLVM-to-WebAssembly Compiler