@particleflux

54 Followers
262 Following
1.7K Posts

I code stuff.

Software / DevOps Engineer at day (#bash #golang #PHP #terraform #AWS)
Hacker at night (#██████)

Automate all the things!
Hack all the things!

Reject the LLM Hype!

Usually tooting in english, rarely in german

btw I use #gentoo

webhttps://particleflux.codes
githubhttps://github.com/particleflux
trycurl http.machine.codes/418
orcurl machine.codes/ansi/mini

John Gruber on one more #enshittification of the web - dickovers.

https://daringfireball.net/2026/05/what_is_a_dickover

What Is a Dickover?

dickover — a modal panel, popover, or curtain presented by a website or app, deliberately obscuring its own content to frustrate the user with an unwanted, unnecessary, mandatory interaction; e.g. asking the user to accept “cookies”, subscribe to a newsletter, install the website’s mobile app, agree to terms of service, or anything else that the user couldn’t give two shits about.

Daring Fireball

It's time to stop this madness https://gitlab.gnome.org/GNOME/libxml2#strict-no-llm--no-ai-policy

After reading this great essay about the harm that LLMs are doing to open source communities I've decided to go full strict about LLM https://linguacelta.com/blog/2026/05/LLMs.html

https://toot.wales/@linguacelta/116600964539347661

GNOME / libxml2 · GitLab

XML parser and toolkit

GitLab

"I really want a complete redesign of this app I'm using"

-- no user ever

#UI #UX

never fucking forgive them for what they've done to the computer

*gently grabs the cheeks of all programmers to stare deeply into their eyes*

All I want is a dry tech manual. A boring, well indexed manual that defines every function. Not a chatbot. Not a training. Not a million "articles" that I have to search through. Not a "community forum".

My rice cooker came with one. I want one for every piece of software I have to interact with.

Go get yourself a technical writer if necessary.

I. Want. An. Instructional. Manual.

Pasting a huge AI generated explanation to a problem in an issue or pull-request is nothing but RUDE. Don't do it. You look stupid and the receivers of that feel insulted.

We are humans. We communicate like humans. Fine, use the tools you like, but don't insult us.

OH: "If you make a garbage collector that doesn't work, is it a garbage collector?"
🤚 Getting a 2160p screen to watch 2160p movies.
👉️ Getting a 2160p screen to watch 1080p movies in split-screen with working.

New on #blog (this time with quotes from Fedi): "Why Gentoo?"

https://blogs.gentoo.org/mgorny/2026/05/28/why-gentoo/

"""
Multiple times in the past I’ve been thinking of how #Gentoo is perceived by the wider public, the non-users. What probably stands out most is compiling. Almost everyone who heard of Gentoo knows it has something to do with compiling everything. And why are we doing that? Well, besides being hardcore, the common sentiment goes for performance. So yeah, Gentoo users must be some kind of hardcore ricers who try to squeeze every last bit of their system performance.

To be honest, I don’t think that’s a good way to describe Gentoo. Yes, compiling is at the core of it. But performance? I don’t think so, at least not in the obvious, -O9999 -fzomg-fast way. The world has moved on, CPUs have gotten faster, optimizations have gotten smarter, and distributions have started optimizing more aggressively. Optimization-wise, I suspect your average Ubuntu package with generic optimizations may be no slower than the equivalent Gentoo package fine-tuned for your CPU. And if it’s not, then it probably won’t make a real difference anyway.

There’s much more to Gentoo than that. Yes, some of it comes from building from source: the flexibility. But a lot of it comes from the wider Gentoo philosophy, the philosophy that brought us all together. The idea that Gentoo is the distribution we’re making for ourselves and people who enjoy Gentoo. So if I were to make a few arguments for Gentoo, I’d focus on that. And this is what I’d like to do here.
"""

Why Gentoo?

Multiple times in the past I’ve been thinking of how Gentoo is perceived by the wider public, the non-users. What probably stands out most is compiling. Almost everyone who heard of Gentoo kn…

Michał Górny

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.