winit VS learn-wgpu

> The consortium aims to develop guidelines, tools, libraries, and language subsets to meet industrial and legal requirements for safety-critical systems.

> Moreover, the initiative seeks to incorporate lessons learned from years of development in the open source ecosystem to make Rust a valuable component of safety toolkits across various industries and severity levels

Resources and opportunities for a safety critical Rust initiative:

- "The First Rust-Written Network PHY Driver Set to Land in Linux 6.8" https://news.ycombinator.com/item?id=38677600

- awesome-safety-critical > Software safety standards: https://awesome-safety-critical.readthedocs.io/en/latest/#so...

- rust smart pointers: https://news.ycombinator.com/item?id=33563857 ; LLVM signed pointers for pointer authentication: https://news.ycombinator.com/item?id=40307180

From https://news.ycombinator.com/item?id=33563857 :

> - Secure Rust Guidelines > Memory management, > Checklist > Memory management: https://anssi-fr.github.io/rust-guide/05_memory.html

Rust OS projects to safety critical with the forthcoming new guidelines: Redox, Cosmic, MotorOS, Maestro, Aerugo

- "MotorOS: a Rust-first operating system for x64 VMs" https://news.ycombinator.com/item?id=38907876: "Maestro: A Linux-compatible kernel in Rust" (2023) https://news.ycombinator.com/item?id=38852360#38857185 ; redox-os, cosmic-de , Motūrus OS; MotorOS

- https://news.ycombinator.com/item?id=38861799 : > COSMIC DE (Rust-based) supports rust-windowing/winit apps, which compile to a tag in WASM.

> winit: https://github.com/rust-windowing/winit

- "Aerugo – RTOS for aerospace uses written in Rust" https://news.ycombinator.com/item?id=39245897

- "The Rust Implementation of GNU Coreutils Is Becoming Remarkably Robust" https://news.ycombinator.com/item?id=34743393

From a previous Ctrl-F rust,; "Rust in the Linux kernel" (2021) https://news.ycombinator.com/item?id=35783214 :

- > Is this the source for the rust port of the Android binder kernel module?: https://android.googlesource.com/platform/frameworks/native/...

> This guide with unsafe rust that calls into the C, and then with next gen much safer rust right next to it would be a helpful resource too.

From https://news.ycombinator.com/item?id=34744433 ... From "Are software engineering “best practices” just developer preferences?" https://news.ycombinator.com/item?id=28709239 :

>>>>> Which universities teach formal methods?

/?hnlog "TLA" and "side channel"

Hi! I’m Aloke, an engineer at Warp.

I’m really excited to share that Warp is now available on Linux! If you’re interested in trying it out, you can download Warp: https://warp.dev/

Building Warp on Linux was quite an undertaking. Warp uses a custom Rust-based UI framework that we built in house and renders natively on the GPU. To get Warp running on Linux, we built a version of our UI framework that supports winit [1] as a windowing backend. We also built a version of our renderer that uses wgpu [2]. Reducing complexity by using these well-supported, cross platform, frameworks let us bootstrap a version of Linux quicker than expected and should make it easier to build Warp for other platforms (like Windows).

Please let me know what you think! Happy to answer any questions, either about the product or about technical challenges.

[1] https://github.com/rust-windowing/winit

This link: https://github.com/rust-windowing/winit has this code:

Have you seen the official example?

That's a bit shortsighted given that there is an active discussion about reducing the interior mutability.

I really need a file dialog for my ImGui-based project in Rust. I tried using this crate but it's wayyyyyyy too old. I also saw this but considering the date it was last updated and the look of the repo, it's not gonna work either. Also I maintain my own library for such things, but it's currently blocked by this issue. What options do I have?

In this case, I used the "A"GPL because this crate could feasibly run on the web. winit has a web backend. At the moment I don't support it (there's a PR that needs to land first), but in the near future it's not implausible that this crate could be used in a web environment.

There are a number of up-and-coming Rust-based frameworks in this niche:

- https://github.com/iced-rs/iced (probably the most usable today)

- https://github.com/vizia/vizia

- https://github.com/marc2332/freya

- https://github.com/linebender/xilem (currently very incomplete but exciting because it's from a team with a strong track record)

What is also exciting to me is that the Rust GUI ecosystem is in many cases building itself up with modular libraries. So while we have umpteen competing frameworks they are to a large degree all building and collaborating on the same foundations. For example, we have:

- https://github.com/rust-windowing/winit (cross-platform window creation)

- https://github.com/gfx-rs/wgpu (abstraction on top of vulkan/metal/dx12)

- https://github.com/linebender/vello (a canvas like imperative drawing API on top of wgpu)

- https://github.com/DioxusLabs/taffy (UI layout algorithms)

- https://github.com/pop-os/cosmic-text (text rendering and editing)

- https://github.com/AccessKit/accesskit (cross-platform accessibility APIs)

In many cases there a see https://blessed.rs/crates#section-graphics-subsection-gui for a more complete list of frameworks and foundational libraries)

Name: Francesca! Location: Portland, OR (UTC-7) Looking for: Remote only, full-time or contract. Contact: [email protected] LinkedIn: https://www.linkedin.com/in/francesca-lovebloom/ GitHub: https://github.com/francesca64 Experience: 4+ years of professional Rust experience; former lead maintainer of winit and creator of cargo-mobile.

https://sotrh.github.io/learn-wgpu/

Wgpu is a Rust-based library that takes a similiar general API shape as Vulkan but is simplified. When I first tried to learn Vulkan I found the complication to be overwhelming (primarily because there are no defaults for ANYTHING) but once I learned wgpu it was substantially less so. It is still quite complicated though.

Wgpu is aiming to be almost as powerful as Vulkan, but it's not there yet because the features that are needed to do the modern techniques that make Vulkan really good (as compared to opengl) either aren't there yet or are so bug-ridden as to not be usable in practice yet.

It has some ability to run in a web browser, probably with JS, too, but I'm unfamiliar with the details there.

Nice.

Speaking of Snake game, if you want to go even deeper, you can try to use the wgpu crate to combine Rust and WebGPU to write everything from scratch. Here is the tutorial:

https://sotrh.github.io/learn-wgpu/#what-is-wgpu

I once wrote a code editor with wgpu, from font rendering to char/line state management (very rough) for music live coding:

https://github.com/glicol/glicol-wgpu

It runs in browsers, even including Safari!

https://sotrh.github.io/learn-wgpu/ This is probably the best resource out there for learning wgpu specifically. If you're unfamiliar with graphics, the learnopengl one is good. If you've got experience though, jumping right into that one is a shout or looking at some vulkan ones as they're pretty similar in terms of architecture.

- https://sotrh.github.io/learn-wgpu

Most of The WGPU I learnt is from https://sotrh.github.io/learn-wgpu/ but it doesn't really talk about designing n stuff, I thought of checking out the source code for Bevy or even games like veloren. But well, their codebases are pretty big to get started in the first place.

So I was wondering if opting for option 1 would be better to begin with. OpenGL has a much bigger community and wgpu only has its documentation which I hear is not quite up there yet. There is this excellent tutorial for wgpu that I read through, but it seems like wgpu can be a lot more complicated than starting with OpenGL.

I started with wgpu tutorial (https://sotrh.github.io/learn-wgpu/) since I like the idea of portability and it's a Rust-first library, but it seems I'm missing some foundations of how CG works in general: the code is given, a little of explanation like it assumes I already know something, maybe I'm wrong, but I wish there was a longer explicit version.