Rune: A native GPU-rendered Rust UI framework for macOS, Windows, Linux and web

Posted by mik3y 1 day ago

Comments

Comment by nicoburns 22 hours ago

If you're interested in a GPU-rendered Rust UI framework, then maybe skip this vibe coded project, and check out some of following established projects:

  Rust-native GUI frameworks (by crates.io downloads):

   1. egui (30.3M total / 9.2M last 90 days)
      https://crates.io/crates/egui

   2. Iced (3.2M / 770k)
      https://crates.io/crates/iced

   3. Slint (2.4M / 955k)
      https://crates.io/crates/slint

   4. GPUI (447k / 255k)
      https://crates.io/crates/gpui

   5. Dioxus Native (181k / 26k)
      https://crates.io/crates/dioxus-native

   6. Freya (49k / 12k)
      https://crates.io/crates/freya

   7. Floem (45k / 15k)
      https://crates.io/crates/floem

   8. Vizia (7k / 700)
      https://crates.io/crates/vizia

List is hand-picked list, ordered by crates.io downloads. I had an LLM fetch the download counts and links. Webview based UI like Tauri and Dioxus Desktop are excluded. As are bindings to native toolkits and GTK.

Comment by bryanlarsen 21 hours ago

IMO, the top GUI framework crates for Rust are windows or native-windows-gui, objc2 or icrate for MacOS and gtk4-rs for Linux only. Actually for MacOS / iOS I'd use uniffi to embed the rust core in a SwiftUI app.

In 2026 IMO it's much better to use an LLM to keep 3 separate native front ends in sync than it is to try and use any sort of cross platform UI.

Comment by the__alchemist 15 hours ago

Could you please explain why? For example: Is it colors? A je-ne-sais-quoi? Widget rounding size and fonts? Performance reasons? Keyboard shortcuts? Do you really find it's easier to maintain 3 separate frontends using an LLM than using EGUI, GPUI, QT etc?

I have seen this suggestion several times recently regarding GUI framework threads on HN in the past week (There has been a surge!), but they are always described in the way you did: With no explanation of why. Just an assertion that native UI kits (of which you need a separate one for each OS family) are superior; cross-platform kids are an "inferior experience" etc. I have asked at 3 times and received no answer. I say this as someone who uses both Windows and Linux regularly, and find they are functionally equivalent once you have an application launched. There are ABI differences, driver differences, file system differences, etc which need to be smoothed over with feature gates for certain application functionality, if you're using certain functionality.

I want my applications to have the required functionality, run fast, and have a good UI. I don't care if the widgets look the same as on my other applications or the ones built in to the OS; this isn't even a thing because there is so little standardization broadly. Maybe on Macs it's standardized and cross-platform kits look out of place?

The proposed approach of "Use LLMs to vibe-code a system of 3 native kits" has cons to weigh. Or making your program Windows only or w/e for a look-and-feel reason or whatever it is has cons too. IMO all our OSes are so similar, PC software should almost all be cross-platform. Exceptions are mostly drivers and driver-adjacent code.

Comment by grub5000 8 hours ago

Windows and Linux actually feel pretty close these days, and I don’t generally feel any friction switching between them. But when I try to use a Mac it’s another story entirely. That OS just makes no sense to me - the keyboard shortcuts all seem to be insanely bad choices, just inconsistent with huge gaps and divergences from the other OSs. It feels so stuck in the 90s

Comment by the__alchemist 2 hours ago

This checks out. My leading mental model to explain this mismatch is that the critique has been from people who are expecting Mac idioms, which I can't speak to. Window and Linux GUI look/feel are fragmented as-is.

Comment by kleeklee 21 hours ago

Keeping 3 separate native front ends in sync with custom visual components means you end up building a cross-platform UI. The only apps you can build without custom components are trivial ones.

Comment by bryanlarsen 20 hours ago

All 3 have a way of embedding webviews. In my perhaps limited experience, all desire for custom visual components are either specious or for read-only presentation views. In my opinion all controls should be native, but if you ask for a fancy data presentation I have no qualms reaching for a webview.

Comment by jasomill 19 hours ago

So long as the web views provide for accessibility (and thus UI automation), this sounds perfectly reasonable for the majority of applications.

Speaking of which, my dream is an "HTML light" standard with a subset of functionality specifically designed for local UI use, ideally with lightweight non-browser engines supporting this standard shipping with all major OS platforms as shared system components.

We had browsers that ran on systems with 8 MB RAM, after all, and while it's not a fair comparison, there's no technical reason why a system with three orders of magnitude more RAM should struggle to run more than a handful of applications merely because they use HTML and JavaScript for rendering.

Comment by nicoburns 19 hours ago

I am building such a lightweight browser engine: https://github.com/dioxuslabs/blitz. It targets most of HTML/CSS, but leaves out (or makes optinal) a lot of the extra stuff that browsers pull in). It also has the option to use Rust instead of JavaScript for the scripting layer.

Though 8 MB RAM is a non-starter when a single RGBA texture @4k is ~30Mb and modern system often require 2 or 3 for buffering. Somewhere around the 60MB to 100MB mark seems to be the base for modern setups, at least on macOS.

Comment by simonask 19 hours ago

> perhaps limited experience

New rule: Programmers with limited UI experience (that includes myself) should abstain from weighing in on what UI designers and programmers need.

Comment by tadfisher 21 hours ago

An advantage of this approach is that everyone's screen readers and other accessibility tools actually work with your app.

Comment by treyd 21 hours ago

There's also relm4 which builds a Elm-like paradigm on top of gtk4-rs.

Comment by nextaccountic 15 hours ago

rather than gtk4-rs maybe try relm4

Comment by auraham 20 hours ago

https://crates.io/crates/dioxus-native was released 3 months ago and does not have a link to GitHub, I do not think it can be considered as established project yet.

Comment by nicoburns 19 hours ago

(I am the maintainer of dioxus native, and also posted the comment above)

So:

- The initial version was released over a year ago (3 month is the most recent patch release of the stable version).

- It is part of the Dioxus project (https://github.com/dioxuslabs/dioxus) which has been going since 2021 (but the other renderers are web/webview based).

- The native renderer (https://github.com/dioxuslabs/blitz) has been under development since December 2024 (building a whole new web engine is just a big project).

You're ultimately kind of right that it's not as established as 1-4 in the list. But I think it justifies it's place with the other frameworks lower down the list as one of the lesser-known frameworks that compete technically with those further up the list.

Comment by nextaccountic 15 hours ago

Is dioxus native usable in android already?

Comment by kdienxiendkw 17 hours ago

[flagged]

Comment by nicoburns 16 hours ago

It's absolutely in good faith. There are two kinds of GUI framework in Rust:

- Those people have poured consistent time and effort into over a period of years

- Those people vibe code into existence in a couple of weeks and typically abandon after a few months.

Nobody wants to waste their time on the latter, so I am pointing people to the former. Yes, mine is one of them, but that doesn't make it bad faith, it just means I know what I'm talking about.

Comment by pentaphobe 13 hours ago

You've the patience of a saint to respond so politely to abrasiveness

And thanks for sharing the list and saving me from clicking on yet more half baked vibe spam!

Comment by plaguuuuuu 2 hours ago

most downloaded is a poor metric

Comment by drnick1 18 hours ago

Stick to Qt, none of those solutions are mature enough for actual production use.

Comment by satvikpendem 11 hours ago

Lots of companies use them in production.

Comment by amelius 18 hours ago

Slint is proprietary. Given that AI makes it so easy to spec out and build even entire GUI frameworks, why would you even go with proprietary anymore? And why doesn't the article showcase a full-fledged set of UI components?

Comment by dmantis 6 hours ago

I might be wrong, but I believe Slint has qt-style dual-licensing and provides AGPL version for GPL projects.

I assume you make an open source project giving the critics about proprietary nature, so it shouldn't be a problem.

Comment by ogoffart 11 hours ago

[dead]

Comment by xedrac 4 hours ago

> AI makes it so easy to spec out and build even entire GUI frameworks

When a vibe coded gui framework becomes so good that it simply cannot be ignored, I'll believe this can work. Until then, all I've seen is half-baked disposable slop that looks really good on paper.

Comment by noodletheworld 16 hours ago

> List is hand-picked list, ordered by crates.io downloads.

O_o

Just say it’s a hand picked list of ones you like and why.

Do you like them? Have you used them?

I found iced to be unreliable (couldn't reliably render basic widgets); slint overly relies on their DSL and honestly seemed to be moving away from rust; and GPUI felt sloppy. That was my personal “lets try rust gui” journey before I went; nope, guess we’re doing native ui and a shared rust core.

This is just a random list of stuff; I can't tell if you think they're all good (I dont) or just copy pasted chatgpt output.

For each one: why is it on the list? Do you like it? Why do you think, for example, slint, deserves to be on the list, when you dont even write the ui scripts in rust?

Comment by ogoffart 11 hours ago

(Slint author here) Slint is written in Rust, and Rust API is at its core. That's not changing. What's wrong with the DSL? the UI is described in the DSL, the application logic in Rust. I wrote about why here: https://slint.dev/blog/domain-specific-language-vs-imperativ...

What gave you the impression we're moving away from Rust?

Comment by noodletheworld 8 hours ago

The website developer docs.

Look, bluntly, you can’t have your cake and eat it to. Either it’s a rust library or it’s not.

If you’re not writing your ui in rust, then even if parts of it are implemented in rust, it’s not a rust ui library any more than a js library like calls a c backend is a c library.

I really really wanted to like slint and absolutely did not.

> Domain Specific Languages like Slint offer a great alternative to traditional GUI toolkit APIs.

No they don’t.

If you can arbitrarily assert something so can I.

A DSL needs it clear the minimum bar of “why is this not just using a real programming language?”.

UI programming is tricky, but declarative approaches have almost universally failed, because there’s always some edge case logic that needs a full programming language to handle it.

The few UI DSLs that Ive seen work (eg. blueprint) exist a) as stand alone languages, and b) fill a niche that an existing language doesn’t.

What does your DSL do that is unique? Why was using js like qt quick not good enough? Why not just use rust?

The issue I have with it is you’ve never articulated why it exists.

Good DSLs like those implemented using clojure (1) are additions to the language that can natively be mixed into the existing language ecosystem.

You could have done the same in rust using proc macros; but instead you’ve chosen (as far as I can tell) to chase the non-rust UI market with a custom DSL.

Well.. you want an opinion? There you go. I don’t like slint, sorry. It’s not a rust UI library. It just happens to be implemented in rust, in my opinion.

(1) - https://clojure-doc.org/articles/cookbooks/growing_a_dsl_wit...

Comment by ogoffart 7 hours ago

> Either it's a rust library or it's not.

It is one. Your app is a Rust program that depends on a crate. The UI compiles to Rust code, and we also have the `slint!` proc macro.

> there's always some edge case logic that needs a full programming language

Right, and that language is Rust. The DSL only describes the GUI. You operate it from Rust.

> Why was using js like qt quick not good enough?

QML was the inspiration. I worked on Qt and wrote QML bindings for Rust before (qmetaobject-rs). Slint is a new take on it, compiled ahead of time, no GC, strongly typed.

Comment by noodletheworld 6 hours ago

> The UI compiles to Rust

Right, so not rust.

Languages that compile to c are not c.

Languages that compile to rust are not rust.

> QML was the inspiration

Yes, except you invented a new programming (1) language unnecessarily.

Whatever.

We'll have to agree to disagree.

If the programming language you write is not rust it is not a rust ui library.

Slint requires you to write your UI in slint. I havent used it much, but Ive used it enough to know that this:

> The DSL only describes the GUI

Is about as disingenuous as you can get.

Thats like saying that javascript only describes the GUI of a website, a backend rust website is really just a rust application. Really you're building in rust. React is really a rust UI library at heart. <—- obviously BS.

(1) - https://docs.slint.dev/latest/docs/slint/guide/language/conc...

Comment by eaf7e281 16 hours ago

It seems like self promotion, but in a smart way.

https://news.ycombinator.com/item?id=50394569#50398826

Comment by HackerThemAll 20 hours ago

Yeah, have you tried to do anything in egui? I tried today a ComboBox, but I wanted one with filter input box, "X" icon to clear it, and automatic focus.

I've given up when the code reached 300 lines and was still buggy/not working.

egui is not mature. I'd prefer declarative approach, data binding, and styling. Therefore will skip egui.

Comment by slopinthebag 20 hours ago

i've built pretty complex stuff in egui. any modern agent will one-shot that component, so i'd say it's more just a lack of familiarity with the library.

Comment by jbirnick 19 hours ago

Luckily GPUI isn't vibe coded at all but a mature and well thought-out project.. /s

Comment by hmry 18 hours ago

I tried using it and yeah, GPUI felt very sloppy. Something about that lack of documentation + having to install it from some subdirectory in a giant monorepo + Tailwind-based API...

And the recommended component library for it (GPUI Kit) seems to have been 100% Clauded, down to the website and README.

Comment by nextaccountic 15 hours ago

the component library is gpui-component which I think is a too old of a project to have been built primarily by AI

gpui-kit is meant to solve your second point: installing it from crates.io rather some unrelated monorepo

it doesn't matter if gpui-kit is vibe coded because it's just upstream gpui, repackaged

Comment by hmry 15 hours ago

Hmm, I see, thanks for the correction

Comment by Varelion 21 hours ago

Brutal and based

Comment by mik3y 23 hours 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"?)

Comment by atrokhymchuk 22 hours ago

I find this line pretty sad actually, what if someone wants to contribute code, written by hand? What if some beginner finds this project interesting and wants to invest own time into it?

Or human is completely removed from the development whatsoever..

Comment by JoshTriplett 21 hours ago

> I find this line pretty sad actually, what if someone wants to contribute code, written by hand? What if some beginner finds this project interesting and wants to invest own time into it?

Then they would be better off contributing to a project that welcomes them.

Comment by dsagent 22 hours ago

While I sympathize I think we all know a majority of contributions would not be hand written. This is optimizing for the reality we're in.

You could fork and reference it in the issue if you still wanted to contribute.

Comment by viraptor 20 hours ago

> what if someone wants to contribute code, written by hand?

It's up to the maintainer. Sometimes it's just easier to listen to what's needed and do it the way you know and are efficient with than to review someone else's code.

> What if some beginner finds this project interesting and wants to invest own time into it?

There's nothing stopping them. They can even publish it in a fork.

Comment by ksh09 11 hours ago

Why would any beginner want to contribute or invest a large amount of time where he doesn't trust a maintainer or their processes?

Comment by hmry 22 hours ago

Yep. There's other projects that have a "we want your ideas, but not your code" policy (like SQLite and Lua), but the "just tell your agent to tell our agent what to do" framing makes me depressed.

Comment by varispeed 18 hours ago

Why would you contribute code written by hand in 2026?

Comment by IOT_Apprentice 20 hours ago

Just take your hand written code and have it send it as the request to the AI.

Comment by devmor 21 hours ago

Why would you want to contribute thoughtfully written code to a slop project?

Comment by DoesntMatter22 22 hours ago

Those days are over

Comment by kodablah 21 hours ago

I did the same for a vibecoded project [0] but I would never do this for a human-written project. Simply put, if most contributions are similarly vibecoded and/or they will be reviewed/treated as such, then how is a PR/review from an unaffiliated agent any better than one managed by the project curator. Of course that human curation still needs to occur.

This is a natural progression (only on these types of projects). We accepted contributions because it actually helped and they were difficult and time consuming. When that is no longer the case, contributions are a burden, the actual problem/idea is the real value, hence the request to open the issue.

0 - https://github.com/cretz/vitaslop

Comment by dabinat 15 hours ago

Won’t this just lead to bloatware in the long run? Part of creating a product is knowing what to say no to. And I’ve found my customers’ ideas for how to improve my products aren’t always the best way to implement the feature they want (or it would create issues for other customers who use it differently).

Comment by satvikpendem 11 hours ago

They never said they'd merge in every idea.

Comment by teekert 20 hours ago

I had a Nix issue. Agents fixed it in 5 min.

Of course, one could conclude that another agents screwed up before, still was a good experience.

Comment by CSSer 23 hours 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.

Comment by bhouston 22 hours ago

I am not sure about that.

Which gate is easier to maintain?

1. Check issues for malicious intent

2. Check PR for malicious intent.

I think in PR requests it is easier to introduce purposeful bugs or obfuscated code than it is to hide them in issues.

So I think gating on issues is easier and more secure.

Comment by notnullorvoid 23 hours 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.

Comment by sebzim4500 22 hours ago

That seems a lot harder than if they accepted PRs like everyone else

Comment by travisgriggs 21 hours ago

Makes this (not a real) job posting seem all the more funny/relevant:

https://lovro-bikic.github.io/software-line-specialist/

Comment by rbehrends 21 hours ago

My main concern with this would be that for a library in particular I need a stable API and behavior (Hyrum's law). I do not know to what extent a fully autonomous agentic approach can ensure that. Note: I don't see a problem with preferring issues over pull requests (many of which would be poorly coded slop), just fully automating the handling.

Also a bit wild to assume that no person will just create an issue manually. This is not something I'd normally use an agent for.

Comment by rgbrgb 23 hours 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.

Comment by viraptor 20 hours ago

You can do the same thing with swiftui. The surface you render to doesn't have to be visible at all. And the tree has nice introspection available.

Comment by 0x457 22 hours ago

Headless part is neat, but agents can already drive apps and take screenshots. As a side note, I have agent driving android tv using wireless adb and hdmi capture card + mpv rpc, its fun to watch.

Comment by 22 hours ago

Comment by owenbrown 23 hours ago

How should I think about this, compared to GPUI (https://gpui.rs)? What are pros and cons?

Comment by winstonp 22 hours ago

Dax on Twitter: "we just couldn't get gpui to look good enough"

Comment by grub5000 4 hours ago

Has GPUI development even picked up since the Zed team gave up on it? The GPUI website still links directly to the Zed repo's subfolder. I can't tell if there's even one coherent GPUI project any more

Comment by bhouston 23 hours 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.

Comment by jmvoodoo 22 hours ago

The most common rust UI framework I’m aware of, iced, completely fails on these metrics afaik.

Comment by eviks 12 hours ago

Egui is an order of magnitude more common than iced

Comment by geoah 23 hours 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.

Comment by skolos 22 hours ago

What is benefit of GPU-rendered UI? In regular 2d apps where I can select enable/disable GPU rendering, disabling doesn't make app feel slower, but it drastically reduces RAM and VRAM usage (VRAM is the one I care about, as I run local models). Why so many UI frameworks brag that they are GPU-rendered?

Comment by MayeulC 22 hours ago

Well, for one, it usually is much more energy-efficient: longer battery life, cooler computers, and more responsive under heavy (CPU) load.

Comment by devilsdata 22 hours ago

Other people have different hardware and different goals. A year or so ago I worked on a Linux laptop that was dog-slow. If I didn't enable GPU-rendering for the UI, it competed for the very limited CPU.

Comment by nicoburns 22 hours ago

Using less power is generally the main benefit. On lower end hardware you may also notice a performance difference, depending on what the UI is trying to display.

Comment by dahrkael 22 hours ago

composition with transparencies is the main one

Comment by piker 23 hours 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.

Comment by nicoburns 22 hours ago

It's definitely possible to do sharp fonts in the Rust GUI ecosystem (although you certainly won't get it out of the box). With the native text libraries if you want to (both Servo, Zed/GPUI, and anything using Skia do this), or emulated with Skrifa + Vello.

But I agree with the reset

Comment by hmry 23 hours 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:")

Comment by etaioinshrdlu 20 hours ago

When I made my ow GPU-renderered framework I found that it was possible to render the entire UI in one call/shader to the UI. All primitives and styles can be passed as a updatable data blob that the single GPU shader handles in one call. Do most of the GPU-rendered frameworks do it this way?

It has some tradeoffs to consider but seems quite good overall.

Comment by williamcotton 20 hours ago

Re: Use it with your agent

An approach I've found useful, albeit for a DSL that ships a binary for execution, is to give a way for the LLM agent to get a high-level topic list so it can drill down all the way to specific language/API implementation details.

Perhaps with this project the author could make a website that does the same?

Comment by the__alchemist 22 hours ago

Broadly: In what circumstances, use cases, preferences etc would I use this instead of EGUI or GPUI?

The double-edged sword of choice!

Comment by DoesntMatter22 22 hours ago

I'd like to know this too. I'm building a egui app and it's fantastic. I have tons of custom drawing and stuff though

Comment by GaronG 22 hours ago

It would be fun to port some apps over to this, I'm worried at the speed it moves, It would be hard to settle on a commit. I'd rather fast updates over slow, but I feel like I'd have very little trust on this between updates, especially how many things could be broken after updating.

Comment by ricardobeat 17 hours ago

Is this related to https://rune.build which was also developing their own rendering layer?

Comment by ernestrc 38 minutes ago

It isn’t. Rune is written in Go, and completely unrelated.

Comment by mrpotato 22 hours ago

Rune, the rust ui framework, not to be confused with Rune, an embeddable dynamic programming language for Rust

Comment by portaltonowhere 22 hours ago

Not to be confused with Rune, the development environment [0].

[0]: https://rune.build/

Comment by efficax 22 hours ago

What does "native" mean to these people. Native UI means using the widgets provided by the operating system. This is not that.

Comment by eska 22 hours ago

Changing times. Nowadays a lot of software UIs are developed by people with a web UI background. Those people won’t learn the OS-native UIs because that would mean they’d give up on their existing knowledge. Because of that native means “not running in an embedded web browser” to many nowadays.

Comment by fishgoesblub 22 hours ago

I have the same annoyance. It's continually maddening to see "native" plastered everywhere only for it to be some non-native junk. I miss when native meant something like Qt.

Comment by foresto 20 hours ago

Qt is an interesting case, because it doesn't use the native platform's widget code*, but does a good job of looking and behaving as though it does. That's usually close enough for me.

Various other toolkits have tried this approach, but unfortunately, I'm not aware of any others that succeed. Common deficiencies include keyboard navigation and text rendering.

*(Except on Qt-based desktops like KDE Plasma, of course.)

Comment by factotvm 22 hours ago

I've been thinking a lot about the term "native" as I come from mobile. When writing a core in Rust (which I like to do), and then layering on the operating system's UI SDK components per platform (which I also like to do), what is native and what isn't, especially when you throw in React Native to the discussion?

I like your definition quite a bit, but I need another word for, "code that doesn't need a runtime to execute."

I ended up using "experience layer" to describe the SDK components.

Comment by thayne 22 hours ago

Native often means "not a wrapper around a webview".

If you define it as "using the widgets provided by the operating system", then "native" is by definition incompatible with "cross-platform." And what does that mean on Linux, where the operating system doesn't provide widgets? Are gtk and Qt not native?

Comment by foresto 20 hours ago

Adding to this...

When discussing GUI toolkits, "native" should be understood to mean "native to the host's graphical environment".

"Native to the OS" might or might not be equivalent, depending on the OS and what one considers "OS" to mean. (Does it mean a kernel? A desktop distro? Something else?) Because of this ambiguity, it's not a very practical way to approach the discussion. Different people attach different meanings to that phrase.

Some frameworks are native to Qt. Others are native to Gtk. Practically none are native to Linux. ;)

I don't think "cross-platform" is incompatible with "native". It has been achieved more than once using toolkit wrappers, usually selected at build time.

Comment by elcritch 17 hours ago

The dynamic lighting setup is pretty cool. Not sure how practical it is for most applications but cool.

But this syntax – egads man! It literally hurts my brain trying to parse it:

    fn view(s: &State, _: &mut Cx<State>) -> El {
        let t = tok::theme(true);
        let label = text(if s.on { "Lights on" } else { "Lights off" })
        .font(type_::TITLE).color(t.text);
        let knob = el().key("knob").size(18.0, 18.0).radius(9.0).fill(t.knob)
            .absolute(if s.on { 18.0 } else { 2.0 }, 2.0);
        let switch = el().key("switch").role("switch").label("Lights").checked(s.on)
            .focusable(true).size(38.0, 22.0).radius(11.0)
            .fill(if s.on { tok::accent(0, true) } else { t.control_off })
            .motion(motion::SNAPPY)
            .on_press(|s: &mut State| s.on = !s.on)
            .child(knob);
        col().w_full().h_full().center().gap(16.0).fill(t.bg).child(label).child(switch)
    }

Maybe I'm getting too old but I'd prefer good old Perl 5 linenoise.

Comment by bovermyer 23 hours ago

So it's a UI framework by agents, for agents?

Comment by sarabarasa100 22 hours ago

why are we giving more accessibility to agents than to like disabled human users?

Comment by eska 22 hours ago

I wonder whether that results in better accessibility for disabled people in the end because agents can control UIs for them.

Comment by esafak 23 hours 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/

Comment by anentropic 23 hours ago

there are tests, no?

e.g. https://github.com/anomalyco/rune/tree/dev/crates/rune-kit/t...

Comment by QuantumNomad_ 23 hours ago

Indeed. But why not run the tests in CI when merging to master?

Comment by efficax 22 hours ago

Where I work, we've moved CI "left", all tests are run on the developers machine before merging

Comment by esafak 22 hours ago

You're not shifting left unless you guarantee local tests always run, faithfully to production. That rarely happens. Local testing should be supplementary. We use https://hk.jdx.dev/

Comment by efficax 22 hours ago

We do ensure this, requiring signed proof, running in containers that would be identical to github runners (more or less). Now, this could be spoofed by an engineer, but we operate in a high trust environment

Comment by esafak 21 hours ago

This is interesting. Are you using an available product for managing these signatures, or did you write your own?

Comment by efficax 19 hours ago

we built workflows using swamp https://swamp-club.com/

Comment by esafak 23 hours ago

They ain't running in CI.

Comment by varispeed 18 hours ago

> and the web,

And no live examples...

Comment by nbevans 21 hours ago

This is from the same guys that thought building a coding agent harness with "Bun" was a good idea

Comment by cpursley 21 hours ago

Another option is Crux, which lets use actual native UI:

https://redbadger.github.io/crux

Comment by cute_boi 22 hours ago

Another Vibe coded slop which will probably be not maintained after 3-4 weeks.

Comment by rvz 23 hours 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.

[0] https://github.com/anomalyco/rune/blob/dev/crates/rune/READM...

Comment by bhouston 23 hours ago

Wait, zero tests? It is super cheap to write tests these days. It is how you gate agent generated code from destroying production.

Comment by wuliwong 22 hours ago

They have tests, this person is just wrong.

Comment by wuliwong 22 hours ago

What are you talking about? They definitely have tests.

Comment by auscvlt 21 hours ago

Damn, this README is more of a DONTREADME. Even the root README is for agents, not people. The more I see stuff like this, the more I think about becoming a welder or a carpenter...

Comment by eviks 22 hours ago

Why do you say 0 tests? Are the other statements similarly precise?

Comment by the__alchemist 22 hours ago

You're not kidding - that README is not readable.

Comment by Phelinofist 21 hours ago

I don't thinks its intended to be read by humans

Comment by sick_of_slop 22 hours ago

[dead]

Comment by ForHackernews 23 hours ago

...what does this do? Is it just a vibecoded version of https://www.egui.rs/

Comment by roblh 23 hours ago

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.

Comment by skavi 23 hours ago

it doesn’t look immediate mode to me?

Comment by esafak 23 hours ago

It presumably powers OpenCode, the agent harness.

Comment by GrayShade 20 hours ago

It doesn't, that's https://github.com/anomalyco/opentui.

Comment by esafak 19 hours ago

Apparently the plan is to move the desktop from Electron to Rune: https://github.com/anomalyco/rune/blob/dev/PLAN.md

Comment by bhouston 23 hours ago

The website for https://www.egui.rs sort of sucks, it took around 10 seconds to load and initialize for some reason.

Comment by hmry 22 hours ago

It's a fun tech demo, egui isn't meant to make websites. It's primarily for integration into games/other real-time-3D-rendered applications, and secondarily for GUI applications via eframe.

But I agree, I think they would be better served by making a normal website and linking to the demo prominently (For comparison, see iced's website https://iced.rs, which is great IMO)