webrender VS bubbletea

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.

I recommend looking at the charm libraries. Lip gloss https://github.com/charmbracelet/lipgloss can provide the styling and bubble tea can handle the screen updates and framework https://github.com/charmbracelet/bubbletea there is a premade progress bar component in bubbles library. https://github.com/charmbracelet/bubbles

I built a TUI app to find anime scenes by image to learn the TUI framework [Bubbletea](https://github.com/charmbracelet/bubbletea)

TUI’s are awesome; I’ve used this library to build them in the past: https://github.com/charmbracelet/bubbletea

For a sufficiently-complex system, a CLI client just isn’t as powerful as a live “console”. A TUI can play the part and you don’t have to venture into the web SPA world.

If you want to build terminal app, I highly recommend the bubbletea library: https://github.com/charmbracelet/bubbletea

You can view your snippets in a human-friendly web UI that syntax-highlights the code and even renders markdown. In addition to the Web UI, the TUI (powered by bubbletea) has a file browser, code viewer and attribute editor.

A sibling comment points at https://github.com/charmbracelet/bubbletea as a Go alternative with a similar architecture

The closest thing in Go I know about is bubbletea:

https://github.com/charmbracelet/bubbletea