tiny-std
pgwm
| tiny-std | pgwm | |
|---|---|---|
| 3 | 5 | |
| 41 | 67 | |
| - | - | |
| 7.6 | 4.9 | |
| 5 days ago | 5 days ago | |
| Rust | Rust | |
| Mozilla Public License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tiny-std
-
Static-pie linking a no-libc `no_std` Rust binary
I was doing some cleanup in tiny-std and implemented a feature that I'd wanted for some time, static-pie-linking.
-
I reinvented another wheel, linux threads.
I just got threads to work with my tiny no-libc no-std std-library for x86_64 and aarch64 linux tiny-std.
-
Pgwm 0.3 a pure rust `no_std` no libc window manager.
If you want to check out the WM, that can be found here. If you want to check out tiny-std, that's here. As previously mentioned, there's a write-up on all of that here.
pgwm
-
I reinvented another wheel, linux threads.
Ps. I don't at all endorse using tiny-std, I think it's correct but I wouldn't be surprised if some nasty bugs are hiding somewhere in there. Although I do use it for my WM pgwm which can now be build on stable, assuming you're running Linux with io-uring, a wrote a bit about that change here but didn't post about it then. The main benefit of tiny-std being tiny binaries that link statically.
-
Pgwm 0.3 a pure rust `no_std` no libc window manager.
If you want to check out the WM, that can be found here. If you want to check out tiny-std, that's here. As previously mentioned, there's a write-up on all of that here.
-
I wrote an x11 tiling window manager inspired by DWM that I've been using for a few months now. If you're using x11 and want to try out a new tiling window manager I'd love your feedback!
So if firefox is an application you can find you can query the WM_CLASS property, like this. Other applications might not set that and you'd have to use some other property or information to deduce that this given window(which is just a u32) is actually applicationA. A tip is to start the application, use xprop and see what properties it sets. call_wrapper.rs contains a lot of code about querying different properties. The x11rb example simple_window.rs has a few examples of the other side of that showing how an application can set its on properties.
What are some alternatives?
steed-1 - [INACTIVE] Rust's standard library, free of C dependencies, for Linux systems
x11rb - X11 bindings for the rust programming language, similar to xcb being the X11 C bindings
penrose - A library for writing an X11 tiling window manager
rustix - Safe Rust bindings to POSIX-ish APIs
i3status-rust - Very resourcefriendly and feature-rich replacement for i3status, written in pure Rust
presser - A crate to help you copy things into raw buffers without invoking spooky action at a distance (undefined behavior).
shadow - Shadow is a discrete-event network simulator that directly executes real application code, enabling you to simulate distributed systems with thousands of network-connected processes in realistic and scalable private network experiments using your laptop, desktop, or server running Linux.