vtebench
accesskit
vtebench | accesskit | |
---|---|---|
5 | 24 | |
284 | 926 | |
0.0% | 1.6% | |
0.0 | 8.8 | |
over 1 year ago | 3 days ago | |
Rust | Rust | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vtebench
-
Just How Much Faster Are the Gnome 46 Terminals?
https://github.com/alacritty/vtebench/tree/master
-
Show HN: Warp, a Rust-based terminal for the modern age
Hey - that's a good point. The thing about terminal benchmarks is that there are many of them, each focusing on a different aspect and producing different results. There's one by alacritty team[1] that we used in our initial tests[2], there's another ones mentioned in the comments above etc. When using vtbench, Warp performed much better than iterm, for example.
Ideally we'd ace all of them, but we're not there yet. Anecdotally, many of our users mention speed/performance improvements over other terminal apps a lot in our Discord!
[1] https://github.com/alacritty/vtebench
-
How Warp Works
The diagram below shows the output of vtebench for scrolling in various terminals. For some reason Hyper generally could not handle running the benchmarks at all and did not terminate after a reasonable amount of time.
-
Top 3 GPU-Accelerated Terminal Emulators
It's not easy to measure the performance of terminal apps. But I definitely notice a difference compared to let's say iTerm2, especially when scrolling through large files in Vim. Alacritty claims that it's faster than the competition using vtebench as a benchmarking tool. Kitty claims that the CPU usage is slightly increased compared to xterm (6-8% compared to 5-7%), but that scrolling is smoother.
- Alacritty vs Kitty
accesskit
-
Looking for this. html + css rendering through wgpu.
If you were to implement this yourself, i'd look into either swash or cosmic-text for the text rendering stack (this is one of the things you really don't want to write from the ground up). For accessibility, AccessKit has quickly become the standard for communicating with crossplatform accessibility APIs in rust GUI. lightningcss (or its lower level counterpart cssparser) are both decent options for CSS parsing. Taffy handles some of what browsers offer for a layout engine, but is still being worked on.
-
JetBrains Noria
> Fleet relies on the Java AWT/Swing framework to get a window from an operating system, but it doesn’t use the Java platform for managing its GUI components besides one JFrame and JPanel on top of it.
This is a terrible decision that is going to bite them in the long run. Doing things this way makes it far, far more difficult to implement accessibility, and regulations on this are only going to get stricter.
Implementing accessibility for a framework like that would involve three separate implementations for three separate platforms and the need to interface with D-Bus, COM and Objective C, from Java. I imagine that the latter two would be particularly difficult, considering how bad Java's FFI support is. It's not just calling methods either, you'd actually need to implement your own classes that conform to the relevant COM interfaces / Objective C protocols. There are libraries that can help with this[1], but I don't think they would work particularly well for something as complex as a code editor.
[1] https://github.com/AccessKit/accesskit
-
fltk-accesskit: AccessKit integration for fltk
fltk-accesskit is an accesskit integration crate for fltk-rs, the gui crate. It's implemented as an external crate to allow for more experimentation before stabilizing the api, especially since fltk is at version 1.4.
- AccessKit - Cross-platform accessibility infrastructure
- Emerging Rust GUI libraries in a WASM world
-
We're building a browser when it's supposed to be impossible
Libraries for a lot of this stuff exist (albeit in many cases not very mature yet):
- https://github.com/pop-os/cosmic-text does text layout (which Taffy explicitly considers out of scope)
- https://github.com/AccessKit/accesskit does accessibility
- https://github.com/servo/rust-cssparser does value-agnostic CSS parsing (it will parse the general syntax but leaves value parsing up to the user, meaning you can easily add support for whatever properties you what). Libraries like https://github.com/parcel-bundler/lightningcss implement parsing for the standard css properties.
- There are crates like https://github.com/BurntSushi/bstr and https://docs.rs/wtf8/latest/wtf8/ for working with non-unicode text
We are planning to add a C API to Taffy, but tbh I feel like C is not very good for this kind of modularised approach. You really want to be able to expose complex APIs with enforced type safety and this isn't possible with C.
-
XUL Layout has been removed from Firefox
There are a number of up-and-coming Rust-based frameworks in this niche:
- https://github.com/iced-rs/iced (probably the most usable today)
- https://github.com/vizia/vizia
- https://github.com/marc2332/freya
- https://github.com/linebender/xilem (currently very incomplete but exciting because it's from a team with a strong track record)
What is also exciting to me is that the Rust GUI ecosystem is in many cases building itself up with modular libraries. So while we have umpteen competing frameworks they are to a large degree all building and collaborating on the same foundations. For example, we have:
- https://github.com/rust-windowing/winit (cross-platform window creation)
- https://github.com/gfx-rs/wgpu (abstraction on top of vulkan/metal/dx12)
- https://github.com/linebender/vello (a canvas like imperative drawing API on top of wgpu)
- https://github.com/DioxusLabs/taffy (UI layout algorithms)
- https://github.com/pop-os/cosmic-text (text rendering and editing)
- https://github.com/AccessKit/accesskit (cross-platform accessibility APIs)
In many cases there a see https://blessed.rs/crates#section-graphics-subsection-gui for a more complete list of frameworks and foundational libraries)
-
A new open-sourcing project launches!!! A declarative, compose-based and cross-platform GUI
Using HarfBuzz makes sense. But if you're looking for a pure-Rust alternative, I hear cosmic-text (made by Pop!_OS) is good. There's also AccessKit for accessibility.
-
GPU-Backed User Interfaces
There are efforts to support a cross platform accessibility library:
https://github.com/AccessKit/accesskit
-
Egui 0.20 Released
egui is an easy-to-use immediate mode GUI for Rust, and I just released 0.20. It's a big release!
There is now support for AccessKit (https://github.com/AccessKit/accesskit) which brings accessibility to egui (a first for an immediate mode GUI?).
There is also better table support, nicer keyboard shortcut handling, better looking text in light mode (still not great, but better).
See more in the changelog: https://github.com/emilk/egui/blob/master/CHANGELOG.md
Try it out at www.egui.rs
What are some alternatives?
vte - Parser for virtual terminal emulators
widevine-l3-guesser
Warp - Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
elm-architecture-tutorial - How to create modular Elm code that scales nicely with your app
glassbench - A micro-benchmark framework to use with cargo bench
femtovg
warp - Secure and simple terminal sharing
gyroflow - Video stabilization using gyroscope data
benchmark-scratchpad - A quick scratchpad for benchmarking Rust code
Nu - Repository hosting the open-source Nu Game Engine and related projects.
upterm - A terminal emulator for the 21st century.
chibi-scheme - Official chibi-scheme repository