10 ms·
Nobody who removed the joke said they were offended by it, they just said that they didn't believe it was the sort of thing that belonged in technical documenta
by geofft 9y ago
Nobody who removed the joke said they were offended by it, they just said that they didn't believe it was the sort of thing that belonged in technical documentation. If anyone is offended, it is RMS, in the sense that he seems personally affronted that he doesn't carry the line-item veto power he thinks he had over all of GNU and people did not ask him before removing something he added 25 years ago.
Not everyone who disagrees with something is offended by the thing they disagree with. Shall I say that someone who prefers writing documentation in man pages instead of Markdown is offended by Markdown? Is Project Zero offended by buffer overflows?
- flukus 9y ago> they just said that they didn't believe it was the sort of thing that belonged in technical documentation I've been dreading the day OSS projects became as soulless and boring as corporate ones. If we can't have jokes in technical documentation then it seems that day has come. Next the FOSS HR department will be asking them to rename the abort function.
- sitepodmatt 9y agoThe day went and passed a few years ago. SJW asswipes campaigned to have the phrased blacklist removed from projects and changed to allow list, also 'slave database' too because it could offend some dead ancestor that was a slave? These little cry babies are ruining tech, another example MS just had a tech conference with a cuddle farm, they imported animals so people could feed and cuddle them in the event any of the talks accidentally included trigger words. Don't forget crockfordgate - the javascript legend (the good parts book) who described brackets as dogballs and was mercilyless hunted by SJWs including being removed from jsconf. Sad times.
- geofft 9y agoThere's certainly something lost here, I won't deny that. But glibc, and huge other parts of the FOSS ecosystem, has been a corporate project for years. Maintenance comes from stodgy companies like Red Hat who install glibc on the sort of extremely stodgy companies who are Red Hat customers. And for those of us whose day jobs involve using glibc and reading its documentation, we deserve the benefits of free software as much as everyone else. If it is an ethical imperative (as RMS says!) for all software to be free and for proprietary software to die, it follows that the primary battleground is the servers of soulless, boring corporations. Your hobbyist laptop is important, too, because everyone deserves free software. But if free software weren't around, you would have installed a pirated copy of Windows with a keygen with some hentai as its background image and enjoyed the non-HR-compliance of the process, and Microsoft would have been quite okay with it because you would be locked into their proprietary software. If free software is an ethical imperative - or even if it's not, but even if open source is simply a better way to develop software - then everyone who wants a job in software engineering and is qualified for it should be able to have a job in writing and maintaining FOSS. Human society has determined that if we want everyone to participate in an activity, things work better if everyone agrees to uphold a few norms. They don't have to be the same norms as boring corporations uphold (and you can quite easily argue that the norms of boring corporations aren't that good, actually, at making sure everyone is welcome to participate on equal terms). But the fact that we open our shared infrastructural work to accountability and public judgment is sort of how civilization works. Hobbyist projects are still as possible as ever. Twenty years ago, you wouldn't have been able to get inappropriate jokes in the technical documentation for Solaris libc, or into MSDN, or whatever, but you could work on some upstart free software project with your friends and do whatever you want. You can still do that. If you want to be the young, upstart libc with some off-color political jokes that's being an alternative to the boring corporate libc, more power to you. Not everyone will participate, but that's what you want. Meanwhile, the libc whose goal in life was to displace the corporate libcs has won - and needs to step into its role.
- __s 9y agoYou see it too in people going around telling people to stop saying master/slave for clusters https://github.com/antirez/redis/issues/3185 https://github.com/antirez/redis/issues/3185
- keiyakins 9y agoI think you're looking at the wrong axis. This isn't an order-vs-chaos question, it's one of constructive vs destructive. This particular joke makes the manual worse, not better, at being a manual. Cut it and move on, and always keep an eye out for places it could be improved, whether that be through better descriptive prose or a good, understanding-building joke.
- roenxi 9y agoTechnical documentation isn't the place for a joke full stop. Documentation is for people who are typically busy, uncertain and potentially dealing with something that is going wrong. They want clear, concise and accessible help. They don't want or need tasteless jokes. It is disrespectful to their time to include random garbage. This is supposed to be read by people who need it, not people who know what is going on and want to enjoy a good laugh.
- thiagoharry 9y agoThe TexBook was a technical documentation for TeX written by Donald Knuth. The book had a lot of jokes, and I enjoyed reading it.
- geofft 9y agoLeaving aside the question of the nature of its jokes, the TeXBook is the sort of thing you read straight through. It's a narrative about how some code came to be. It's not the same sort of reference as the glibc manual, and I think a narrative form of documentation benefits from a casual tone and a four-sentence standalone reference about a function (especially where one of those sentences is "Preliminary: | MT-Safe | AS-Unsafe corrupt | AC-Unsafe lock corrupt") benefits from a terse tone.
- hapnin 9y agoKnuth is actually funny.
- lrl939ndj 9y agoAgreed with RMS in spirit Disagree with his application in this context I don’t give a damn about your politics when I’m trying to solve a problem unrelated to them
- makomk 9y agoThe main justification for why it shouldn't be there is that it was offensive. The idea that software should not be political is, in fact, itself just as offensive to the community of campaigners who've joined the calls to have this removed as this joke is. The last big controversy I saw was the entire console jailbreaking community being declared a bunch of bigots because someone mocked the idea that code could have views on LGBTQ rights.
- geofft 9y ago> The main justification for why it shouldn't be there is that it was offensive. This is simply untrue; you can look at the patch's commit message and the review thread. The primary justification was that it wasn't appropriate, and the secondary one is that it wasn't actually funny and was tasteless. Nobody said "offensive". You can read the thread yourself. https://sourceware.org/ml/libc-alpha/2018-04/msg00595.html https://sourceware.org/ml/libc-alpha/2018-04/msg00595.html (The April history shows the conversation between maintainers regarding the patch itself; if you want to see RMS' reply, go to the May index. RMS and Alexandre Oliva, the two people defending the joke, brought up the concept of "offense", and people repeatedly say in reply that they're not offended. Oliva later says he's offended by other people in the discussion.) Of course, you're also welcome to believe that everyone who disagrees with you must be offended; you're entitled to your opinions.