Hacker News new | ask | show | jobs
by yoanizer 4195 days ago
It really leaves me shrugging my shoulders when I see titles like "such and such written in such and such language/framework". Like saying that writing a window manager in Rust (or whatever) is interesting just because it is in Rust.

Tell me, what does it bring to the table compared to other window managers ?

2 comments

Writing a window manager in Rust is interesting precisely because it's written in Rust.

I wouldn't be surprised if this homebrewed WM didn't hold up in features or performance to alternatives like xmonad, dwm, Awesome, i3, etc.

However, the linked repo is an interesting way to showcase both a relatively new technology (Rust) and the innards of WMs, which most people don't look at very often. It gives non-Rust-users a glimpse into Rust's features and capabilities, and a glimpse at how simple (150 loc + 125 lines of config) a window manager can be.

I found it insightful.

> Tell me, what does it bring to the table compared to other window managers ?

This kind of window managers are often coupled to a programming language and the end user is expected to modify the source to their liking. For example, dwm is written in C, Xmonad in Haskell, awesome in Lua and there's even ones written in Scheme and Common Lisp. In all of these, the idea is that the source code is the configuration, and you're expected to hack on it.

Of course there's some appeal in just doing it in another programming language, even if it has been done before. A tiling window manager is a few thousand lines of code, so it's a neatly sized practice project.