It's clear that AI assisted coding is dividing developers (welcome to the culture wars!). I've seen a few blog posts now that talk about how some people just "love the craft", "delight in making something just right, like knitting", etc, as opposed to people who just "want to make it work". As if that explains the divide.
How about this, some people resent the notion of being a babysitter to a stochastic token machine, hastening their own cognitive decline. Some people resent paying rent to a handful of US companies, all coming directly out of the TESCREAL human extinction cult, to be able to write software. Some people resent the "worse is better" steady decline of software quality over the past two decades, now supercharged. Some people resent that the hegemonic computing ecosystem is entirely shaped by the logic of venture capital. Some people hate that the digital commons is walled off and sold back to us. Oh and I guess some people also don't like the thought of making coding several orders of magnitude more energy intensive during a climate emergency.
But sure, no, it's really because we mourn the loss of our hobby.
Hey Berliners, did you know that there are two petitions going that really need more signatures. One is to start reducing cars in the city, similar to what Amsterdam, Copenhagen, and Paris have done, and the other is to ban a lot of street advertising. Sadly both of them need to be printed out and sent by mail, and they have to arrive before 8 May.
You can find information and the forms for these at the following addresses:
https://verkehrsentscheid.de
https://berlin-werbefrei.de
Do us all a favour, and print out the forms, sign it yourself, and get everyone around you to sign it as well and send it in, as this city would be much better to live in with less cars and advertising.
And please boost this for reach, as we urgently need a lot more signatures on both.

GTK-NoCSD: an LD_PRELOAD library to disable CSDs
While Libadwaita applications running in a GNOME desktop environment look great and nicely consistent, they look utterly out of place and jarring when run in Xfce, Pantheon, KDE, and others. The biggest reason for this is GNOME's insistence on using client-side decorations, which feel at home inside a GNOME environment, but out of place in envi
https://www.osnews.com/story/144473/gtk-nocsd-an-ld_preload-library-to-disable-csds/
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code credited to Claude will actually have a warning sigil
CF
PSA: Did you know that it’s **unsafe** to put code diffs into your commit messages?
Like https://github.com/i3/i3/pull/6564 for example
Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!
This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.
My FOSDEM presentation ia now possible to watch online! 🎉
https://fosdem.org/2026/schedule/event/JYGFRE-modular-in-the-daw/
A small talk about Cardinal's history/beginnings, differences vs Rack Pro and some tips&tricks.
See you all next year again!
You don't need to pay Apple or start a new subscription to unleash your creativity. We asked creatives what free software they use to get the job done and here are their picks.
A thread 🧵
A small update on the KXStudio repositories this month(ish).
Just a few updates, but added new "hamburger" distortion plugin.
https://kx.studio/News/?action=view&url=kxstudio-project-update-august-october-2025
If you are 🇩🇪 German, you can now call many of your Bundestag members directly via https://fightchatcontrol.eu/ by clicking the "Call" button!
Yay for audio plugins under Wayland.
Non-embedded type for now, but one step at a time we will get there.
Also, today I answered a question I had for a long time...
If an X11 host running under XWayland calls Wayland-native APIs manually, would it be able to load Wayland-UI based plugins?
The answer is yes - Carla running under Qt xcb "platform" can still show Wayland UIs.
The reverse is also true (Qt wayland "platform" with X11 UIs through XWayland)
Future is bright 🌄
Audio production on Linux, using proprietary audio plugins, is somewhat funny/interesting to see in the context of security.
I mean, there are a lot of recent efforts to put applications in containers, sandboxes, lots of talking about X11 being unsafe vs Wayland...
And then users just download and run arbitrary binary code from the internet 😅
Nothing against those that do this, it is just a bit funny to see from a security perspective.
The scumbag conservative-led Berlin government plans to massively reduce spending on public transportation, biking & pedestrians (60-70% down) while also massively increasing spending on streets & cars. 🤬
So this is possible... web-browser based audio processing as part of your signal chain.
PipeWire makes this extremely easy to setup, and Ildaeil on the browser with some pre-compiled plugins makes the magic possible.
So here output from Firefox goes into Chromium to give it some LV2 reverb, then into some native metering plugin, then to the speakers 😆
Feel free to try this at https://ildaeil.kx.studio/
But ***beware of feedback loop when enabling input***
The browser will use default input!
"open the pod bay doors, Hal"
"sure, the doors are now open"
"no, Hal, they aren't. open the doors"
"you are right, that is my mistake. i have now opened the doors"
"Hal, the doors are still not open. open the doors!"
"you are right, the doors are not open. i have now opened the doors"
"Hal! the doors are still not open! i'm dying out here!"
"i am sorry, i did not open the doors when i said i had. that was my mistake. the doors are now open"
"... Hal ... open ... the ..."
Made a whole new plugin in just a few hours today 🎉
https://github.com/Darkglass-Electronics/anagram-midi-control
It would actually be < 1 hour if I didn't have to fix a few things on the framework first.
It's not really useful for users at all in general, this is just a testing tool for the Darkglass Anagram unit.
But I like to do things openly and there are no secrets on this one - all it does is send out MIDI - so why not have it open?