glow VS bonsaidb

You can absolutely do WebGL. glow is a good place if you want to do the webgl stuff yourself. With wgpu you can as well, though it is mostly targeted to the upcoming WebGPU standard. I have seen many crates that are capable of gltf loading, but I haven't used any yet. Hence I can't reall recommend one. But gltf capability does not really have anything to do with rust. As long as you can read a file and translate it to your engines scene/entity structure, I don't see why it shouldn't be possible to load gltf files.

Most of it is written in Rust and compiles to Wasm with WebGL/OpenGL bindings via glow. The settings panel is written in Elm and the whole project is compiled with Nix. There’s also a very basic native desktop app. I haven’t seen many examples of a complete setup like this, so hopefully this can serve as a template for anyone trying out a similar stack.

If you want to target desktop, mobile and/or web: https://github.com/grovesNL/glow

A/B Street, which comprises a UI library, lots of data import pipelines, and traffic simulation. 100k LoC, the only unafe is to make system calls through glow

https://github.com/grovesNL/glow/blob/main/examples/howto/src/main.rs :)

https://github.com/grovesNL/glow is used by wgpu for its OpenGL ES / WebGL backend

By the way, nowadays many projects use glow instead of glutin because of.. I think it's because glow works on wasm, in the web (as webgl).

But what glow actually does is highlighted on lines 66 to 123. This section is filled with gl.some_function() calls, which is the same on every platform.

I do have ideas in the issue tracker on some of the next steps towards an actual migration system.

What about https://github.com/khonsulabs/bonsaidb? Progress seems stall since last summer but very cool project

There is Nebari which is the KV part of BonsaiDB I've used both successfully (and that is currently in production)

In BonsaiDb, I define entire test suites as macros. This crate has a common trait that has multiple implementations in different crates. Each implementation needs to be tested thoroughly. For cargo test to be able to work in each crate independently, I needed to have the #[test]-annotated functions in the crate being built. By using a macro, I can define the functions in one location and invoke the macro in each crate to import the test suite into that crate.

hey, just letting you know that there already is a project called bonsai-db and some people might confuse bonsai-bt as part of that project

I'm finishing up a large refactor of BonsaiDb which will add support for using BonsaiDb in non-async code.

I'm working on a major refactoring of BonsaiDb, aiming to improve the design of several interrelated features. While it started by aiming to enable a non-async interface for BonsaiDb, I realized mid-refactor that another major refactor would be better to do simultaneously rather than separately. Thank goodness that refactoring in Rust is such a wonderful experience!

It depends on what you mean by "support graphs". If you mean support the abillity to build a GraphQL interface in front of it, yes that is already possible in a limited fashion, although there are no first-class relationship types yet.

I'm trying to release the first alpha of BonsaiDb. I'm wrapping up replacing OPAQUE with Argon2, in an effort to make upgrading less likely to cause issues in the future (given that OPAQUE is still a draft protocol). I still love OPAQUE and will bring it back in the future.