rootnod3

I got good and bad news: my own WM did it Xmonad style, but I have not updated it in years. If there is enough request I might revive it (also X11 though, so not fitting the bill).

See https://github.com/Kintaro/wtftw It handles screens the exact same way Xmonad does, because it was modeled after Xmonad. The config is entirely done in Rust, so it allows for a lot of hackability. On reload, the config gets compiled to a dynamic library and the WM restarts itself, passing the current window IDs to itself to "reload".

But I was meaning to pick up a new project in 2026 for myself. So maybe a CL based Wayland WM with an Xmonad style?

Trust me, the majority of tiling WMs has on workspace for ALL monitors combined. The percentage of WMs treating every monitor as a separate unit is smaller.

And sure, you can send message and commands to Niri via IPC, but that is very very different from say XMonad or StumpWM where you can actually override or alter functionality within the config instead of having to change the original source code.

That I'd say is the very definition of hackable. When you can actually just throw stuff into your config to change core behavior.

I honestly do not understand the scrolling WMs. The last thing I want to do is move my hand to my mouse to scroll. I tried them, didn't work for me. So yes, there's still a crowd of people hanging on to old tiling WMs and therefore sticking to Xorg instead of Wayland. Because you can pry EXWM and StumpWM out of my cold dead hands.

Apart from the Haskell fun, xmonad is really really good. Especially how it handles workspaces on multiple monitors. By default, each monitor has one workspace. Not one workspace for ALL monitors.

So if your side screen has say documentation open, and you switch on your main screen from terminal to editor, only the main screen changes. The side screen stays untouched. Some people prefer it, some hate it. But it's good that xmonad offers it. It also has hot reloading of the config, which is also nice.

Sure, Niri's config is approachable, but is it hackable? It only offers what Niri offers, right? You can't extend its functionality by config alone.

That is where XMonad and others shine. Sure, they might not be for the "I don't wanna spend time configuring my WM to death" crowd (and I mean absolutely no derision in that. We all have different rabbit holes we want to customize to oblivion), but Xmonad or Stumpwm etc allow for those shenanigans, and I myself am very very happy to have those.

Long story short, it's not all 100% about the type safety, it's also a lot about the extensibility of it.

Niri is nice, not mocking it. But infinite scrolling is not everyone's jam. Some others might even question the choice of KDL instead of JSON without any clear benifit.

Whatever you prefer and if it works for you, great. That's why we have choices ^^

One can of course add the same stuff to other languages in form of libraries and stuff, but lisp/scheme make it incredibly easy to make it look like part of the language itself and make seem a mere extension of the language. So you can have both worlds if you want to. Lisp/scheme is not dead.

In fact, in recent years people have started contributing again and are rediscovering the merits.

That is where Lisp or Scheme weirdly shines. It is incredibly easy to add prolog to a Lisp or a Scheme. It’s almost as if it comes out naturally if you just go down the rabbit hole.

“The little prover” is a fantastic book for that. The whole series is.

So far it works pretty good. Minor edits I just quickly edit and tangle, otherwise I open the source block in a buffer (C-c '), and from there I can just use the usual C-c C-c shortcut to send it to the REPL.

But as the first stage bootstrap in CL is mostly done at this point, I have to hot-reload anyway.

At some point it might be nice to have my own REPL running in Emacs, but that is a worry for way later when I actually get something usable. For now this is purely for personal entertainment.

I am working on my own Lisp-like language (cliche, I know). Goal is a hybrid. Syntax is a bit more Clojure inspired, but want to emulate the interactivity of SBCL once I am done.

And the other goal is minimal dependencies. The only bootstrapping stage is a very very small core in Common Lisp + FSet but could also be replaced with other languages, and then using that subset to bootstrap the rest.

There is absolutely zero claim to be highly performant, it is more of an educational experience.

All of it is done via literate programming in org-mode. So far it's working pretty well, but will have to see how that approach works if the project grows.

Yeah, but doesn't that also apply to GCC or LLVM? Download the target-system version and go compiling away. That is not unique to ZIG.

I absolutely love the idea and methods behind OCaml, but the syntax..... I also love Haskell and already feel that its syntax is not easy to grok on larger projects, but OCaml basically went "hold my beer" and went to town on that.

"Make data accessible and preserve it" -> FBI "Use copyrighted data for LLM training and sell the product" -> Billions from NVIDIA

I guess so. In a way it makes sense if you can share your code base between the iOS/MacOS app and your backend. It makes development easier. But I guess that the majority of apps is not running MacOS servers for the backend. So far it's probably some node backends and all going JSON inbetween. But for some dedicated apps without a web portal inbetween it might be easier if app and backend are both in Swift.

Why would llvm favor linux? FreeBSD also officially moved from GCC to LLVM for the base system, so I don't see why LLVM wouldn't support it.

Are they also gonna take the reigns and officially be the maintainer of the FreeBSD package in ports or are they gonna wait for some volunteer to package it for them and choke on the bug reports whenever someone finds an issue?

EXWM + Qutebrowser can work like that. The individual tabs of Qutebrowser become Emacs buffers.

And where then is your backup? In the same cloud? The one that just tried to rip your data sovereignity away from you?

The average person still uses the same password for EVERYTHING, despite say iOS and Android making it easy as pie to just go "generate passwords for me". Telling an average person to have a 3-2-1 backup AND run stuff in the cloud that they will 100% lose the password for is not a battle I see to be won in the near future.

I am just missing a similar dongle to hook up my ZMK split keyboards to my OpenBSD systems.

So many use cases. It serves as my mail server because it is secure and simple. It serves as my gateway via wireguard to my homelab. It serves as a daily driver on my x220. It is a simple and straightforward operating system. It can 100% serve you as a daily driver even on desktop (excluding maybe running Steam).

But the simplicity also yields stability. Upgrading Arch for example can sometimes backfire. Upgrading OpenBSD? Almost blindly. It just works (tm).

Maybe a very unpopular opinion, but if you have money to spend on that fad, you are a new level of douche. Take that money and sponsor some open source projects or gift it to charities. If you can’t be arsed to put a plate into a dishwasher you got a level of problem that is so removed from actual problems that it’s weird.

That is even disregarding the privacy implications of a robot that walks around the house with a fucking camera attached to its noggins. If anyone thinks that the camera is only there for the job and kit collecting data is fooling themselves. Because I will bet my ass that that’s how the company actually makes money from investors.

Buy two and make them wash each other :D

It's the Innolux IGZO Low-Power FHD Panel. There are similar ones or same on AliEpxress for example. Compared to the default FHD screen of the T480, The low power screen cuts the power consumption of the display by about 40%. While also having better contrast and brightness. Biggest power-saving upgrade for the T480.

T480 can hold 2 batteries. A swappable and an internal one. At least under FreeBSD the swappable alone gives about 10-11 hours on low brightness. The internal one carries the rest of the way.

I did replace the screen with a low power screen, which easily had the biggest impact on battery life.

I haven't tested the T480 under OpenBSD in a while, but my guess is that if I ran it with "apm -L", it would get close to the same numbers.

Donated. I think what NetBSD is missing, but also hard to pull off, is something like https://openbsd.amsterdam. A service that people can use where parts of the fees go towards the foundation.

Months at the minimum probably.

Manufacturing probably way outshines the usage. And, the side-benefit of using old machines with say NetBSD or OpenBSD etc is that it makes people realize that they don't NEED new modern shiny hardware. I am still daily-driving a x220 on the road (it gets 99% of my stuff done) and at home I am using mostly a slightly upgraded T480. So a 15 year old and a 8 year old laptop. And power consumption wise, my T480 lasts about 17 hours on a charge. That is about same time I'd get out of a modern M3 MacBook Air.

With a bit less performance? Sure. But for my use-case it works. And more people realizing that might actually be a good thing.

I guess. That's why I added the "unless I am mis-interpreting", still got downvoted for it because I guess it was against AI. The wording was confusing but so was my understanding of it as a non-native speaker. Shit happens.

Ah ok, then I did misunderstand a lot. That makes sense. And I do like the non AI based NLP work.

So, unless this went r/woosh over my head....how is current AI better than shit post-transformers? If all....old shit post-transformers are at least deterministic or open and not a randomized shitbox.

Unless I misinterpreted the post, render me confused.

I am still waiting for OpenBSD to add support. They do use Asahi to get the install going. But unless I am mistaken, only up to M2 is supported now.

I'd rather have a simple coarse-grained mechanism than whatever feverdream that seccomp, selinux and apparmor are. A convoluted mess incorporating almost Turing complete languages that are just asking to shoot yourself in the foot a mile deep.

The simplicity of pledge is good enough for 99% of use-cases I'd wager AND easy to add to existing code.