femtovg VS bevy

Femtovg (https://github.com/femtovg/femtovg) which uses OpenGL to render

Congrats! I don't want to diminish the accomplishment, but have you seen femtovg? It seems like it's probably well-aligned with your needs.

I'm currently using femtovg for vector graphics in my games, and I would like to get into bevy by porting one of my game prototypes using it to bevy.

I use femtovg It's a simple vector graphics engine having all the important features you probably want from a 2D rendering engine: simple shapes, images, text

https://github.com/femtovg/femtovg/pull/5

Before Power10 was done, IBM actually asked us Raptor users about proposals for useful machine code instructions to add to it. I replied that I’d like to have hardware UTF-8 de-/encoding but they wanted a more detailed proposal and I never got around to write it. I’m not even sure that this would be worthwhile, but I see UTF-8 de-/encoding everywhere in the code I write and would like it to approach memory read/write speeds.

I was very disappointed to learn that they had gone more proprietary with Power10 so I would not have been able to use those instructions anyway. What a pity!

In my actual code, I'm using a library called femtovg that is a Rust port of a C library for 2D rendering. But In the blog post I kept the example simple to keep it relevant for people who might want to use Web Workers + WASM for other things; didn't want to get hung up on femtovg for someone who had never heard of it. As you say, if you all you need to do is basic 2D manipulations of a canvas that are supported by the native API, then you likely don't need WASM.

You guys should also check out the femtovg project, a 2D rendering API that sixty fps relies on.

https://github.com/femtovg/femtovg

It's a decent starting point for trying to build your own toolkit.

I have recently added a wgpu backend but for now it lives in my fork https://github.com/adamnemecek/femtovg

run the demo with `cargo run --example wgpu_demo --release`.

Also join the femtovg discord https://discord.gg/V69VdVu

I'm involved with the femtovg project. We are definitely looking for contributors. Join the discord channel.

It's not a GUI framework but I'm involved with this project called femtovg, it's a Rust nanovg port. I've recently added a wgpu backend. Run the demo with cargo run --example wgpu_demo --release. Some people have been using it for their own UIs, e.g. tuix. I think that you should consider rolling your own GUI toolkit, it's not that bad and you'll appreciate the control.

Bevy. A very young engine where you need to write the game entirely in Rust—that was appealing. But fatal flaws overshadowed everything: no editor, the engine brutally enforces the ECS approach, and the game's architecture must literally bend to fit this paradigm. So, you won't migrate to another engine at all—you just throw away all the code and start from scratch.

Missing one of the best choices as long as "maturity" isn't on the top of your list: Bevy - https://bevyengine.org/

Game engine written in Rust, leveraging ECS in almost every place and way, with a really capable WASM export option. Wrestling ECS for the first time might take you some time, but in my experience helps you keep game code as clean and decoupled as game code could be.

I don't see WASM/WebGPU changing anything when it comes to gaming, as an industry, personally. 3d visualizations and interactive websites? Yeah definitely a nice improvement over WebGL 2, if years late.

WebGPU is pretty far behind what AAA games are using even as of 6 years ago. There's extra overhead and security in the WebGPU spec that AAA games do not want. Browsers do not lend themselves to downloading 300gb of assets.

Additionally, indie devs aren't using Steam for the technical capabilities. It's purely about marketshare. Video games are a highly saturated market. The users are all on Steam, getting their recommendations from Steam, and buying games in Steam sales. Hence all the indie developers publish to Steam. I don't see a web browser being appealing as a platform, because there's no way for developers to advertise to users.

That's also only indie games. AAA games use their own launchers, because they don't _need_ the discoverability from being on Steam. So they don't, and avoid the fees. If anything users _want_ the Steam monopoly, because they like the platform, and hate the walled garden launchers from AAA companies.

(I work on high end rendering features for the Bevy game engine https://bevyengine.org, and have extensive experience with WebGPU)

I was working through an example in the repo for the Bevy game engine recently and came across this code

That's possible. I did spend quite a bit of time tinkering with compiler flags, and followed the recommendations.

Some notes I found just now seems to agree with my results, though: https://github.com/bevyengine/bevy/issues/3978#issuecomment-...

I cannot recommend immediate mode GUI programming based on the limitations I've experienced working with egui.

egui does not support putting two widgets in the center of the screen: https://github.com/emilk/egui/issues/3211

It's really easy to get started with immediate mode, it's really easy to bust out some UI, but the second you start trying to involve dynamically resized context and responsive layouts -- abandon all hope. The fact it has to calculate everything in a single pass makes these things hard/impossible.

... that said, I'm still using it for https://ant.care/ (https://github.com/MeoMix/symbiants) because it's the best thing I've found. I'm crossing my fingers that Bevy's UI story (or Kayak https://github.com/StarArawn/kayak_ui) become significantly more fleshed out sooner rather than later. Bevy 0.13 should have lots more in this area though (https://github.com/bevyengine/bevy/discussions/9538)

I've also been enjoying building My First Game™ in Bevy using ECS. The community around Bevy really shines, but Flecs (https://github.com/SanderMertens/flecs) is arguably a more mature, open-source ECS implementation. You don't get to write in Rust, though, which makes it less cool in my book :)

I'm not very proud of the code I've written because I've found writing a game to be much more confusing than building websites + backends, but, as the author notes, it certainly feels more elegant than OOP or globals given the context.

I'm building for WASM and Bevy's parallelism isn't supported in that context (yet? https://github.com/bevyengine/bevy/issues/4078), so the performance wins are just so-so. Sharing a thread with UI rendering suuucks.

If anyone wants to browse some code or ask questions, feel free! https://github.com/MeoMix/symbiants

These days, some game engines have done pretty well at making compute shaders easy to use (such as Bevy [1] -- disclaimer, I contribute to that engine). But telling the scientific/financial/etc. community that they need to run their code inside a game engine to get a decent experience is a hard sell. It's not a great situation compared to how easy it is on NVIDIA's stack.

[1]: https://github.com/bevyengine/bevy/blob/main/examples/shader...

This is the API you need: https://github.com/bevyengine/bevy/pull/9774