Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by StavrosK on Thursday October 26, 2017 @10:11PM
(#15565113)
You know, I'm tired of being respectful and composed while others are walking all over me. If Nvidia doesn't care enough about the OS I bought their card for, fuck them, they suck, and I'm not buying another one of their cards again. I'm tired of being polite and not rocking the boat while I'm being taken advantage of.
[ Parent
| on HN ]
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by tomjakubowski on Thursday October 26, 2017 @10:17PM
(#15565146)
It's one thing to be a jerk to Nvidia, which seems justifiable. It's another thing to be a jerk to Nvidia users who may simply be unaware of the harm their GPU vendor has done.
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by kelnos on Friday October 27, 2017 @12:52AM
(#15565799)
I think it's perfectly understandable (and perhaps even useful) to lose your composure when you have a bunch of users who act entitled and complain about your (free) software being "broken", when it's the fault of their GPU vendor, who makes a ton of money off their user base.
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by djur on Friday October 27, 2017 @02:27AM
(#15566163)
It seems like a big problem for the Wayland ecosystem that support for a large category of video cards depends on one volunteer.
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by Qwertious on Friday October 27, 2017 @11:38AM
(#15569430)
>support for a large category of video cards depends on one volunteer.
How did you come to that conclusion? SirCmpwn doesn't maintain Wayland Nvidia support, just the Sway Compositor. If you want a Wayland compositor that supports Nvidia-proprietary, you can use GNOME.
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by djur on Friday October 27, 2017 @05:41PM
(#15572449)
The last time Sway came up as a topic at HN there was a conversation about whether a particular terminal manager was compatible with it yet. It seems to me that if the applications you use can have compatibility issues with the compositor you use, if you want to use an application your choice of compositors will be necessarily restrained to those that are compatible. And if compositors can be compatible or incompatible with particular hardware, that means that it's possible to have an application you want to use that is only compatible with compositors that are incompatible with your hardware.
What am I missing?
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by jorams on Friday October 27, 2017 @03:26AM
(#15566363)
It doesn't. Support for that large category of video cards depends on the manufacturer of those video cards.
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by StavrosK on Friday October 27, 2017 @12:21AM
(#15565692)
Is he being a jerk because he doesn't want to do a bunch of unpaid work? If your car manufacturer doesn't want to fix your broken car, am I a jerk for not doing it for them?
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by chongli on Friday October 27, 2017 @08:19AM
(#15567612)
No, but you are a jerk if you tell people who want to use your software to "fuck off" or buy a different car.
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by StavrosK on Friday October 27, 2017 @12:11PM
(#15569748)
Did he tell the people that? Or Nvidia? I must have missed it, if it was the former.
Re:Sway 1.0 is not going to support the Nvidia proprietary d...
by chongli on Friday October 27, 2017 @03:26PM
(#15571453)
And proprietary driver users have the gall to reward Nvidia for their behavior by giving them hundreds of dollars for their GPUs, then come to me and ask me to deal with their bullshit for free. Well, fuck you, too. Nvidia users are shitty consumers and I don’t even want them in my userbase.