News for hackers. Stuff that matters.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by yongjik on Thursday October 26, 2017 @09:40PM (#15564924)
From TFA:

> When people complain to me about the lack of Nvidia support in Sway, I get really pissed off. It is not my fucking problem to support Nvidia, it’s Nvidia’s fucking problem to support me. Even Broadcom, fucking Broadcom, supports the appropriate kernel APIs. 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. Choose hardware that supports your software, not the other way around.

Now, contrast with [1]:

> I first heard about this from one of the developers of the hit game SimCity, who told me that there was a critical bug in his application: it used memory right after freeing it, a major no-no that happened to work OK on DOS but would not work under Windows where memory that is freed is likely to be snatched up by another running application right away. The testers on the Windows team were going through various popular applications, testing them to make sure they worked OK, but SimCity kept crashing. They reported this to the Windows developers, who disassembled SimCity, stepped through it in a debugger, found the bug, and added special code that checked if SimCity was running, and if it did, ran the memory allocator in a special mode in which you could still use memory after freeing it.

[1] https://www.joelonsoftware.com/2004/06/13/how-microsoft-lost...

Re:Sway 1.0 is not going to support the Nvidia proprietary d... by Sir_Cmpwn on Thursday October 26, 2017 @09:42PM (#15564939)
Author here. You know Microsoft engineers were paid 6 figure salaries to work on that, right? I have a Patreon where I make enough money to recoup half of the costs of maintaining these projects.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by yongjik on Thursday October 26, 2017 @09:55PM (#15565025)
"I'm doing it as volunteer" is not an excuse for being unprofessional.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by StavrosK on Thursday October 26, 2017 @10:10PM (#15565101)
I would expect professionalism from someone I'm paying. I don't expect professionalism from someone who's basically giving me free stuff.

If someone offers to paint your fence for free, and your fence has some really nasty angles at some point, would you say the volunteer was unprofessional if they said "yeah I'm not going to paint that part"?

Re:Sway 1.0 is not going to support the Nvidia proprietary d... by esaym on Thursday October 26, 2017 @11:40PM (#15565545)
There is a certain level of just being a decent human being though. If I am an unpaid pastor of a church, should I give crappy sermons?
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by icebraining on Friday October 27, 2017 @05:11AM (#15566803)
In what way is Sir_Cmpwn's work "crappy"?

Guess what: if you ask your local Catholic priest to give sermons for your weird sect, he'll probably refuse too. And if lots of people keep insisting, it's not surprising he gets annoyed.

Re:Sway 1.0 is not going to support the Nvidia proprietary d... by yongjik on Friday October 27, 2017 @12:33AM (#15565735)
> I don't expect professionalism from someone who's basically giving me free stuff.

Ironically, that's exactly what Microsoft has been saying about Linux during those bad old days. Linux was successful because its developers didn't say "If you want to talk to a professional, buy something else."

I'm not saying an OSS developer should bend over and take abuse from users. But I believe there's a line between that and calling users "entitled brats" just because they use vendor-supplied drivers for their $500 cards.

Re:Sway 1.0 is not going to support the Nvidia proprietary d... by kelnos on Friday October 27, 2017 @12:50AM (#15565793)
No, he's calling his users "entitled brats" because they come into his channel and bitch and whine and demand he support them... for free.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by sgift on Friday October 27, 2017 @04:35AM (#15566651)
After the post and all his comments here I have my doubts that "bitch and whine" isn't actually "people ask me questions, I realize that they use Nvidia so their questions are by definition whining and bitching."
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by kelnos on Monday October 30, 2017 @06:07PM (#15589382)
You're certainly entitled to your opinion, but as someone who has actually maintained widely-used open source software, you'd likely be shocked at the level of entitlement I've encountered among OSS users.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by Qwertious on Friday October 27, 2017 @11:35AM (#15569400)
>Ironically, that's exactly what Microsoft has been saying about Linux during those bad old days. Linux was successful because its developers didn't say "If you want to talk to a professional, buy something else."

Except, the reason why Microsoft was wrong was that Red Hat existed. If you're running CentOS or Arch Linux or something, you really are fucked as a business. The key distinction here is that SirCmpwn is not a Red Hat dev, so should not be expected to meet the responsibilities of one.

Re:Sway 1.0 is not going to support the Nvidia proprietary d... by jcelerier on Friday October 27, 2017 @05:10AM (#15566800)
> I don't expect professionalism from someone who's basically giving me free stuff.

That's weird. Professionalism should be expected in all aspects of life. That's basic human respect.

Re:Sway 1.0 is not going to support the Nvidia proprietary d... by mikeash on Thursday October 26, 2017 @09:56PM (#15565029)
It is an excellent excuse for not devoting a huge amount of time and effort to fixing other people's stuff, though.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by Avshalom on Thursday October 26, 2017 @10:00PM (#15565050)
Not being paid for something is pretty much the literal definition of not being a professional.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by shmerl on Thursday October 26, 2017 @10:06PM (#15565080)
So you define volunteers as unprofessional by definition. That doens't sound right.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by Avshalom on Thursday October 26, 2017 @10:17PM (#15565140)
It is an off handed snark based on the not terribly subtle difference between "not a professional" and "unprofessional" which I feel perfectly validated making because Sway isn't a volunteer effort, it is an (un|insufficiently) paid effort, which is also not a very subtle difference.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by platinumrad on Thursday October 26, 2017 @09:58PM (#15565042)
Wasn't aware that disassembling other people's broken code in your own free time for their benefit was a key part of being """professional""".
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by chongli on Thursday October 26, 2017 @10:05PM (#15565072)
It isn't, but being a professional does suggest a basic level of respectfulness and composure. Going on a profanity-laden rant against a popular vendor and its users would seem to fall short of that.

On the other hand, a polite refusal to support EGLStreams may not have moved the needle enough to reach the front page of HN.

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.
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.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by wizbright on Thursday October 26, 2017 @10:14PM (#15565125)
SirCmpwn has a patreon. If you feel the need to help pay for him to develop a feature, you can. He can't maintain everything especially with the hardware working against him.

https://www.patreon.com/sircmpwn

Re:Sway 1.0 is not going to support the Nvidia proprietary d... by Derbasti on Friday October 27, 2017 @01:33AM (#15565945)
By that logic, I hope you cook only professional-grade food, and exercise like a professional athlete.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by ww520 on Thursday October 26, 2017 @10:48PM (#15565309)
That is some heavy BS logic.
Re:Sway 1.0 is not going to support the Nvidia proprietary d... by sprayk on Friday October 27, 2017 @12:16PM (#15569797)
this pattern of a platform dev special casing in their product for specific games still goes on today, but by Nvidia and AMD. When a new, giant game comes out, nine times out of ten the developers did some depraved stuff with directx/opengl that worked on whatever few cards they actually tested on. When the game gets released (or sometimes as a prerelease), Nvidia/AMD will go through what the new game does on their hardware, find any hackey/unexpected/bad call to their drivers made by the game, fix these problems in their drivers for these specific games, and release new drivers a few days after the game releases. You could buy a $60 game on launch that is broken from the AAA developer and have to wait days to weeks on a patch from Nvidia to play with any playable framereate/graphics in general.

I believe I read about this phenomenon here https://www.gamedev.net/forums/topic/666419-what-are-your-op...

Re:Sway 1.0 is not going to support the Nvidia proprietary d... by mikeash on Thursday October 26, 2017 @09:56PM (#15565026)