Post by @fd0
RE: https://circumstances.run/@davidgerard/117441841785502664
I'd like to tell you a story about a contributor who came to us at Mozilla, in my first 2-3 years working there. I never met them, don't know their name, and I still think about them a few times a year.
They came to us with questions, as they were struggling to build Firefox on their computer, and they were getting errors that nobody had ever seen. And I don't mean "errors that were unfamiliar to our engineers", I mean "we can't figure out how or why our build system would emit that string."
So, after going back and forth a bit with person, who it turns out is in their early teens, we asking about their hardware, what setup they've got that's doing this. Maybe this person's got some new system we've never seen, maybe they're running in some novel context we need to know about. Is this an edge case, or is this a leading-edge case? Outliers are always interesting.
I've seen some Pretty Far Out There systems, I run a few myself, and this kid's system is Out There.
So, they're running one of those weird dual-slot Pentium III boards with two physical CPUs. Running Linux - somehow - on a hard drive that's almost full, a userspace partition on NTFS and more, and the more I hear about this system the more confused I get.
For the non nerds following this thread, this is like finding out somebody's daily driver is built out of the parts of a sports car, a semi and a train, and it's running on vegetable oil. You might ask why, but the first question is ... how?
This kid is getting error message that nobody has ever seen because they've got a machine nobody else has, set up like nobody else does that nobody would ever choose. And you might ask how, but the first question is why?
And the answer is: this kid has nothing. And they've _built their own computer_ out parts they've scavenged from the computers other people have put to the curb, got a Linux ISO and somehow made it work.
There _are no_ computers like this. And... they want to help us?
And I'm sitting there, reading this on the screen of a five thousand dollar Macbook Pro in an office where the snacks are free, feeling humbled and deeply ashamed.
There's nothing I can do for this person. But the enormity of it. They've cobbled up a machine out of nothing but trash and their own tenacity, and they want to help us build Firefox? There's lots of ways to do that, but building it, compiling it, that can't happen. Not on this machine.
There's always been a financial barrier to participation in open source. Always. And we have to make it as low as we possibly can.
But a _wealth_ minimum bar, to contributing?
That's vile. It's disgusting.
@mhoye as a point somewhat orthogonal to the one you're making: one of the conclusions I'd draw from this is we have a moral obligation to make build systems simple. our build systems are very complicated and often it's not because they need to be but because of converging historical concidences.
no one wants to hear this, but whatever other downsides it has, Rust's "Cargo" system is very simple. it works without odd problems in a wide variety of circumstances because it's simple. that's good
This is true in pretty much EVERYTHING.
The more parts a thing has, the more things there are to break.
True for programs, true for cars and appliances-- and legal systems! Holy shit those are so complicated you basically have to be a dedicated priest whose brain is geared to memorize vast amounts of arbitrary illogical minutiae in order to make much sense of it-- obfuscating what's right, concentrating power in elitist hands, and opening masses of nooks and crannies for corruption to fester.
My father is an engineer, the type that builds physical buildings. I was brought up thinking "efficiency" was all about getting as much done as possible, as effectively as possible, with the minimum amount of materials needed-- and all with safety in mind, accounting for extreme situations like earthquakes. A good design is a CLEAN design. The simpler, the better. Elegance in finding ways to stack uses, satisfaction in optimizing for stability and longevity, pride in minimizing waste.
The depraved crap passing for technology now-- especially built-in obsolescence-- seriously pains him. Every engineering instinct in his body and soul rebels at the inefficiency and recklessness of it all. That weary, wincing facepalm he does when he sees why this mistake here (the homeowner carving an arch in that particular LOAD-BEARING wall for example) is going to cause a nasty, expensive, and totally preventable disaster.
>The more parts a thing has, the more things there are to break.
as much as the technophile parts of me would like smart-devices all over the house connected to my home servers and automating my life, your tenet there is the main reason why every device in our house (and each car) is about as dumb-simple as we can get it. My fridge doesn't talk to the internet or have cameras or a display (we even took out the ice-maker). The can-opener is a manual-crank. The TV takes line-in video (component or HDMI) provided by trusted offline devices, except when explicitly hooking up a laptop to stream something.
I like simple.
@gumnos@mastodon.bsd.cafe In general: complexity is the enemy of correctness
@gumnos@mastodon.bsd.cafe @violetmadder@kolektiva.social @mcc@mastodon.social @mhoye@cosocial.ca