Open Source Software Community - it's about ethics in Code of Conducts

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Sadly your prediction is accurate; the flame will burn out. We are starting to see the damage of pozzed influence. It's evident with the forced adoption of Rust. As of recently even Rust cultist are admitting Rust in the kernel is technically inept decision.
I'm fairly optimistic about this, actually. Very little work is being done on rust in the kernel now and the "experiment" has been declared over, so it'll hopefully face much more rigorous oversight in the future.
 
Sadly your prediction is accurate; the flame will burn out. We are starting to see the damage of pozzed influence. It's evident with the forced adoption of Rust. As of recently even Rust cultist are admitting Rust in the kernel is technically inept decision.
Torvalds has been consistently pro-Rust for years. He has also been consistently against drama-seeking trannies, e.g. https://forums.freebsd.org/threads/...es-into-linux-kernel-rust-driver-drama.96732/

Smart people realize that Rust is a separate thing from trannies. Being anti-tranny is wise. Being anti-Rust is just catty.

I’d love to see an example of your claimed Rust experts admitting Rust in the kernel is bad.

I'm fairly optimistic about this, actually. Very little work is being done on rust in the kernel now and the "experiment" has been declared over, so it'll hopefully face much more rigorous oversight in the future.
By “very little work”, you mean “the kernel allowed the C UAPI part of the Rust Asahi GPU driver to be committed before the actual driver, in violation of their own processes, because they anticipate the driver being merged this year”?

The GPU driver is 21,000 lines by itself, discounting the downstream Rust abstractions we are still carrying. It is almost double the size of the DCP driver and thrice the size of the ISP/webcam driver, its two closest rivals. And upstreaming work has now begun.

We were very graciously granted leave to upstream our UAPI headers without an accompanying driver by the DRM maintainers quite some time ago, on the proviso that the driver would follow. Janne has now been laying the groundwork for that to happen with patches to IGT, the test suite for DRM drivers.

There is still some cleanup work required to get the driver into an upstreamable state, and given its size we expect the review process to take quite some time even when it is ready. We hope to have more good news on this front shortly!
 
By “very little work”, you mean “the kernel allowed the C UAPI part of the Rust Asahi GPU driver to be committed before the actual driver, in violation of their own processes, because they anticipate the driver being merged this year”?
Last I had checked, there was very little work being done and only a single maintainer left standing. If that's changed in the last few months, then I guess I'm wrong.
 
Smart people realize that Rust is a separate thing from trannies. Being anti-tranny is wise. Being anti-Rust is just catty.
The problem with anything where a lot of the maintainers are trannies is that they'll eventually have psychotic meltdowns and wreck the project, so if you depend on that project being maintained, you're going to be let down eventually.

I mean even nool uses Rust. But not for things where you need it to be maintained.

So minor projects for a website? Probably fine. Putting it in the kernel? No thanks.
 
Omacon a convention for fellow Omarchy Linux fans, enter right now for just ... $299

https://x.com/dhh/status/2024142918861140446?s=20 https://archive.is/BA74R
https://www.omacon.org/ https://archive.is/VIqmo

1771445275640.png

Also I guess this is what Vaxry looks like:

1771445410333.png
 
Stack Overflow is having a redesign!
page | archive

They're also sneakily removing votes-to-close and reviews, and hid that part in the redesign announcement (the bolding in the currently archived version was edited in).
Tranny jannies, who do it for free, are not happy!
Screenshot_20260219_004103.png
history archive
 
If such a perpetual license were viewed by a bankruptcy court as being an executory license, then yes, it may be set aside in bankruptcy proceedings. Moreover, though, even if it were not considered an executory license, and hence were subsequently purchased in bankruptcy by a third party, that third party could then turn around and revoke the existing license since, again, the GPL is described as a bare license, and bare licenses are revokable at will. Any confusion you may have surrounding this point stems from the FSF wanting the GPL to be characterized as a bare license instead of a contract in the SCO trial for strategic reasons, but not wanting it to be treated as one when it comes to revocation. In short: The FSF has been trying to legislate a contract-thats-not-a-contract license for decades which can and will explode the second it's put in front of a judge.
lmao i spent years dealing with 365(n) issues after 2008 and gave myself an aneuyrsm staring at all the case law. it's so convoluted that courts have a hard time following how all this maps onto IP licenses. You've done a better job explaining it than anyone could hope for, but good luck getting lay ppl to follow this. It's very frustrating to see FSF just make shit up in their license in an overreaching attempt to rewrite copyright and licensing law, using patent law concepts to try to make the license "inherent" to the software contrary to copyright law. What FSF are trying to do is impose right to repair/EU Data Act-style protections for consumers without doing all the messy work of actually engaging in the legislative process. GPL can't get us there for all the reasons you described and a bunch more. People in the thread keep thinking that us pointing this out means we oppose the FSF's goals, when it's that the goals are good but GPL is counterproductive in getting to where we all want to be. It's the autist engineer's worldview that politics is wrong and fallen, and if only the world was run by dictatorial technical experts then all of these problems would be solved by expert fiat. Or here, it their hope they can mechanistically apply a license as if it were self-executing code that worked on people. The Soviet Union was and the PRC is run by this kind of technocratic ideology and they both hit worse fail-states than the US's subjective, political, non-technocratic style of governance.
 
Last edited:
lmao i spent years dealing with 365(n) issues after 2008 and gave myself an aneuyrsm staring at all the case law. it's so convoluted that courts have a hard time following how all this maps onto IP licenses.
You know what bothers me?
When we had our IP law classes (which were a part of our IT degree), we were told that law isn't about fairness, it's about order.
The problem is that there is no order as it stands which defeats the purpose of the legal system (copyright) in the first place, and needs to self-justifice its existence.
The purpose of the system is what it does which apparently is a well-oiled Kafkaesque machine designed to (legally) rape you into submission.
 
Stack Overflow is having a redesign!
By removing the review queues and close votes, they're going to let all of the pajeet/llm slop overrun the web site and then try to dump it on another company. Good news for Experts Exchange.
 
So... what would actually change?
The nature of the web site and its inhabitants? Nothing. However, when that chart came out last month showing their drop in questions reaching the all-time low, no doubt they freaked out and so they're willing to do anything to get the traffic to appear new and relevant on the web site. Not being allowed to close the slop will let them generate metrics showing just that.
 
Tranny jannies are not happy!
to the shock of nobody. trannies could get literally everything they want and they will still not be happy.
So... what would actually change?
i bet it annoys a lot of people but i actually find it kinda hilarious when i'm looking at a question and then way down at the bottom there's muhdar raknesh giving a completely absurd answer that's often not even related to the question. it's like hacktoberfest but it happens every single day. you just know regular users are sick of it too but they can't allow themselves to talk about the elephant in the room. suffah.

it makes sense their traffic dropped like a stone too. stackoverflow and it's sister sites are an absolute goldmine for training LLMs, it was probably the first sites that were scraped.
 
Last I had checked, there was very little work being done and only a single maintainer left standing. If that's changed in the last few months, then I guess I'm wrong.
There is still a fair amount of rust code and fixes going into the kernel.
"git log -- *rs"
But most of it is for existing subsystems already done in rust like parts of usb and drm.

The maintainership is of concern though. Rust is different enough that it is unlikely many C developers can help much with this making a shrinking pool of dedicated rust maintainers risking burnout.
They do need more people to step up and offering to become long term rust maintainers but I think it is one of these situations where there are many advocates but few actually willing to put in work.

Personally I would have preferred to see if and how much of the kernel could be built with fil-c and what the performance impact would be.
 
Back
Top Bottom