nobox

To be honest, I have not yet written Rust seriously, so I cannot comment as much on it. I mostly use C, OCaml, Lua, at times Perl, these days. I do not know how much the language would feel like it is getting in the way of "expressing" my thoughts. https://github.com/serprex/nobox/blob/master/nobox.c is definitely terse. :D I get lost just by looking at it; a little bit of refactoring (indentation-wise) would help though.

They were opining that Ada is unsuitable for fine grained data structures (like Rust being awkward with linked lists) & lacking mature graphics APIs For years I used a C window manager I wrote which was less than 150 lines[1], it can definitely be a terse language. But I've also written pretty tight Rust code for a card game engine & its http server. I don't think Rust is particularly more verbose. Rust code can be artistic too[2] 1. https://github.com/serprex/nobox/blob/master/nobox.c 2. https://github.com/serprex/Kelxquoia/blob/master/src/main.rs

Nice to see someone else fall upon what I call funnel-based control flow, as opposed to stack-based control flow of most programs using functions. I used the same pattern in nobox: https://github.com/serprex/nobox/blob/master/nobox.c Idea is that using goto your program can be mostly a loop where you make forward jumps to anywhere in the code & everything converges or jumps back to the start. It ends up making for very terse code since you're no longer passing values back & forth as much through structs/params/returns. You align variables & jump to code. Each label has a kind of ABI where the variables are the registers

https://github.com/serprex/nobox would make for a good baseline, it uses about 12K resident memory It was my desktop environment for years until I switched to wayland & sway. My desktop had 512MB ram until I got a new desktop in 2019

I also used a more minimalist self made WM based on reading dwm's source: https://github.com/serprex/nobox The "I don't want to spend time configuring my desktop environment" argument misses the point with these things. Everyone had to learn how to use various interfaces. It's easiest for me to learn something whose code I can mess around with

I prefer https://github.com/serprex/nobox (which isn't on wiki's list) Only using 3 pages of RAM is pretty good

This was a reference for me while initially developing nobox: https://github.com/serprex/nobox/blob/master/nobox.c

Here, have a window manager I wrote, maybe it'll make your skin crawl right off: https://github.com/serprex/nobox/blob/master/nobox.c

"Suckless inspired my naming of sxi: https://github.com/serprex/sxi & dwm served as the base from which I learnt to create nobox: https://github.com/serprex/nobox" Any screenshots of nobox that I could see ?

Suckless inspired my naming of sxi: https://github.com/serprex/sxi & dwm served as the base from which I learnt to create nobox: https://github.com/serprex/nobox Good stuff. Though seeing dwm have a null-check-before-free made me squirm. Have been using st for awhile now, it's nice, bit of a hassle to get backspace working & I sometimes miss being able to scroll back over console output The only-one-file philosophy seemed to be a bit of a hassle where st had to turn down a wayland patch. One would think that it could be split into st-common.c, st-x11.c, & st-wl.c where the rendering backend is abstracted stalin is neat but I personally feel using git to distribute binaries suboptimal. I'd prefer if there was a /build directory where one could git clone submodules & run a /build/install.sh to update the system. But that'd be something else