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

[UNIXLover]

Apparently the Wayland committees have been slow as molasses and Valve has become fed up with them not moving forward on pressing issues

Josh has a name. And he is obsessed with frogs.

So they have developed their own client server protocols, that have been rolled out and used on their Linux devices as far as I understand. Now they ask to merge their tried and tested protocol

They are protocol extensions to the Wayland protocol. They are akin to Vulkan extensions if you are familiar with those. The Wayland standard has a list of messages (requests and events) that every compositor should support along with standardized extensions to that, but also each compositor is able to make their own protocol extensions to expose additional functionality. Applications then are able to detect such custom protocols and then use them if they are available. This MR makes it so that applications that load the Mesa Vulkan driver will now use the frog-fifo protocol extension changing the behavior of vkQueuePresentKHR.
The protocol extension that gamescope's Vulkan WSI layer and compositor uses for this is pretty different. The frog-fifo protocol extension isn't tried and tested, not that it really matters, but the benefits of it are real. The goal here is to just get something working to deliver user value instead of bikeshedding on what the perfect way to expose this behavior is.

The Wayland community seems to be seething in the comments, fearing - correctly - that their oh so holy committee will lose decision making power

One wayland developer and another person stating that they do not think it is a good idea is not the "Wayland community seething in the comments."

 

[jakkufurosuto]

Wayland news everyone:
Valve Merge Request on FreeDesktop Git

Apparently the Wayland committees have been slow as molasses and Valve has become fed up with them not moving forward on pressing issues. So they have developed their own client server protocols, that have been rolled out and used on their Linux devices as far as I understand. Now they ask to merge their tried and tested protocol

The Wayland community seems to be seething in the comments, fearing - correctly - that their oh so holy committee will lose decision making power

info: works for Valve as a contractor, mainly contributes to DXVK, VKD3D-Proton. identifies as "she/they". frog quirk
public facing name: Joshua Ashton
usual usernames: misyl, misyltoad, frog
public email: misyl@froggi.es
github | gitlab | twitter (nitter) | pleroma | "website"


archive.is | twitter (nitter)


archive.is | twitter (nitter)

first time trying to aggregate info and links to someone, seems mostly benign aside from quirky tech trannyism so idc much about finding more.

 

[mentally retarded user]

Gabe fucked him

 

[anustart76]

It's a tricky situation because the problem this is attempting to solve is real. The argument used to go that you can monetize free software by selling hosting or consulting, but that doesn't hold much water when cunts like Amazon can just decide to roll in, offer your unchanged software as a service on top of their mega infrastructure, and make tons of money off your work while you don't see a dime. This has happened repeatedly.

This is why you don't use a fucking cuck license. AGPLv3 prevents exactly that.

 

[UERISIMILITUDO]

This is why you don't use a fucking cuck license. AGPLv3 prevents exactly that.

In polite company, I call them loose licenses. They're loose, like a whore.

 

[306h4Ge5eJUJ]

This is why you don't use a fucking cuck license. AGPLv3 prevents exactly that.

So Amazon takes your software, offers it as a service, links you and... still rakes in the money while you fronted the development costs. How exactly does this prevent anything?

 

[UERISIMILITUDO]

So Amazon takes your software, offers it as a service, links you and... still rakes in the money while you fronted the development costs. How exactly does this prevent anything?

Google and other corporations fear it, which is good enough for me. Now I just need to write something they'd actually want to take.

 

[Kola]

So Amazon takes your software, offers it as a service, links you and... still rakes in the money while you fronted the development costs. How exactly does this prevent anything?

Amazon will not use any software that's licensed under AGPL.

 

[306h4Ge5eJUJ]

Amazon will not use any software that's licensed under AGPL.

Did they release DocumentDB shortly after MongoDB switched from AGPL to SSPL just for funsies or what?

 

[Kola]

Did they release DocumentDB shortly after MongoDB switched from AGPL to SSPL just for funsies or what?

Ok, I misunderstood what you meant. They can't modify the software they're offering as a service, but they can provide it as-is.

 

[Weapons of Mass Tardation]

So Amazon takes your software, offers it as a service, links you and... still rakes in the money while you fronted the development costs. How exactly does this prevent anything?

Having worked inside of ${FAGMAN} and other ${TECHNOLOGY_MEGACORP}s the AGPLv3 is like garlic to vampires. You can watch the expression of business development and product types go from salivating over milking some autist's passion project selling it to infinity shitty startups to abject horror and sadness when they see the license. It's one reason that unless something is being written for hire to be open source, I don't understand why you wouldn't use the AGPLv3 on everything now (even that isn't enough, since shit ends up getting laundered through "AI" anyways) unless you have a fetish of getting used and abused like a loose whore as our APL autist friend mentions above. It's a shame you can't say nigger in polite company, otherwise I would recommend just going AGPLv3 + NIGGER for all of your licenses.

Some startups are going ‘fair source’ to avoid the pitfalls of open source licensing (archive)

No more of that "open sores".

Unless we go back to free money forever (i.e. ZIRP and NIRP) "open source" startups/companies for the most part will continue to be money pits for the naive. Corporations are all almost exclusively retarded and greedy, and even if they depend on your software, will basically never contribute anything back to your code (or your pocketbook) if it's open source. The best you can hope for is getting hired as something like a dedicated developer for an open source project like the kernel at BIGCO. It's a shame, Stallman was and is right, always, but all the open source startups do is light VC money on fire, and VC money has getting harder and harder to come by recently and brazenly lighting on fire is going out of style (believe me, I've tried). No amount of weaseling around will ever change that; you have to sell your product for real money and bar access to it if someone doesn't pay.

Wayland news everyone:
Valve Merge Request on FreeDesktop Git

Apparently the Wayland committees have been slow as molasses and Valve has become fed up with them not moving forward on pressing issues. So they have developed their own client server protocols, that have been rolled out and used on their Linux devices as far as I understand. Now they ask to merge their tried and tested protocol

The Wayland community seems to be seething in the comments, fearing - correctly - that their oh so holy committee will lose decision making power

I will make a wager that we'll all still be using X11 or at least XWayland in 10 years, and Wayland, like BTRFS will still be "in progress."

 

[Kyangyenki]

Josh has a name. And he is obsessed with frogs.
View attachment 6452934

They are protocol extensions to the Wayland protocol. They are akin to Vulkan extensions if you are familiar with those. The Wayland standard has a list of messages (requests and events) that every compositor should support along with standardized extensions to that, but also each compositor is able to make their own protocol extensions to expose additional functionality. Applications then are able to detect such custom protocols and then use them if they are available. This MR makes it so that applications that load the Mesa Vulkan driver will now use the frog-fifo protocol extension changing the behavior of vkQueuePresentKHR.
The protocol extension that gamescope's Vulkan WSI layer and compositor uses for this is pretty different. The frog-fifo protocol extension isn't tried and tested, not that it really matters, but the benefits of it are real. The goal here is to just get something working to deliver user value instead of bikeshedding on what the perfect way to expose this behavior is.

One wayland developer and another person stating that they do not think it is a good idea is not the "Wayland community seething in the comments."

It's Misyl Ashton now you chuddies

Edit, have a bonus:

https://x.com/misyltoad/status/1811881082800730622

 

[HootersMcBoobies]

Did they release DocumentDB shortly after MongoDB switched from AGPL to SSPL just for funsies or what?

Same with ElasticSearch and OpenSearch. I don't think they'll try to adopt any new services that are AGPLv3 licensed, but when Elastic Co changed their licensing, they couldn't just stop offering their version of it. But they also need to maintain it, so forking it under a compatible license seemed to be the only route they could go.

It's weird since AWS constantly takes advantage of open source to build their overpriced garbage services without really contributing back, but at the same time, they're keeping Elastic Search open source with their fork (the elastic license is no OSI approved or considered open source)

 

[Short Circuit]

I don't know if it's a hot take, but personally if I had to make an FOSS project, I would certainty make it as safespacey and inclusive as possible, autists and troons may be hard assets to make them play together, but they're certainly will get attached as fuck to your repo and slave away with working for it for free with no strings attached, signing off each of their commits for the "greater corporate good". For example I really like programming in Rust and really enjoy the progress so far on Wayland especially on low power devices(raspberry pis) where even X is struggling to run.
I kinda understood that the boards and foundations have quite a difficult time existing and managing assets. Remember, for example Rust Foundation not only has to manage its own resources, and continue development of the language, but also establish business relations with Big Corpos and such.
If some troon gets a welfare check but they spent all their time in the wage cage of their shared accommodation making sure Steam works on my monstrosity of a GNU/Linux distro, I'm fine with that.
tl;dr use whatever works for you, usually OSS drama where its just troon maintainer stepping down isnt gonna really impact anything you use

 

[Carpenter Trout]

To be honest, @Short Circuit, most tech troons can't contribute for shit. All they do is join, ask you to add pronouns and useless shit, and the moment you give them an inch they take a mile. It's not rare to see F/OSS projects get completely derailed by lunatic troons that can't do anything except ruin everything. Maybe at first they'll do something, but then they just slow down as they start engaging in meaningless flame war over basic biology or why math is racist. and if the program no longer compiles, you're troonsphobic.

Minor tangent, but I'm not "transphobic" in the sense that I have a "phobia" of you. I'm just very disappointed in you. (and I'm fairly sure this lukewarm take is shared among the whole forum as well as a big chunk of the internet, including LGB+ communities)

 

[DavidS877]

X is struggling to run.

X11 came from a time where the big computers had a 16MHz processor and 16MB of RAM. It shouldn't have any problem on any modern hardware.

On the other hand, in the beforetimes(my lawn, get off it) we had Motif and CDE crapping everything up. Now we have Gnome, GTK and KDE. Same shit, different decade century.

 

[Short Circuit]

X11 came from a time where the big computers had a 16MHz processor and 16MB of RAM. It shouldn't have any problem on any modern hardware.

I don't know but in my experience, when it comes to X windows on like raspberry pi's it tends to make input latency increadibly laggy, maybe if i ran cwm or twm it would be better, but at this point you can just use it over ssh and have a better experience, wayland just outright has better latency on single board computers including compositing and vsync, makes it a way better experience. Still using X on desktop though.

To be honest, @Short Circuit, most tech troons can't contribute for shit. All they do is join, ask you to add pronouns and useless shit, and the moment you give them an inch they take a mile. It's not rare to see F/OSS projects get completely derailed by lunatic troons that can't do anything except ruin everything. Maybe at first they'll do something, but then they just slow down as they start engaging in meaningless flame war over basic biology or why math is racist. and if the program no longer compiles, you're troonsphobic.

You are right but I personally noticed it to be more of a loud minority than a majority, but also I dont know im not in any gay discords and dont browse /g/ or HN so maybe my viewpoint is skewed.

 

[Markass the Worst]

Edit, have a bonus:
View attachment 6454389

https://x.com/misyltoad/status/1811881082800730622

He's obviously talking about Vaxry and Hyprland but he's too much of a pussy to name them. Daily reminder that Drew DeVault is responsible for Hyprland's negative reputation.

 

[GhastlyGhost]

It's Misyl Ashton now you chuddies

View attachment 6454366

Edit, have a bonus:
View attachment 6454389

https://x.com/misyltoad/status/1811881082800730622

I wish for these disingenuous cock suckers to switch out the cock for a shotgun because they couldn't leave well enough alone and made it my problem. I'm not sure what could possibly be done to make them understand.

 

[Kola]

The Winamp thing is hilarious. Beautiful flamewar with clueless people on all sides:

Please tone it down, I don't want Winamp to regret opensourcing

Licence violates github TOS