stretch VS kajiya

The most common is flexbox (an attempt to a cross-platform engine at https://github.com/vislyhq/stretch).

There's a few critical subtasks here: - determine the data flow model we'd like to use for our UI. We'd like to integrate tightly into the ECS, but need to figure out how to reduce the boilerplate and improve reliability around working with hierarchies. - swap our layout library. Our current dependency stretch implements the flexbox algorithm, but is unmaintained and has critical bugs :( The three main options here are to fork flex, move to the new morphorm crate, or write a layout library from scratch - consider rearchitecting our UI to be more flexible and compositional: splitting the massive Style component into several parts and moving to a "UI is a collection of behaviors" paradigm - build out more widgets! - more docs and examples!

That would probably entail integration with bevy, or some other game engine to get the UI drawn. Our TUI crate uses https://github.com/vislyhq/stretch/ to lay out the elements, so I imagine you could use that but just draw with WGPU.

Are there any plans to make yoga fully conformant to the web implementation of flexbox? For example, migrating to use stretch instead?

https://github.com/vislyhq/stretch exists, I don’t know how well it would do at all this.

There's also Kajiya, though it's very new and works on a limited range of GPUs.

I don't know how major they are considered, but Embark Studios is doing quite a bit of Rust in the open source space, most notably (IMO) rust-gpu and kajiya

I'm also aware of https://github.com/EmbarkStudios/kajiya/, which has a pretty neat documentation:

> You can't even achieve PS2-era graphics with Rust right now

That's just straight up false:

https://github.com/EmbarkStudios/kajiya

There you go

What do you think of the Kajiya renderer from Embark Studios. Is there a desire from the core developers to improve the plugin and maybe use as a default renderer?

A good example of what you can do with rust-gpu is kajiya from rust-gpu's creators. You'll notice that every shaders are not using complex enum, traits or even vector (no_std) from Rust.

I know nothing about game engines/programming/design, but I have recently read about https://github.com/EmbarkStudios/kajiya and wondered if bevy could benefit from it?

This release constitutes a massive rendering API rework. You can think of it more as a foundation that makes it easier to implement better rendering features in the future.

If you check the release notes[0], you'll see HDR/Bloom support was dropped at the last minute, and several other major rendering features are still pending implementation.

The great part about Bevy is that it's modular, so you can swap out the renderer if you like. There's already several people using Bevy with Embark's kajiya renderer[1].

[0] https://bevyengine.org/news/bevy-0-6/#what-s-next-for-bevy

[1] https://github.com/EmbarkStudios/kajiya