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

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
ve looked at some Hyprland code before (the parser for Hyprlang, specifically) and honestly, I agree. The code is atrocious and reeks of whippersnapper who thinks he's a C++ god.
I think Vaxry (the lead dev and the reason why trannies are seething) is pretty young, no? So it's somewhat understandable. He had Drew with him, but of course this faggot was more interested in trying to break Vaxry into sucking tranny dick than teaching him anything useful.
 
Void is a nigger distro for making mixed cased package names. "Oh it's what the upstream named it" I don't care and I don't want to have to query for both foo and Foo to find a thing and you also get problems like thunar where it was uppercase but is now lower. Except in Void's case of course where it's still uppercase and a bunch of libs are lowercase. Red Hat also does this. Red Hat is also very gay and extremely retarded.
 
The maintainers try to play it off as this is because they aren't satisfied with the quality of the code.
I've looked at some Hyprland code before (the parser for Hyprlang, specifically) and honestly, I agree. The code is atrocious and reeks of whippersnapper who thinks he's a C++ god.

Powerleveling, but yes I can confirmed this. Especially the "plugin" system is the biggest piece of garbage ignoring security practices we've had since 20 years.

They map the .text section read-write :story: and then have plugins register its hooks that then monkey patch a trampoline into the hooked function (x86_64 only [maybe i386 too] unsurprisingly).

Their plugin manager has also gotten them into trouble recently, where they've had it set up in a way that it wrote the compiled plugin into a world readable location and then loaded it by path. An attacker (process owned by any user) could just swap the shared library with their own before it was loaded and have their arbitrary code run with compositor level access.
 
They map the .text section read-write :story: and then have plugins register its hooks that then monkey patch a trampoline into the hooked function (x86_64 only [maybe i386 too] unsurprisingly).

An attacker (process owned by any user) could just swap the shared library with their own before it was loaded and have their arbitrary code run with compositor level access.
If thats how these morons write C++ then I understand why the other half is shilling Rust. I'd like to see how bad the Rust they write is. X11 may be ancient but it was at least written by proffesionals, do they really not have a single real programmer in the Wayland hugbox?
 
You can't just write a window manager for Wayland.
Wayland is a protocol. Nothing is preventing people from having the compositor be separate from the window manager like everyone else.
here's a big "Lol, Lmao, even"-worthy thing delivered to us by Lunduke
His article? 75% of it is ad hominem or irrelevant and the rest is him complaining about a clause that allows for AI models that were trained off copyrighted material like the web.
 
So, what's stopping anyone from just ignoring their bullshit and releasing software under an open source license?
Nothing. He talks about it in the article the video is based on: https://lunduke.locals.com/post/591...tion-not-open-built-by-dei-funded-by-big-tech

What Impact Will This Have?​

While many may argue that this "OSAID" is simply irrelevant -- and can be ignored by the broader "Free and Open Source Software" industry -- that misses a key impact that is worth noting.

That being: The continued corruption of both the ideas and the organizations of Open Source.

Not only has the Open Source Initiative banned their founding members (and re-written their own history)... they are now seeking to create a new "Open Source Definition" which will allow for systems consisting primarily of closed, proprietary data to be considered "Open Source". Thus making their Big Tech financiers happy.

The meaning of the term "Open Source" is being actively modified to mean "A little open, and a lot closed". And many of the same corproations which are funding this effort are also funding things like... The Linux Foundation.

Which means this corruption and dilution of the concept of "Open Source" is likely to spread far beyond the reaches of one, small (but growing) licensing certification foundation.

Also, apparently, decolonizing values... or something.
 
I guess I can see why the government would want it to be used in its own systems. One would think, though, they wouldn't be pushing for widespread adoption just because of that. It doesn't seem like it would harm the average consumer-level user, so I'm just not seeing how this is against the public interest?
Most government systems are made with off-the-shelf, commodity gear, instead totally custom, bespoke, one-off equipment designed in-house. And even then, the custom stuff tends to use at least some commodity off-the-shelf parts.

Oh, sure, DoD and other high-security stuff might be programmed with Ada, but most government systems aren't the hyper-secure setups used by the Pentagon or the NSA. The workstations at the DMV are running Microsoft Windows, and using Active Directory to secure their logins. The datacenters the Department of the Interior uses to store their annual tree-inspection reports are secured with Cisco firewalls. And even within the higher security branches of government, you are still going to find regular tech gear being used. Various factors drive this. Part of it is being able to hire people who know the systems and tools and can manage them.

So much of this commodity gear is programmed with C and C++. If Rust were to become commonplace and as widely used as C and C++ are today, then that means gear that doesn't suffer from C's and C++'s flaws is more widely available to the government, too, and it will be easier to hire people who can maintain it.
 
So, Windows is garbage and Linux trooned out. What's left? Just BSD?
given a guess people my go back 2.0linix core as vs toolinix3.0.then start make there own again some in pubic side known ware look bigger deal for them hide right now form loonytoons party’s. Window need fully rip out Linux group before get canbeledzed up. So ya see lot linix moving around free bsd be free one mostly., few partys noted windows pushing back for anlog more res only for next yr computers my remove some toons and fuz balls in there as well. Out needing to hide in new spots. Heard weebs Dune there own os .thay bet planing look for Luwd os to do there art. .other move it fast. Case of pureton goofness to happen as well.lmao any way.word digial sovereignty come up more.as yr goes on even vr or ar cumupter seen tested as well. Lot more just that alone It few thing I have seen.
 
Last edited:
Back