This isn't meant to be confrontational. If you don't want to spend money on code provided by volunteers (or whatever your justification is), that's fine; it's your money and your life philosophy.
But at least be classy about how you conduct yourself; if you don't want to pay then just say so instead of coming up with endless excuses.
In my life I have had precisely 3 opportunities to realistically pay for a Linux distro:
- A boxed copy of Mandrake (found on the shelf at Sam's Club many years ago) that got me into it in the first place. I talked my mom into that one.
- Professionally, evaluating whether the support and customer service provided by Red Hat was worth using it over CentOS. My recommendation was no, and as it turns out since we did not run software that required it, we never encountered a problem that having their assistance would have solved.
- Semi-professionally, really wanting to throw some money to the Proxmox team for access to the enterprise repos and support ticketing on my home-lab-ish cluster, and not being able to afford it because they insist on annual billing.
So no, sometimes it's as simple as the combination of price/features/support not being competitive with the free alternatives.
If I wanted the ability to submit 3 support tickets per year with a one day turnaround time, that price triples. I could easily justify splitting that cost monthly, but not upfront all at once.
Heh, at first I parsed that as IPC socket.
Now I'm amusing myself thinking about which companies would try to charge for that.
I don't think that follows logically. People who won't pay for Red Hat, after Red Hat's deemphasis of desktop work, might still willingly pay for another desktop focused distribution.
Obviously, certain types of desktop work have been de-emphasized. However, there are a lot of other types of desktop work which Red Hat does, which are continuing or even increasing in resources.
* Pipewire
* Filling in the Wayland gaps, e.g. color management and HDR
* Contributions to Firefox e.g. VAAPI hardware acceleration
* Mesa / RADV driver contributions
* Improving the Nvidia driver situation in collaboration with Nvidia
It's perfectly fine to be upset about the work that's being stopped, but some people in this thread are acting like everything is shutting down, which is ridiculous. And it's not like this stuff that is being worked on is insignificant, either.
And moves like this are seldom done in isolation.
The bluetooth settings panel GUI in gnome, not bluetooth support in general.