this project is a dignified non-dogmatic rationalist marketplace-of-ideas meritocracy. that is why this particular controversial technical issue is beyond discussion, and we will be moving forward with my personal opinion without any community input. it is fine for me to have this position as the BDFL because if you don't like it you can always fork our open source code and spend decades building up the institutional material support necessary to maintain this critical infrastructure
7
Replies
·
0
Boosts
@aeva "It's just a tool! We are primarily concerned with technology! How dare you question the implications of what we are making and how it is made! Don't bring ethics into this you social justice warriors! La La laaa!! La la laaaa!!!"
Linus is really showing himself to be just another slop-obsessed boomer who drank a little too much corporate techno kool-aid. Disappointing but not surprising.
@aeva This project is super rational, we only make decisions based on technical merit, which is why we use the word "clearly" to describe how useful the random text generator is, despite repeated reports of it never generating any measurable return of investment of any kind.
Research papers about increased generation of buggy and insecure code? Research papers about de-skilling and cognitive laziness? Come on, how many times do we have to repeat the word "clearly" to make our rational argument?
there's another better world where the rust-linux project took on a hardline anti-slop stance, forks linux over this, RIIRs out the rest of the C in kernel, and successfully runs away giggling with the institutional support
@aeva honestly it's so funny to me that getting slop into the linux kernel was this easy while getting rust out of "experimental" in the linux kernel took around 5 years
@aeva after I realized the wgpu maintainers are AI enjoyers I just don't put hope in anyone doing this stuff. The mesa people seem pretty cool tho.
@radgeRayden i've definitely heard a lot of rust people express disappointment in project after project taking up the mantle of memory safe slop, which as an outsider presents an interesting paradox: is the rust community anti-slop because the rust people in my orbit are all against it, or is it pro-slop because (afaict from the complaints by said people) major rust projects keep jumping on the slop wagon
@aeva @radgeRayden I feel like this split shows us who actually cares about rust's relative advantages like memory safety, and who just uses memory safety as a convenient sales pitch. If you want memory safety because it makes it easier to maintain a secure codebase, it's incoherent to then also say "slopcoding is good, actually"
