webrender VS Slint

This source code:

https://github.com/servo/webrender/blob/master/wr_glyph_rast...

suggests to me that the glyph rasterization (which is the CPU-limiting factor for text rendering) in WebRender (which is the new FF 93+ GPU-accelerated rendering engine) is implemented in Rust and to be run on CPU.

Both Servo and Fifefox make use of webrender, which is an awesome piece of tech and is well suited to render a web page. Some GUI projects attempted to use webrender directly as well, like Azul and moxie-native

Surprised noone mentioned https://github.com/servo/webrender

Firefox article outlining which parts use Rust https://wiki.mozilla.org/Oxidation#Within_Firefox Servo/WebRender, the 2d renderer used by firefox: https://github.com/servo/webrender

Hi, what do you think about using webrender instead of wry on desktop? That is, instead of a full featured browser, just the bare minimum to render the DOM.

This is in the context of rust.

> it adds a line to a `go.sum` while with a hash of the code at the version specified

Cargo.lock also contains a checksum

> You can distribute your code without a copy of the dependency

Also true in rust, and the default way of using rust.

> If the hashes are different, an error is thrown.

Also true in rust.

For an example of what this looks like: https://github.com/servo/webrender/blob/54b725be37f13b166946...

You haven't described anything different between go and rust in your comment since every feature you've pointed out applies equally to both.

Yes! This is because web browsers use the platform text input stack

Browsers are a great example of cross-platform UI, because they sprinkle platform-native widgets throughout the canvas that they render. Which reminds me that people were trying to use webrender[1] to build native apps in Rust.

[1] https://github.com/servo/webrender

What more can be done, besides site isolation and ASLR+DEP? Oh wait, Mozilla rewrote the damn renderer in a better language than C(++), that seems like a good way to prevent issues.

As an anecdote, the three top contributors to sixtyfps are ex-Qt people. I think it is not anecdotal that there is at least some degree of overlap and competition between Rust and C++, and that this is a market that surely The Qt Company is watching.

SixtyFPS (https://sixtyfps.io/) is in progress for Rust, but it is still early days. It also does not technically use a native toolkit (it uses Qt), but I believe that might be on roadmap. For traditional GUI apps, I think the lack of a table or tree widget is the most limiting for the time being. They have stated they intend to remedy that.

The most promising GUI hasn't been posted here, SixtyFPS. It's in it's early stages and not FOSS, but it's built by some ex-QT cats and has a lot of potential.

People have been recommending https://sixtyfps.io/ to me.

There is already a project to make a Qt like GUI toolkit in Rust: https://sixtyfps.io/ It is really similar to Qt https://sixtyfps.io/releases/0.1.5/docs/rust/sixtyfps/index.html

People are doing that too. https://sixtyfps.io/ is basically a Qt clone in Rust, actually developed by previous Qt developers.

spdlog, a pretty useful and more and more commonly used logging library for C++.\ SixtyFPS, an emerging GUI library for Rust, but you can use it in multiple languages. It uses OpenGL or Qt currently as backend (well, it's a new library and they wanted two from the get-go to make sure their abstractions are done right/well enough). They started a company this year for it too.

Just so some are not aware, there's a new project called sixtyfps by some people who were in the Qt world for long. I didn't take a deep dive into it but it looks promising.