@tomcoates@gruber it’s really not. bsky never had broad appeal like twitter did back in the day. only the terminally online use it, and only a subset of the terminally online. who is on it is distinctly different.
also nobody at bsky was ever employed by twitter- twitter/dorsey seeded the company.
@tomcoates the point i’m trying to make in my first reply is that while theres some value in the bones now that king epic memes has taken his foor off the nazi gas a bit, dont get comfy as he’ll turn it back up when he wants. we’re aggressively and loudly agreeing here.
@tomcoates lol calm down buddy, you’re posting on the same site. i’m not on team gruber, but there are some conversations in tech and policy that dont happen elsewhere on the bones of the old network. a place among many, and not my main one. also morbid curiosity watching what gets pushed.
@the_transit_guy such a visceral change, especially notable at the 23rd st station that has a PATH side and a MTA side. cross the threshold to the PATH side, instant change.
Tonight was awesome. Filmed this before the crowds arrived to the opening at NCM Hawthorn. Seeing the CM-2 transformed from wreckage to operational was incredible given the short timeframe!
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.
@ibuildthecloud@lucperkins@nickstinemates i think it is also really hard to pick the “best” default here (use the conventional linker location if available vs. use the nix one unless told otherwise) as i can see “use default if available” causing the non-nix part of the system to leak in in surprising ways
@ibuildthecloud@lucperkins@nickstinemates got it- trick here is that if this were the default behavior, “go build” would create binaries that _do not work on nixos_, as nixos has no fixed path for the linker. i get the annoyance! just kind of an ELF problem, and one that isn’t unique to nix.
@ibuildthecloud not saying holding it wrong, but saying you are going to be fighting the system’s central conceit uphill, like doing pointer tricks in rust.