swiftshader VS slint

Is it really true that those bugs aren't getting fixed? There's a commit from July 18th to SwiftShader that seems to be addressing exactly the bug described in the blog post:

https://github.com/google/swiftshader/commit/4e401427f8dd799...

If your GPU does not support Vulkan you can still do some experimenting with a CPU renderer. I've used swiftshader a lot, it's a bit of a pain to compile, but once you manage to do so you can compile and run Vulkan code almost the same as if you had a compatible GPU. The performance of course is not great, but it's better than nothing.

swiftshader by Google (link):

You also don't get extensive support for various hardware for free – good luck running a Vulkan GUI on a pre-GCN AMD card or a sufficiently old NVIDIA one without a compatibility layer of sorts, which would require bothering with Vulkan Portability (i.e. missing certain Vulkan features due to it being implemented via an older API). The only alternative to that is SwiftShader (which would throw your extremely fast GUI aspirations right outta the window).

That's like saying no one needs a GPU anymore because Swiftshader exists.

Btw, if anyone's interested, here's the link to that branch: https://github.com/google/swiftshader/tree/legacy-d3d9

Yeah, there's still a fallback option through the use of Swiftshader if GPU accelerated vulkan isn't an option. If you use Vulkan for GUI, then it'll be fine to use Swiftshader, but if you're trying to play a game on Swiftshader, it'll likely struggle and probably fail.

The fix is https://github.com/flutter/engine/pull/25205 to use soft renderer SwiftShader instead of DXD9 on low-end PCs

Google’s version is SwiftShader

Did you get a chance to check https://slint.dev?

Disclaimer: I work for Slint

Currently, we do it by using binaries through napi-rs so we can bring in a window using the platform native API. And then we do some hack to merge the event loops.

But if Deno supports bringing up a window directly, this means we can just ship wasm instead of native binary for all platform. And also I hope event loop integration will be simplified.

Although we'd also need more API than just showing a window (mouse and keyboard input, accessibility, popup window, system tray, ...)

[1] https://slint.dev

Rich Text content is not yet implemented. This is tracked in https://github.com/slint-ui/slint/issues/2723

Thanks for reporting the broken link. Fixed in https://github.com/slint-ui/slint/commit/9200480b532f49007d2...

With Slint (https://slint.dev) we're trying to make a lightweight toolkit that doesn't use HTML/CSS. And that you can program either from low level languages such as C++ or Rust. As well as with higher level language such as JavaScript, and we want to extend to python too.

I haven't. I was just searching for a GUI library that was Bevy-compatible and slint isn't at the moment: https://github.com/slint-ui/slint/discussions/940

Sorry!

Trying to do that with Slint: https://slint.dev

You can do that with Slint (https://slint.dev) and its linuxkms backend. No need for a xorg server or wayland compositor, just run the application made with Slint from the init script.