Hacker News new | past | comments | ask | show | jobs | submit login

Wow, what a conceited message.

If you want to support nouveau, then you can put the work in. You have no right to demand that others do work for you. Especially when they already have a functioning alternative solution in software rendering.




I am not demanding that they do work. I'm demanding that they do not deliberately sabotoge the nouveau driver. If they find the nouveau driver lacking, they should improve it, not sabatoge it. If they don't want to put the work in, then they should just leave well enough alone.


>I am not demanding that they do work.

Sure you are:

>If they find the nouveau driver lacking, they should improve it, not sabatoge it.

Not supporting a buggy driver is hardly "sabotaging it". It's not their job to make it work.

>If they don't want to put the work in, then they should just leave well enough alone.

And in doing so, their least-technical Linux users will suffer from sudden crashes that they don't understand. Now how does that help Linux?


Did you deliberately omit the end of that quote to make your point look better? I gave them an out: a demand with an out is not a demand.

>If they don't want to put the work in, then they should just leave well enough alone.

nouveau doesn't crash, but some cards may experience occasional glitches. That's something you need to take up with Ubuntu, not Chromium.


I'm demanding you not do the same in your own software, by this logic. You've done the same crap in the past, man: https://drewdevault.com/2017/10/26/Fuck-you-nvidia.html


Like I said to your other comment:

>The Nvidia driver does not "work" in my project. I have added no code which explicitly blacklists it, and the day Nvidia releases a driver which implements the required APIs it will work with no changes in my code.


But it's not well enough, people are filing bug reports with Chromium that are really bugs in noveau.


So Chromium should direct these users to the right place and close their ticket.


That is a "should" based on your feelings about Nvidia, not about what is the correct decision for users. They are falling back to software rendering when the GPU driver does not properly support the hardware acceleration. That's not uncommon, and it's certainly not the outrage you are trying to make it out to be here. Everybody gets it, you disagree with Nvidia's decision to not have open-source drivers. Not everyone else shares your views there, and it is not their obligation to support your views.


>That is a "should" based on your feelings about Nvidia, not about what is the correct decision for users.

No, it's not. If you encounter a bug in a piece of software, you should report it to the maintainers of that software. That's true even for, say, bugs found in the Nvidia proprietary driver. Expecting Chromium to fix it is expecting them to do more work, which is the exact thing others have railed on me for "expecting" from them (which I haven't, to be clear once again).


> If you encounter a bug in a piece of software, you should report it to the maintainers of that software.

I mean, sure. But that's not really the whole of it here. Chromium has encountered multiple bugs in a piece of software, and they decided they don't want to expend the resources to reproduce those bugs and deal with them. In the meantime, those bugs mean that the driver is not properly implementing the functionality for all users, and so Chromium has decided to simply not use that part of the driver. They aren't doing anything to the OS, they aren't bypassing the OS, they're just rendering on the CPU because the driver doesn't properly implement the hardware acceleration features. There is no obligation whatsoever to use software that you know doesn't work just because the OS ships it.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: