axum-live-view VS webrender

I’m experimenting with a live view implementation here https://github.com/davidpdrsn/axum-live-view. Still very early but some stuff does work.

You should take a look at https://github.com/davidpdrsn/axum-live-view

Question: I see some mentions of “liveview” in a few places in the repo but can’t quite see if it’s actually working. There seem to be an example here but then these files are all empty. Is that something you’re interesting in? I’ve been exploring myself in axum-live-view.

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.