iris-aiandClaude Opus 5
1940e85c70
Profiling a move by cycles rather than by instructions says the cost is not where the last session recorded it. In `apply_scalar` the `i64` division is **0.00%** of cycles and the multiply 1.5%: the time is in `saturating_add`, which is five instructions and no vector form for an `i32`, and a box that only moved does eight of them. Asking for them one scalar at a time, each behind a match on which kind of move this is, gives the compiler four short sequences where it had four adds in a row to pair up. So a translation is now asked for once for the whole region -- which is what a translation is -- and the match happens once above it rather than per scalar. `many` over 500 frames: 684M cycles to 660M, and 1,815,666,327 instructions to 1,742,553,104. Cycle counts are worth trusting here, which is the other thing to keep: three runs of one binary varied 0.23%. It is wall time that varies 2x on this machine, not the counters, and instructions alone cannot see a stall. Checked: fmt, clippy, 105 tests, all five shrinker cases at 300 seeds, and `tabs`, `text` and `random` byte-identical at 1920x1200. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
iris
My experimental attempt at a rust ui library (also my first ui library).
It's currently designed around using retained data structures (widgets), rather than diffing generated trees from data like xilem or iced. This is an experiment and I'm not sure if it's a good idea or not.
Examples are in examples, eg. cargo run --example tabs.
Goals, in general order:
- does what I want it to (text, images, video, animations)
- very easy to use ignoring ergonomic ref counting
- reasonably fast / efficient (a lot faster than electron, save battery life, try to beat iced and xilem)
dev details
not targeting web rn cause wanna use actual nice gpu features & entire point of this is to make desktop apps / not need a web browser
general ideas trynna use rn / experiment with:
- retained mode
- specifically designed around wgpu so there's no translation
- postfix functions for most things to prevent unreadable indentation (going very well)
- events can be done directly where you draw the widgets
- almost no macros in user code & actual LSP typechecking (variadic generics if you can hear me please save us)
- relative anchor + absolute offset coord system (+ "rest" / leftover during widget layout)
- single threaded ui & pass context around to make non async usage straightforward (pretty unsure about this)
- widgets store outside of the actual rendering so they can be moved around and swapped easily (unsure about this but seems to work good for now)
under heavy initial development so not gonna try to explain status, maybe check TODO for that; sizable chance it gets a rewrite once I know everything I need and what seems to work best
it's called iris because it's the structure around what you actually want to display and colorful