No rest for the virtuous

user shouting

user: "YOU MUST IMPLEMENT XYZ!!!! IT'S ESSENTIAL FOR MY USECASE"

answer: "Thanks for your feed back. We accept pull requests. "

and the user was never heard from again.

Until later on a random blogpost happens about "why FOSS is dying" or "why FOSS developers are rude" and you get namedropped :D
or you can be gnome, and "accept pull requests" by letting them stall for 8 years for no reason, refuse to elaborate, then claim your getting bullied when users get upset. that's a solid third option
- I'm guessing you're talking about something specific and if so could you link the pull requests or repository?
What do you mean giving back to the community? We already report a use case!!
Honestly, the biggest issue for me is that it's someone else's code that is usually not following industry standards of maintaining something. Usually, it goes off in some open-source standard way of doing something. If more projects were better at standardizing toward the known industry standards then it'd be far easier for me to jump into.
- Where "Industry standard" is EBCDIC? ASN.1?
  Now don't get me wrong ASN.1 is actually kinda nice but if the industry wants FLOSS to adopt it it better produce some actual, comprehensive, FLOSS libraries that make working with it easy. In other instances they shout "noone supports our standards", while simultaneously locking those standards behind $10000 fees to even view. Or they invent brand-new ways to do things just for the heck of it and refuse to be compatible with every other manufacturer out there, see e.g. the NVidia kms/gbm saga. "Yeah we know we're writing a linux driver but let's just ignore how every other linux graphics driver interacts with its environment". Hardware companies trying to productise software leads to some atrocious insanity.
- But which industry standard?

Ignore the shouting; ignore the project; take a vacation and relax.

Id anybody paying you to be a FOSS developer? If no, you can do whatever you want with it.

It's a volunteer thing at the end of the day!

Wayland development. Tons of folks yelling “X is good enough!” Where they just ignore that no one is actively developing XOrg which is pretty much the biggest X11 implementation.

Plenty maintaining XOrg but new things aren’t coming to XOrg, there’s just no one there the XOrg devs moved to Wayland.

So all these people shouting, they’re telling you keep a piece of software that’s very fragile, in a space that hardware makers are progressing at rapid pace, has decades of hot fixes, duct tape, and cruft, and nobody is actively developing for.

Like I just don’t understand the people yelling that Wayland is raping peoples wives and setting fire to their dogs. The yelling group is screaming for people to use something that nobody wants to work on and nobody is paying enough for people to work on. The code base is horrible and it easily causes burnout in three weeks or less. No one in their right mind is picking it up for shits and giggles.

So if everyone abandons Wayland, what’s the end goal? Keep riding XOrg till hardware outpaces it completely? Like I don’t understand what the Wayland haters are trying to get at. There’s so little going on in XOrg at this point and everyone seems to universally hate the code base. And a rewrite of the base sounds a whole lot like Wayland but artificially adding in X11 restrictions that make no sense since we all aren’t using PDP-11 to run the clients.

I get that Wayland has configurations that don’t work yet. All software has bugs, including X11 implementations. But Wayland is arguably a technology that is more in line with how modern hardware works than the X11 protocol will ever be. And Wayland is designed to be easy for devs to work with, not a cobble of archaic limitations due to a protocol that was designed for 1970s era computers.

That level of hate for Wayland is just this confusing Luddite cry for software that hardware that properly supports it no longer exists. The reason modern video cards do run on X at this point is because of a lot of hacks. I thought everyone understood this when we did the whole AIGLX vs XGL thing.

its crazy to think that such an old display server is still being used and even defended to this day. X these days feels like a small thing with way too many extensions.
- It has many neat little features that will never get implemented into Wayland for security reason (e.g. want to play a video on a button in your spreadsheet app using mpv?). It was fun while it lasted, but the next generation will never be able to experience it.
You're listening to loud asshats and assuming they're the majority. They're not.
One day Wayland will reach a tipping point where it will replace X. Until then, most users will just stick with whatever their distro installs. Most people don't care one way or another.
As for me, I'm probably gonna to stick with X until I have no choice because I actually use the network features that Wayland isn't replacing. That doesn't mean I hate Wayland - I've never used it - it just means it's not the best software for me at this time. Most people never do anything with X that Wayland can't do and won't notice when it becomes the default.
- Frankly, the only reason I care is the end-user drawbacks that Wayland seems to have. There are tons of bugs and issues. On top of that, I use Nvidia proprietary drivers which also causes more drawbacks and issues. It feels like at this point a third option needs to be made available. It's been 15 years since Wayland was released and it still has a large amount of bugs and isn't ready for most distros to adopt it.
  I've not touched the Wayland or Xorg code, and I've not looked into why Wayland is so broken, but the major issue I see is that it's taken them 15 years to still have a buggy display server. Display servers need to be the most stable you could possibly make them. They need to be made with desktop and fullscreen exclusive apps in mind. They need to be made modern and extendable while also ensuring those extensions aren't able to crash the entire display server. They need to be robust and that's just not what you are going to find with Wayland, or Xorg, or perhaps even Linux in general.
- You know you can run XWayland and have clients connect via network?
  There's still some development going on in Xorg and it's pretty much all XWayland, it's going to stay alive as a compatibility layer for the forseeable future and beyond. And as a network layer until someone thinks of something better (no, sending video isn't better, the strength of X as a network protocol is that it doesn't need much bandwidth). It's the hardware interface stuff, actually throwing pixels on screen, that's thoroughly dead.
Like I don’t understand what the Wayland haters are trying to get at
New things bad.
- I feel like this is the answer to almost any case where many people hate on something.
[This comment has been deleted by an automated system]

Well, I'm a Windows user who just installed Linux Mint and spent a day setting up the free software media streaming server stack. It was a fun project, and it is impressive how well the many parts work together.

So, I'm just here to say THANK YOU to all of the FOSS developers out there. I am truly amazed at the incredible work you do!

FOSS user:

Wants to improve the software and sees easy fixes, but isn't allowed to create a Merge Request because company policy disallows you from writing code for other projects on company time

Good luck with them holding that up in court. Just do it on your own hardware and you're good to go
- I don't really code in my free time, every merge request for a FOSS project I wanted to do so far was for company projects where a feature was missing or buggy. My GitHub and Gitlab accounts are full of outdated forks we needed for a minor change in the FOSS project which I was not allowed to merge upstream
- Not submitting the pull request until off work hours (maybe a hour or two after the shift whistle blows) would also be a good story to show the court.

I'm about to post out a new FOSS project I've been working on for a while, so this is making me a bit nervous

Don't overthink it. Just publish. And as for entitled users, remember that you don't owe them. If anyone insists on a feature, tell them that you can prioritize them for the right fee.
- Or link the contributing page 😂
In reality, those demanding users only start to show up once you have a huge number of users. Post the project and just ignore support requests until you feel like working on it.

[cries in seeing how people treat ROM maintainers]

Doesn't worth the mental burnout buddy