The LLM part is bad news but it isn't the sign.
-
@mhoye Something something cathedral, something something bazaar. Who's the priests now, Linus?
-
@hllizi @mhoye I don't think it was pushing a specifically *nazi* agenda there, but he had very strongly held ideas about human motivation, how human beings organize their activities, and what sorts of organizing should be encouraged or discouraged.
Remember this all came around the same time of his mission to replace Free Software with Open Source and make the whole thing appealing to capitalists for the purpose of appropriating free (lowercase-f) labor.
-
@mhoye Linus and his posse have been elitist unwelcoming jerknobs for decades though. If an alternative were to appear, I agree that people would leave them to wither and die. But so far no reasonable alternative has appeared. *BSD, Plan9, etc have all failed to gain traction.
Linux is a local optimum and the path to a different one leads through the valley of pain. Hardly anybody goes through the valley of pain unless much bigger pain awaits them where they are. And those that do mostly die there unless others join. I think that's the principle that explains most misery on this godforsaken planet.
-
@hllizi @mhoye I don't think it was pushing a specifically *nazi* agenda there, but he had very strongly held ideas about human motivation, how human beings organize their activities, and what sorts of organizing should be encouraged or discouraged.
Remember this all came around the same time of his mission to replace Free Software with Open Source and make the whole thing appealing to capitalists for the purpose of appropriating free (lowercase-f) labor.
-
-
Anyway: The worst thing an organization's leaders tolerate is what that organization becomes, and the blast radius of a single toxic contributor is huge and largely invisible. For everyone who speaks up to say this behavior isn't acceptable, there are dozens or hundreds of smart, competent people who peer into your community, see that this is how you live and move along without your ever knowing they exist, on their way to a better life somewhere else.
We don't have to live like this.
@mhoye this is also why ignore doesn't work in any community. New people assume the behavior they see is acceptable. You must actively remove people who exhibit unacceptable behavior.
-
@jpaskaruk @mhoye Have you looked at Zig? The tag line is basically "C with proper tooling"
@cohentheblue I've heard it discussed on Linux Dev Time once or twice, but I had it jumbled up with Zigbee in my head.
-
Anyway: The worst thing an organization's leaders tolerate is what that organization becomes, and the blast radius of a single toxic contributor is huge and largely invisible. For everyone who speaks up to say this behavior isn't acceptable, there are dozens or hundreds of smart, competent people who peer into your community, see that this is how you live and move along without your ever knowing they exist, on their way to a better life somewhere else.
We don't have to live like this.
A final, selfish addendum to this: I do consulting work around questions of cultural health, process improvement and accessible cultural change. If you'd like to have a conversation about that, let me know.
-
We gave the entire (well, no-PII, no active secbugs, etc) contents and history of Bugzilla to some very smart PhDs at uMontreal, and one of the things they came back with was this: somebody submitting their first bugfix was relatively unlikely to submit a second, but somebody on their fourth bugfix is quite likely to get to five, and six, and stick around.
I cannot emphasize enough how much you get from up front code ergonomics and human care in the early stages of the contributor relationship.
@mhoye I'm very much looking forward to supporting the new user Mosscap experience. Finally I get to help build a software community I want to be part of. And *nobody* with any pull *anywhere* cares about their new user experience.
-
There are plenty of good alternatives to driving your community off a cliff like a gaggle of demographic lemmings, but if you're still convinced that mailing lists and insularity are the path to durability in this godforsaken year of our lord two thousand and twenty six then I'm not sure what words will convince you that there's nothing at the bottom of that cliff but sharp rocks and seawater.
If your community isn't accessible and welcoming to new, learning participants, the clock's ticking.
"If your community isn't accessible and welcoming to new, learning participants, the clock's ticking."
Quoted for truth.
-
@mhoye I'm skeptical that "wants to contribute to a high-profile open source project with name recognition" should be a goal anyone should be supporting.
That's the mindset that got us into the shit we're in: FOSS as a way to get one's foot in the door for cushy tech industry careers, not as a way to take a problem you understand and care about and make things better for yourself and others.
It promotes the same kind of behavior in FOSS as the Google "breaking shit to get a promotion".
@dalias @mhoye Redirecting that kid, and most importantly introducing them to basic notions of activism, autonomy, freedom & direct action (honestly just bringing them along to the local anarchist library) would serve them well in the long term.
The normative society is certainly doing its best to avoid introducing any of those concepts and rediscovering them from scratch by observation & thinking can take a while. -
for decades I'd always thought at least half of FOSS is just gig workers trying to build their CVs/portfolios to get paid corporate work, and seen (especially in AV/multimedia and telecoms) countless FOSS projects enshittify and commercialise as soon as they became popular and others gatekeep support/solution finding to nudge folk towards paid solutions (especially SaaS) to the point I've become cynical about the whole thing and often just stay on Windows as the cost of many proprietary solutions has plummeted (and some things like specialist automotive coding software and hardware simply don't have FOSS equivalents and likely never will..
@vfrmedia @dalias @mhoye For a while I thought what one did constructively was supposed to be considered impressive and help in that demonstration of skill.
(And one did those things, regardless of whether it would lead to a job, because they should be done.)
In retrospect, it is also clear that it did not in fact endear me to the corposcum.
(The entire point of the pro-corporate "open source" view had been lost on me, as I had already rejected its basis.) -
RE: https://woof.tech/@techokami/117439226690379216
The LLM part is bad news but it isn't the sign. It's the talking about planning succession while simultaneously complaining that nobody new wants to learn, that's the sign.
Y'all the kernel is in deep, deep trouble. We saw what happened to Perl and the kernel is in deep trouble.
@mhoye "But, he cautioned, maintainers should not be telling their employers about those bugs before they are public; otherwise the project as a whole risks running into trouble with government agencies worldwide. Once a fix has been pushed, though, the embargo ends. " XDDDDDDD ehhh...
-
RE: https://woof.tech/@techokami/117439226690379216
The LLM part is bad news but it isn't the sign. It's the talking about planning succession while simultaneously complaining that nobody new wants to learn, that's the sign.
Y'all the kernel is in deep, deep trouble. We saw what happened to Perl and the kernel is in deep trouble.
@mhoye tldr; #LLMs are here to stay. People who actually deliver working solutions that shape the world have spoken. Measures to limit slop are being developed. #Linux becomes even more commercial.
I personally hope more open models will arrive, GPUs will become cheaper and universal income will help people who wont be able to find job in such toxic and draining field as computer science.2026 welcome in ultimate hell everyone! Dont forget to enjoy the ride!
-
@cohentheblue I've heard it discussed on Linux Dev Time once or twice, but I had it jumbled up with Zigbee in my head.
-
RE: https://woof.tech/@techokami/117439226690379216
The LLM part is bad news but it isn't the sign. It's the talking about planning succession while simultaneously complaining that nobody new wants to learn, that's the sign.
Y'all the kernel is in deep, deep trouble. We saw what happened to Perl and the kernel is in deep trouble.
@mhoye reading the actual article I am _almost_ sympathetic: the team is clearly inundated with thousands of slop patches, and circling the wagons around just "people we already trust who have write access" is a strategy to protect their limited remaining sanity. Fine. But of course, Linus insists on undercutting all of these arguments by throwing in his personal feelings about responsible LLM usage, strong reliance on the agent triage bot, and general "we want only 10x leet coders" mentality that it easily overshadows anything the other participants may have said or believe.
-
@mhoye reading the actual article I am _almost_ sympathetic: the team is clearly inundated with thousands of slop patches, and circling the wagons around just "people we already trust who have write access" is a strategy to protect their limited remaining sanity. Fine. But of course, Linus insists on undercutting all of these arguments by throwing in his personal feelings about responsible LLM usage, strong reliance on the agent triage bot, and general "we want only 10x leet coders" mentality that it easily overshadows anything the other participants may have said or believe.
@mhoye In other words I strongly agree that: it is NOT possible to turn drive-by vibecoders into real contributors. Especially if they also respond to questions with more Claudespeak emails, don't try to engage, and violate community rules about turnaround time. It's just not worth trying to do that - the time should be spent elsewhere. Hence the search for signals beyond "sending a patch and answering an email", like "going to a conference" to indicate an actual potential contributor
But then th team captain is also dancing in the endzone using the exact same tools and praising their utility to the stars, so like, what can you really say???
-
"If your community isn't accessible and welcoming to new, learning participants, the clock's ticking."
Quoted for truth.
@unchartedworlds @mhoye Back in the early 90s BBS/Fidonet era I tried joining a C++ board and mailing list because I wanted to learn more about the language. Got rejected because I didn't know the C++ black arts. I began to resent programmers for a long time after that.
But social media did what was best-suited for: exclusion of voices that constitute noise to an in-group. Nobody is obliged to be welcoming to anyone. Rejecting outsiders did not stop C++ from becoming a central technology.
-
@hipsterelectron @froztbyte @mhoye This shit right here is why I am not working on my seL4/Idris crap in public. Giving your shit away to comrades is fundamentally different from giving your shit away to the people in the power structures above you, and we need a way to encode and defend that distinction before we can have free software that doesn't feed the monsters.
@lykso @hipsterelectron @froztbyte @mhoye > Giving your shit away to comrades
Beware shutting the door for any stranger yearning for liberation yet not already part of the community. Bootstrapping issues are a problem (and overenthusiastic gatekeeping magnifies it). -
@corbet @mhoye @gvwilson I do also wonder if these problems are in some way an unexpected social consequence of a monolithic kernel with in-tree drivers etc. It seemed like a brilliant idea for years/decades, because internal APIs could be refined without piles of compatibility layers, etc - but it also ends up creating a monolithic community.
I've been wondering for a while if a less performant microkernel(ish) approach with defined APIs would make for a healthier social ecosystem. But I guess industry might not have tolerated that performance hit.
@srtcd424@mas.to @corbet@social.kernel.org @mhoye@cosocial.ca @gvwilson@mastodon.social
It seemed like a brilliant idea for years/decades
It was decried as an awful idea by literally anyone caring about security or maintainability for just as long.
Even before considering many of the corposcum-contributed drivers are so obfuscated and underdocumented they might as well be blobs (some literally do include mystery blobs as variables).
I’ve been wondering for a while if a less performant microkernel(ish) approach with defined APIs would make for a healthier social ecosystem.
It would.
