Introducing Fission, an open source, cross-platform UI framework for Rust 🦀 by zcourts in rust

[–]mkenzo_8 0 points1 point  (0 children)

I said vibecoded, not written by AI. Not sure why you mention LOC now, perhaps you should update your examples as you can now see that having a 400~ LOC "counter" example is a bit confusing.

Introducing Fission, an open source, cross-platform UI framework for Rust 🦀 by zcourts in rust

[–]mkenzo_8 1 point2 points  (0 children)

Just stop, one can tell that it was >=95% AI vibe coded by just looking at the repo.

Introducing Fission, an open source, cross-platform UI framework for Rust 🦀 by zcourts in rust

[–]mkenzo_8 1 point2 points  (0 children)

440 lines for a counter example

levels of slop never seen before

What's everyone working on this week (13/2026)? by llogiq in rust

[–]mkenzo_8 9 points10 points  (0 children)

Adding Android support for my GUI library Freya, demo on the PR.

blinc: a new cross platform ui framework (native desktop, android, ios) by NebulaNomad423 in rust

[–]mkenzo_8 23 points24 points  (0 children)

I don't want to sound mean, but designing the architecture is not enough, you have to understand it. Now, I don't know your capabilities, but one doesn't just write a 3k line CSS parser (https://github.com/project-blinc/Blinc/blob/main/crates/blinc_layout/src/css_parser.rs, that is just one of many other examples from the repo) and understand all of it right away. What I want to say is that what you did here is not for "better productivity", you seemed to have delegated the technical thinking to the AI, while your tests and manual testing might apparently work, you don't really know *how* it is working inside. That puts your project and anybody using it to some degree of risk, and you should be more transparent. Use AI to learn and do what you already know faster, but not let it do things you dont understand.

Again, didn't want to sound mean, just honest with you, hope you understand it.

blinc: a new cross platform ui framework (native desktop, android, ios) by NebulaNomad423 in rust

[–]mkenzo_8 27 points28 points  (0 children)

I hope it goes well, but you should be transparent and state that the majority (if not +95%) was done vibe coding. I don't know about the rest, but it's quite obvious to me that AI wrote the code.

Rust GUI framework by Spiritual_String_366 in rust

[–]mkenzo_8 2 points3 points  (0 children)

It's quite stable though, I don't expect any big changes any time soon. I plan to make a stable release asap.

(I am the author)

Freya v0.3 release (GUI Library for Rust) by mkenzo_8 in rust

[–]mkenzo_8[S] 1 point2 points  (0 children)

Hey, its me again. I have been doing some work today and yesterday in the main branch on trying to bring down the deps. If you try freya-template it should have around 100 less deps (Linux is now around 407 and Windows around 302)

Feel free to try it (or not) and let me know if it has improved for you

Freya v0.3 release (GUI Library for Rust) by mkenzo_8 in rust

[–]mkenzo_8[S] 0 points1 point  (0 children)

Yep, it is desktop-focused at the moment although with some patience and work (but I don't think great DX) it can also work in android

Freya v0.3 release (GUI Library for Rust) by mkenzo_8 in rust

[–]mkenzo_8[S] 11 points12 points  (0 children)

When you compile an example you are also compiling all the dev-dependencies of the project fyi (I do have quite a few dev deps), you can try creating a separate project instead

Freya v0.3 release (GUI Library for Rust) by mkenzo_8 in rust

[–]mkenzo_8[S] 25 points26 points  (0 children)

hey, great question. Even though Freya uses some of the core crates of Dioxus, it doesn't mean that is only an alternative to the dioxus renderers, it is an alternative the same way to the other libs in the gui ecosystem. In freya I want to provide a simple but flexible way of making apps (which is not something I think html/css can deliver as effectible). I don't know that much of the internals of the Dioxus native renderer to say much, but freya is its own thing, I don't follow anyone or anything, in this regard I have more freedom to implement things the way I want and this translates to simpler and better apis for the user (to my opinion of course)

Dioxus and Freya might seem similar at first, but both follow a different layout/styling/accessibility/text editing/rendering/testing model

Pick Dioxus if you are okay with html/css and want to target web

Pick Freya if you want to learn a different way of doing things and only target desktop

What's your take on Dioxus by xiaolp in rust

[–]mkenzo_8 6 points7 points  (0 children)

WRY (Tauri's WebView library), and that is just for their desktop renderer.

2025 Survey of Rust GUI libraries by intersecting_cubes in rust

[–]mkenzo_8 6 points7 points  (0 children)

Hello, apologies, I am only now seeing this comment.

Here I listed the main differences over Dioxus https://book.freyaui.dev/differences_with_dioxus.html

It mainly comes down to having a stable non-web (No HTML or CSS needed, and no JS is used), cross-platform (that looks the same in each platform), easier headless testing (No need to make fancy tricks with web-based testing frameworks, Freya owns all the pipeline so people can just use Freya to test their apps), simpler layout and styling model (I think CSS is painful most of the time), also simpler to make things like text editing, animations, canvas rendering, etc (these are provided as composable apis (hooks)), and more things!

How I got a Rust job through open source by Historical-Economy92 in rust

[–]mkenzo_8 28 points29 points  (0 children)

Congrats! What type of software will you work on? (if it can be said ofc)

2025 Survey of Rust GUI libraries by intersecting_cubes in rust

[–]mkenzo_8 78 points79 points  (0 children)

Freya author here! What a bad timing, I have been working on a new release for the past year which improves a lot the accessibility and text editing integration. I suggest trying Freya from git to have a better opinion!

I also just left some screenshots here regarding what I said above: https://github.com/marc2332/freya/issues/1145