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

[Rusty Metal Skull Gun]

I found three troons working on Alpine in less than a minute:
* Patrycja Rosa
* Willow Barraco
* Celeste

Looks like it's infected...

 

[Battlecruiser3000ad]

Pitcock

Now if that isn't a perfect term for an amhole

 

[Corn Flakes]

I found three troons working on Alpine in less than a minute:
* Patrycja Rosa
* Willow Barraco
* Celeste

Looks like it's infected...

How is that troons, particularly troons in tech, are so completely unable to come up with natural sounding names for themselves? They get to pick their names, something nobody else does, and yet they miss the mark like 95% of the time.

 

[Rusty Metal Skull Gun]

How is that troons, particularly troons in tech, are so completely unable to come up with natural sounding names for themselves? They get to pick their names, something nobody else does, and yet they miss the mark like 95% of the time.

On a related note, I tried to find out about psykose mentioned above. Didn't find much, but did find that his Steam handle used to be "alice-lilith". Lol, nearly every single time.

There must be 100 times as many men out there calling themselves "Lilith" as there are actual women. It's as male a name as, I don't know, David at this point.

 

[Perfectly Innocent]

Time to cash in on my autism and sperg out for a bit:

What security does Wayland provide against a user who is executing untrusted code? The display server doesn't stop a user from injecting malware into their own processes (LD_PRELOAD, ptrace + dlopen, etc.), and almost all of the user's software that you want to extract data from is going to be running under their uid.

Wayland stops one correctly isolated piece of untrusted code from manipulating and/or scraping another's contents using the display channel, which is not true of X11. System calls like ptrace, IPC like D-BUS, as well as sensitive environment variables like LD_PRELOAD are already securable using many other mechanisms. Basically, Wayland is a route towards having similar GUI isolation to what macOS now offers with Quartz, as opposed to dirty workarounds (e.g. X11 SECURITY extension and/or XACE) which barely approximates the level of security Windows offered since Vista with UIPI and MIC.

You're making the same mistake they are. X is crufty, it's not fundamentally flawed - or it wouldn't have been used these past 200 years.
Wayland's fifteen(!) years old now - do you really think that if those thousands of man-hours had instead been spent working on X, every bug wouldn't have been fixed several times over?

Yes, it is fundamentally flawed. So flawed in fact, that until modern toolkits bypassed most of Xorg's workflow, people had to press Ctrl+Alt+Backspace on the regular to escape full screen lockups whenever a single client application would flinch its single-threaded event loop. Even today, one can still grind it to a halt with apps both Windows and macOS is able to handle gracefully (e.g. try complex filters with Photoshop running in Wine and enjoy desktop unresponsiveness).

* Windows 1.0 -> Windows 2.0 -> ... -> Windows 11

Microsoft didn't get their graphics stack transition right either, nor did Apple, and fell back on garbage software rendering for what were previously GPU accelerated scenarios. In all cases, users experienced degraded performance compared to what they previously had. The only difference was back then everyone had to pay for their operating system, so developers would code for the lowest common denominator, allowing everyone to dodge the pain by refusing to upgrade.

In Microsoft's case, performance was vastly degraded (compared to XP) on the majority of applications from Vista through to Windows 8.0, which itself acted buggier than Compiz powered by fglrx atop a dodgy Xorg build when it first landed. In Apple's case, they had to make a similar trade-off from OS X 10.6 all the way through to OS X 10.11 (for Quartz Extreme to become stable enough to be re-enabled across their supported Macs again).

Another painful transition for Microsoft is around the corner, in the form of requiring developers to repackage their software into virtualised appx bundles for the purposes of supplying their equivalent of Linux Flatpaks and/or App Sandbox. I wish MS plenty of good luck convincing stubborn, incompetent developers to redo their poorly cobbled together tooling for their long since abandoned pet projects...

 

[Dylan]

They eventually got to him through his daughter

Women ruin everything, again.

 

[306h4Ge5eJUJ]

How is that troons, particularly troons in tech, are so completely unable to come up with natural sounding names for themselves? They get to pick their names, something nobody else does, and yet they miss the mark like 95% of the time.

"It's not about being a woman, it's about being better than a woman." How are they going to get special treatment if they fit in? The ridiculous stripper names are right on the mark, the mark just isn't where you think it is.

 

[Rusty Metal Skull Gun]

Yes, it is fundamentally flawed. So flawed in fact, that until modern toolkits bypassed most of Xorg's workflow, people had to press Ctrl+Alt+Backspace on the regular to escape full screen lockups whenever a single client application would flinch its single-threaded event loop. Even today, one can still grind it to a halt with apps both Windows and macOS is able to handle gracefully (e.g. try complex filters with Photoshop running in Wine and enjoy desktop unresponsiveness).

And they worked around the issues without spending a decade and a half writing the whole thing from scratch.

Microsoft didn't get their graphics stack transition right either, nor did Apple, and fell back on garbage software rendering for what were previously GPU accelerated scenarios. In all cases, users experienced degraded performance compared to what they previously had. The only difference was back then everyone had to pay for their operating system, so developers would code for the lowest common denominator, allowing everyone to dodge the pain by refusing to upgrade.

What does this have to do with anything? I was saying that Microsoft has for the most part preserved backwards compatibility, which is more important than people realize. "It works but more slowly" is far better than "it doesn't work at all".

Another painful transition for Microsoft is around the corner, in the form of requiring developers to repackage their software into virtualised appx bundles for the purposes of supplying their equivalent of Linux Flatpaks and/or App Sandbox. I wish MS plenty of good luck convincing stubborn, incompetent developers to redo their poorly cobbled together tooling for their long since abandoned pet projects...

Who cares? This isn't going to happen, as long as the normal Win32 way of doing things still works.

 

[Perfectly Innocent]

What does this have to do with anything? I was saying that Microsoft has for the most part preserved backwards compatibility, which is more important than people realize. "It works but more slowly" is far better than "it doesn't work at all".

What I'm saying is that Linux developers have also preserved backwards compatibility. There is no "it doesn't work at all" if you're running a half decent compositor with full support for XWayland.

XWayland is the equivalent to Microsoft's GDI-to-DWM redirection (plus some) and can even run an entire X11 desktop environment inside of it (e.g. the whole of LXDE) with all the same functionality as before. Existing applications which support Wayland still support X11 and can be ran under XWayland either with or without a full window management stack.

You can't get much more backwards compatible than that.

 

[Rusty Metal Skull Gun]

What I'm saying is that Linux developers have also preserved backwards compatibility. There is no "it doesn't work at all" if you're running a half decent compositor with full support for XWayland.

XWayland is the equivalent to Microsoft's GDI-to-DWM redirection (plus some) and can even run an entire X11 desktop environment inside of it (e.g. the whole of LXDE) with all the same functionality as before. Existing applications which support Wayland still support X11 and can be ran under XWayland either with or without a full window management stack.

You can't get much more backwards compatible than that.

You're missing the point. The API for Wayland is completely different to X, just because. Meanwhile Win32 rumbles on, as it has done since biblical times.
Anyone who thinks that spending 15 years redoing X from scratch was a good use of time is deluding themselves.

Anyway, drama in the Nix world as they're forced by troons to drop one of their conference sponsors:



Defending your country is now immoral, apparently. I wonder if it would have been different had Anduril been Ukrainian?

 

[Coolio55]

Anyway, drama in the Nix world as they're forced by troons to drop one of their conference sponsors:

View attachment 5317557

Defending your country is now immoral, apparently. I wonder if it would have been different had Anduril been Ukrainian?

"Oy vey! Application installs are getting too workable on Linux! Send in the troons!"

 

[Perfectly Innocent]

Good thing based upstream isn't so cucked!

"I like sharks with lasers. I just want the mad scientists of the world to pay me back in kind. I made source code available to them, they have to make their changes to it available to me. After that, they can fry me with their shark-mounted lasers all they want. " -- Linus Torvalds

 

[Markass the Worst]

Defending your country is now immoral, apparently. I wonder if it would have been different had Anduril been Ukrainian?

The difference is that the US is irredeemably flawed while Ukraine is holy and mighty and can do no wrong, bigot. Just ignore all the issues we're sidestepping like the Azov or the anti-fag attitudes because it's convenient for us to look past them.

 

[AnOminous]

All the fucking wayland faggots have no clue. They want to turn linux into a desktop only piece of shit because they do not understand why X11 is good and what problems it solves.

It's like they don't get that there's a reason it hasn't been replaced and "New Thing Good Old Thing Bad" is bullshit, and Wayland fucks up a lot of things that work fine. Also there's universality. This will work on anything from an old Sun Workstation with a monochrome monitor (probably stuff before that too) to the most modern terminal more or less seamlessly.

Wayland seems to run like ass on anything but a modern video card with a gigantic binary blob for a driver.

Also I hate change. And the kind of whiny faggot who is always preaching some soy-filled bullshit about Wayland.

 

[Eternal Gopnik]

Of course they don't get that. It's the "Not Invented Here Syndrome" and it's a big part of the absolute fucking state of modern day computing, open source or not. It's not unique to F/LOSS+, or even software as a whole, either, which also conveniently helps explain the absolute fucking state of everything else.

 

[brocktherock]

How is that troons, particularly troons in tech, are so completely unable to come up with natural sounding names for themselves? They get to pick their names, something nobody else does, and yet they miss the mark like 95% of the time.

They name themselves after the hot young thing they want to fuck/be, not the Mary/Susan/Rachel/Jane they grew up with

 

[Tealeaf]

They name themselves after the hot young thing they want to fuck/be, not the Mary/Susan/Rachel/Jane they grew up with

often a porn star or YA novel protag (goldmines for weird names)

 

[The Mass Shooter Ron Soye]

I found three troons working on Alpine in less than a minute:
* Patrycja Rosa
* Willow Barraco
* Celeste

Looks like it's infected...

often a porn star or YA novel protag (goldmines for weird names)

 

[Pee Cola]

View attachment 5327854

The best part is that "Celeste" rhymes with "molest", making it a perfect troon name.

 

[BIG BILL HELL'S]

The best part is that "Celeste" rhymes with "molest", making it a perfect troon name.

...and sex pest!