glow VS rust

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.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.