DEV Community: Zaman Hüseyinli

auto cpufreq rust is rewrittening.

Zaman Hüseyinli — Sat, 14 Feb 2026 00:46:00 +0000

There is a software developed for Linux auto-cpufreq. This software is technically for controlling the CPU frequency and managing energy efficiency, but since the Python version has some performance problems and consumes too much memory compared to low-level software, I adapted the Python version to Rust fully equipped. By adapting it, I directly added all the features in the same way, so now you can manage the CPU frequency in general and provide real energy efficiency with the autocpufreq software, which is compatible with Rust. To put it directly, the Python version had a lot of performance problems and excessive memory usage + it did not have the appropriate alignment and technical management for low-level software. Therefore, in the Rust version, you can use the GTK interface and CLI interface with full performance. The GTK interface is a little different, but technically it has similar features.For those interested, the source code of the project:auto-cpufreq-rust
By the way, those who want can install it via AUR. For now, installation support is only offered via AUR. Support will be offered for the Snap version soon.

AUR setuping
yay -S auto-cpufreq-rust-git

WASMA independent WM compositor UI frontend system

Zaman Hüseyinli — Sat, 17 Jan 2026 23:19:23 +0000

Wasma indepent-full WM,compositor,UI-fronted

Zaman Hüseyinli ・ Jan 17

#rust #wm #ui #frontend

Wasma independent-full WM,compositor,UI-fronted

Zaman Hüseyinli — Sat, 17 Jan 2026 21:27:46 +0000

WASMA

WASMA, or Windows Assignment System Monitoring Architecture, is a WM Compositor UI-fronted layer system currently based on ICED. It is completely independent, written in Rust, and offers its own environment. It is currently under development, but its features are as follows:

It supports manually managing resource usage in windows.
You can share windows over any network; no additional software like a remote viewer is needed. You can start windows via GRPC, HTTP, HTTPS, or Tor. You can use the multi-instances option to start them all at once; if you want to start them individually, you need to use singularity instances. You can open, start, and manage multiple windows over a single protocol.
Optional application permission management support; you can directly define and restrict the permissions of any application, but this is optional. Instead of .desktop, it supports the more modern and innovative .manifest format, allowing you to define and manage the window management features I mentioned through the manifest and application. However, using the source* method for permissions is recommended.
And finally, with wasma-ubin, you can now directly add GTK/QT/ICED platformer features from Windows/macos/Linux via the binary, adding missing GTK/QT/ICED features.
Wasma-ubin offers a unified binary interface and directly adds, modifies, and enforces all features via the binary through a single ABI, thus providing support for translating features from other platforms to other platforms.
Full translation integration support is offered for x11 Wayland applications.
Legacy platform or Windows-only support is offered separately, but for full support, it is recommended to use the WGClient WASMA ground client.
It has a CPU-powered rendering system; GPU is optional. You can directly adjust resource management. For more information, visit Wasma