Skip to content

Newsletter 13: Add NeoCogi's libs #243

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

Merged
merged 9 commits into from
Sep 7, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add reference to Jude3D in action
  • Loading branch information
eloraiby committed Aug 31, 2020
commit 2404ed32df813382b66658a5d7d4aa5370edf23b
5 changes: 3 additions & 2 deletions content/posts/newsletter-013/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,6 @@ Many problems arise when moving existing C/C++/webassembly code to Rust.
The 2 most important ones:

- The new code should still interop with the already existing code

- Payload size matters on the web: Your wasm app should be as small as possible

These led us to drop using rust's std in favor to our own libs (`!#[no_std]`),
Expand All @@ -91,8 +90,10 @@ The good news is that we are releasing most of the libraries as we make them as
[NeoCogi Repo](https://github.com/NeoCogi)

We have included an example that showcase the libs:

[Webassembly glfw3/gles2 example](https://github.com/NeoCogi/rs-glfw3-gles2-test)
A good example that you can build and run with wasm32-unknown-emscripten!

[Jude3D in action]: https://twitter.com/weloraiby/status/1167228654922928130

## Popular Workgroup Issues in Github

Expand Down