Rust source code for WinRAR keygen
 

The attached is the keygen source code for WinRAR, written in Rust.

It's converted from the following C++ repo with vibe coding, just for fun.
Dialog GUI is added, DPI-aware.
License file is saved to the default path "%AppData%\WinRAR\rarreg.key", no admin required(While Admin is required for "C:\Program Files\WinRAR\rarreg.key"),
https://github.com/bitcookies/winrar-keygen/

@WhoCares, I have added egui to your project. Now anyone can compile it for any platform.

What a world:
I have added egui with AI but I have manually fix alignment of widgets.

@WhoCares maybe you should add this to a repo?

hello,

In order to keep the exe file small(no more than 500KB), my package uses "native-windows-gui" crate which supports Windows only, but with Windows built-in editing hotkeys and context menus.
I have another keygen template which produces a 10MB exe with Rust GPUI framework.
Your keygen produces a 4.x MB exe and looks beautiful.

And I put it in my private repo :D

Thanks for your work!

I am fully aware of that ph*t **s binaries. With vibe coding, we can make separate native guis. But who has that time. :D

I prefer GTK on Linux, but I want to give a try on egui. Even though code looks simpler, end result is huge.

At least they are working!

If we want a small binary size and only need a UI with basic controls, libui-rs is also a viable option for cross-platform. It binds to the UI frameworks provided by the operating system, so the resulting size is relatively small.

wxWidgets is another cross-platform option, it also binds to native UI framework, but the compilation process is somewhat more complicated.

I have taken my notes on libui-rs

Put together a libui-rs variant in under an hour with an AI agent.:D

Tested on Windows, macOS, and Ubuntu.

Note: there’s a small macOS-only UI glitch — the "Generate" button doesn’t stretch vertically.

cargo build --release
 

Don't forget to create a release build.
By default a debug build is created.

Release build is approx. 3-4 times smaller than debug one.

Thanks Jupiter for the reminder.

The sizes are for release builds. They are relatively large because the rendering engine is bundled into the binaries.

With native UI frameworks, the rendering engine is provided by the OS (system DLLs / drivers), so the app only contains a thin abstraction layer over the native APIs.