bloom VS wgpu-rs

Static linking is remarkably easy: Creating small Docker images is a delight.

As a data point, I've served millions of HTTP requests using it, without problems.

For larger projects, I think that actix-web is the incontestable winner. That's why it's my choice for Bloom.

For me the worst part was not the job itself (I did ML related stuff) but the environment (commuting, artificial light all day long...).

Since I moved to the entrepreneurship track I'm way more happy. At first it doesn't pay so you need to have savings, but after some time (depends of the person) you start making a living and you can decide on what to work on.

Today, half of my time is dedicated to writing software that I genuinely believe have a positive impact on the world (https://github.com/skerkour/bloom), and half of my time is dedicated to writing and sharing (I'm writing a book).

The best thing that I've understood is that even if my primary skills are programming and architecture related stuff, it doesn't mean I have to code for a living. There are a lot of jobs related to programming that you can switch to.

Hi, I'm not a video game programmer, I mostly do network and web programming, but I do exactly this in Rust and it works very well. Here is an example for a mailer driver, which is a trait and then implemented for multiple "backends" such as AWS SES or SMTP https://github.com/skerkour/bloom/blob/main/bloom/kernel/src/drivers/mailer/mod.rs.

What do you think about degoogle project open source => https://bloom.sh/ " The simplest way to de-Google your life and business: Inbox, Calendar, Files, Contacts & much more ".

What do you think about degoogle project open source => bloom.sh " The simplest way to de-Google your life and business: Inbox, Calendar, Files, Contacts & much more ".

You could start with one of examples from wgpu and tinker with it to see if that's your thing. Ie. copy hello-triangle and add more triangles / make them move, etc.

wgpu-rs (https://github.com/gfx-rs/wgpu-rs) is probably closer to what you're looking for, it's a "high level wrapper" over wgpu-core (Which implements "WebGPU", an upcoming browser API for graphics using gfx-rs, and AIUI "implements" means this is what a browser might use to actually call a graphics API when javascript uses webGPU, although if you're compiling for wasm it could just call the browser APIs). It can run natively, ignore the fact it has "Web" in the name

rust-gpu) is used for compiling a compute shader written in Rust to SPIR-V. wgpu-rs is used natively for running the GPU computation.

For web assembly there is the unofficial bevy_webgl2 plugin. Official bevy web assembly support would probably use the wgpu webgl backend, which still needs some work, and is currently untested in bevy.

We let wgpu https://github.com/gfx-rs/wgpu-rs handle our graphics backend abstraction, so our OpenGL support will come whenever they implement and release it. Currently, it seems to be a WIP.

It's the same thing, the Rust implementation is just called[wgpu](https://wgpu.rs/)

Same as with GLSL, isn't it? What we do in wgpu-rs examples, and that's something I expect to see more widely, is having an integration test that just parses all the WGSL in the project and reports errors. Ideally though, we'd have a set of IDE plugins to do the parsing and report errors right where you type the code. We'd appreciate any help to get these started!

Also you could use an existing cross-platform graphics library, e.g. wgpu-rs. It supports Vulkan, Metal, DirectX, OpenGL and WebGPU. Oh and it seems to allow switching backends at compile-time via the WGPU_BACKEND environment variable, so maybe check out how they're doing it.