0xJenkz

Architecture Builder : : being of radical notions

[0xJenkz @0xJenkz]

@D_Espanadero snob

[0xJenkz @0xJenkz]

@FarZenith @scottstts @thsottiaux If I showed you my swarm, you'd shit yourself. It’s the most traceable system ever engineered. If a worker dares to make an edit without a tool, it gets wiped instantly and replaced without blinking. I couldn’t care less about token efficiency, I want full traceability

[0xJenkz @0xJenkz]

@hilbertspaess Dude, all you have to do is quit your job and that's it, you don't need to write your shitty post. Now you've got all the mainstream media parroting the crap you say. You fucking nerdy idiot.

[cafkafk @cafkafk]

Let me do one serious post chat, and I'll resume shitposting. This is important to make explicitly clear.

Two weeks ago, fellow Dane, David Heinemeier Hansson (@dhh) went on a public tirade about Nix and the Linux ecosystem.
​
"Goddamn maniacs." "Clowns." "Goblins." "Cancer."
​
In the same conversation, he called Nix “amazing technology.”
​
Two days ago, it became clear that he is planning to build his "distribution" on NixOS.
​
That is worth dwelling on.
​
NixOS can be criticized. Of course it can. We criticize ourselves constantly.
​
What I find deeply gross is arriving as a tourist to an ecosystem, using an enormous platform to ridicule the people who built it, then deciding their work is good enough to become the foundation of your own project.
​
Much of his indictment is not even about NixOS. Land acknowledgements? That is not some defining debate here. It is Twitter culture-war material imported into a caricature of a community he barely knows.
​
For someone so insistent that technology should be "apolitical", David spends a lot of time talking about politics, culture, codes of conduct, and community governance.
​
He rails against codes of conduct, then writes rules for how people in his own community should behave while insisting that somehow does not count.
​
Call it whatever you want. Communities require governance.
​
And governance, packaging, security, infrastructure, release engineering, review and maintenance are not distractions from building a distribution.
​
They are the work.
​
So far, what he has is a configuration and installer layer on top of years of work by Arch, Linux, Rust, and soon NixOS and Nixpkgs contributors.
​
Using Claude to produce that glue does not make the work underneath disappear.
​
Packages, infrastructure, security and technical knowledge exist because people did the difficult, boring work required to make this ecosystem function.
​
You are not replacing those people. You are depending on them.
​
Which makes the rhetoric about creating a home for the "competent" people obnoxious.
​
David, the competent people are already here.
​
They are the people your project depends on — including people and communities you have been calling clowns.
​
You do not get to praise the "amazing technology", dismiss the people who sustain it as politically deranged, put a layer on top, and cast yourself as the serious technical adult in the room.
​
That is not escaping dysfunction. It is standing on other people's work while sneering downward.
​
People mock NixOS. They declare it insane. They explain why nobody should want it.
��
And then they use it anyway. So who's competent here?
​
You can hate us. You can mock us. You can call us clowns.
​
But when the answer to your own technical problems is to build on our work, that tells its own story.
​
So, David: welcome to NixOS.
​
But understand what you are standing on.
​
If you intend to build on years of work from this community, the attitude adjustment is overdue: less culture-war posturing, more respect and humility toward the people doing the work you now depend on.

[0xJenkz @0xJenkz]

@dhh I guess just a glorified Dark Reader

[Noam Brown @polynoamial]

The original Lee Sedol moment

[0xJenkz @0xJenkz]

@_SsAsS_

[0xJenkz @0xJenkz]

@leonpalafox Genera token por token, no palabra por palabra.

[0xJenkz @0xJenkz]

@markchen90 So you guys are thieves, great, OpenAI steals its users' work in a derivative way. fucking thieves

[0xJenkz @0xJenkz]

@OpenAI No, you're just a bunch of thieves

[0xJenkz @0xJenkz]

@ElBadiablo ah, el turismo linux mas fuerte que nunca, tipicas vacaciones de instalacion, sigue la customizacion del entorno, luego el aburrimiento, luego volver a un OS más estable. Todo esto alimenta la falsa sensacion de productividad. Un clásico.

[0xJenkz @0xJenkz]

@theo @Neolectron

[0xJenkz @0xJenkz]

@MasterAlpaca @dani_absalon ni siquiera a los que les "robaron" el codigo se quejan tanto, ellos mismos estan usando la IA, estas peleando contra mounstros imaginarios jajaja

[0xJenkz @0xJenkz]

@theo Google isn't interested in you as a customer, just accept it

[0xJenkz @0xJenkz]

@SuspendedTommy It is feasible, but of course you get less water than the amount of liquid you put in, so it can't be a closed-loop system, each time you'd have less clean water, forcing you to add liquid from an external source.

[0xJenkz @0xJenkz]

@javsolgar Nunca debes de perder el contexto total del proyecto, no debes de ir más rapido que ese cuello de botella actual, en todo caso empezar a compartir con otro humano responsabilidades del contexto, pero jamas avanzar a ciegas, es el peor error que podras cometer con la IA actual

[0xJenkz @0xJenkz]

@CJSlattery problem is that they aren't actual PM's, it's such a lax role that it ends up being filled by underqualified individuals. these people don't know what real work entails. If I wanted a secretary or a cheerleader, I would hire one directly

[0xJenkz @0xJenkz]

@nestorgodd @SakshiSugandhi Only a snob would say that

[0xJenkz @0xJenkz]

@SakshiSugandhi you need an explorer and a visualizer; you can't be flying blind relying 100% on vibe coding, and it makes no sense to use third-party apps for exploration and visualization when OMP or any agent can build it on its own

[0xJenkz @0xJenkz]

@SebastienGllmt The problem isn’t the command itself, is that all that micromanagement turns the concept of deletion into something cheap and routine, which expands the failure surface. My agents almost never run destructive commands because they only ever handle the actual task, nothing more.