Rendered at 18:14:12 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
bhouston 21 seconds ago [-]
Does this have:
- Accessibility? E.g. Screen reader support? Alternative inputs?
- Full keyboard support?
- Full internationalization, including right-to-left and diacritics?
What happens when no GPU is available?
Just curious as this matters for it to be a serious library and not a proof of concept.
mik3y 36 minutes ago [-]
Sort of a digression, but it's the first time I've seen something like this:
> We don't take pull requests. Have your agent open
> an issue describing the bug or idea, and our agents
> usually turn it around fast.
Pretty interesting approach, compared to receiving a zillion potentially sloppy PRs. Open source in the age of LLMs.. ("agent source"?)
CSSer 9 minutes ago [-]
It sounds like a black hat penetration tester's nirvana. All you have to do is open the right issue to trick the model into installing the right security vulnerability or backdoor, or better yet, a series of small security vulnerabilities that can be chained to create a tailor-made exploit. It's practically a hacker's choose-your-own adventure.
notnullorvoid 17 seconds ago [-]
I suspect they'd be manually filtering which issues/features their agents attempt to fix/implement. Otherwise you end up with all sorts of features that simply make no sense for the project.
The approach is at least better than accepting slop PRs that could have backdoors injected into them.
rgbrgb 31 minutes ago [-]
> Every app can run headless, so an agent can render to PNG, dump the element tree and drive it with scripted input.
This is cool. I hope SwiftUI / UIKit borrow this idea for native mac apps.
owenbrown 38 minutes ago [-]
How should I think about this, compared to GPUI (https://gpui.rs)?
What are pros and cons?
geoah 41 minutes ago [-]
Looks interesting, especially the headless part. Been building various apps lately for ios/ipados/macos for personal use and I would love something like this that would be truly cross platform. Xcode with agent use has been really nice to work with, and t3.code support for emulators has been amazing to use.
bovermyer 43 minutes ago [-]
So it's a UI framework by agents, for agents?
piker 23 minutes ago [-]
> native GPU-rendered Rust UI
Sorry, what? I feel like I've studied the Rust UI ecosystem pretty well, and the examples look nice, but if I've learned anything it's that "native" and "GPU-rendered" are oxymoronic.
Likely the fonts will be fuzzy on various platforms, accessibility will be under-baked and it will land in the bucket with every other UI framework depending on winit. I like the personalities at anomaly, but I'm quite confused about what's even driving a decision to build something like this versus contributing to egui, GPUI, Iced, etc.
hmry 16 minutes ago [-]
Yeah. Presumably "native" here just means "not Electron", which is the sales pitch for most AI-generated Rust libraries these days. ("Tell your agent to rewrite your Electron app into Rust~! :rocket emoji:")
esafak 14 minutes ago [-]
I was thinking "Builds and tests with a fast-moving Rust code base like this must be painful", then I noticed the total absence of tests: https://github.com/anomalyco/rune/commits/dev/
Indeed. But why not run the tests in CI when merging to master?
esafak 3 minutes ago [-]
They ain't running in CI.
rvz 26 minutes ago [-]
This is what a vibe coded UI framework looks like.
Have a read of the clean documentation that they never wrote or read. [0]
All the clean code, architecture principles thrown out of the window in favour of hundreds of code smells, anti-patterns, zero tests, and tons of unmaintainable slop.
The site is wild, but the little triangles in the bottom right corners of each window don't work properly on chrome desktop in windows 11. They aren't clickable, you can only resize the windows horizontally. Which seems weird considering how polished the rest of it looks.
- Accessibility? E.g. Screen reader support? Alternative inputs? - Full keyboard support? - Full internationalization, including right-to-left and diacritics?
What happens when no GPU is available?
Just curious as this matters for it to be a serious library and not a proof of concept.
The approach is at least better than accepting slop PRs that could have backdoors injected into them.
This is cool. I hope SwiftUI / UIKit borrow this idea for native mac apps.
Sorry, what? I feel like I've studied the Rust UI ecosystem pretty well, and the examples look nice, but if I've learned anything it's that "native" and "GPU-rendered" are oxymoronic.
Likely the fonts will be fuzzy on various platforms, accessibility will be under-baked and it will land in the bucket with every other UI framework depending on winit. I like the personalities at anomaly, but I'm quite confused about what's even driving a decision to build something like this versus contributing to egui, GPUI, Iced, etc.
e.g. https://github.com/anomalyco/rune/tree/dev/crates/rune-kit/t...
Have a read of the clean documentation that they never wrote or read. [0]
All the clean code, architecture principles thrown out of the window in favour of hundreds of code smells, anti-patterns, zero tests, and tons of unmaintainable slop.
[0] https://github.com/anomalyco/rune/blob/dev/crates/rune/READM...