Add wgpu and three-d portable (rust) graphics libraries #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
... and rearrange webgpu tutorials.
|
By the way, I saw that you are doing mob programming at your meetup. If you are interested in doing a Rust or WebAssembly session at some point in time (and open to figuring out a Europe-friendly time slot) I would be happy to contribute my experience there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rust has some really nice offers in the graphics ecosystem.
wgpu is really interesting, and it's actually the core of the (experimental) WebGPU implementation in Firefox.
three-d is nice because it's lightweight and easy to target native as well as web apps (OpenGL+ES and WebGL).
I saw that "Learn wgpu" was already mentioned as a tutorial. Not sure how well it suits if someone is interested in using WebGPU in the browser. That's why I moved it to the tutorials sub-section of the new section I've added.
Instead, I've added 2 tutorials for the WebGPU API I've found via a quick google search. But yes, I've seen the note that one shouldn't add something that you can not vouch for (not read/viewed/used). I am happy to delete those 2 tutorials and implement any other improvement/change ideas.