4 ms·
You phrase that as though there is a real choice here. There is not. The open source community has had experience with how to interact with closed source driver
by roenxi 8y ago
You phrase that as though there is a real choice here. There is not. The open source community has had experience with how to interact with closed source drivers since the Linux 0.01 in 1991 and that experience screams "don't do it". Xorg has been a technical disaster for more than a decade; I have sympathy for the people who want to use Nvidia cards, but they are going to have to use X.org and like it anyway because that is all Nvidia supports.
Attempting to run a project based on the opinions of a group of Nvidia devs who (1) don't care about your project and (2) don't care about your goals is technical madness. It took the kernel more than a decade of stubbornness before all the other device driver writers caved and supported decent design. As far as I recall Nvidia is literally the last major device driver who refuses to play ball with open source. If Nvidia users can't use Wayland for driver reasons that is because of Nvidia's choices and there isn't anything the Wayland devs can do without repeating all the mistakes of X.org.
If it takes another decade before Nvidia caves and behaves like a good corporate citizen then that is a decade well spent by the Wayland devs. Long term maintainability will eventually trump short term user issues; just like it did for wifi et al. It is unfortunate Nvidia is making their user's lives hard, but the writing has been on the wall since AMD started open sourcing their driver stack in the 2008 era.
- saulrh 8y agoThe problem here isn't the interaction with the nvidia devs. Like you said, flatly refusing to work with their binary drivers is WAI. The problem here is the interaction with wayland's users and potential users. It is perfectly possible to post exactly what you said here, along with other useful information about why and how people should expect their nvidia cards to fail to behave, instead of saying things like "users are idiots and will blame us no matter what we do". Communicating with users better will not only reduce anger at Wayland, accelerate its adoption, and improve its quality, it'll direct at least some of that anger at nvidia thereby directly enhancing the no-cooperation strategy you describe here.
- pjmlp 8y agoAndroid and ChromeOS show it is possible to have it other way when FOSS religion doesn't stand in the way.
- vetinari 8y agoAndroid and ChromeOS show how any device support is abandoned as soon as it ships. My phone is running kernel 3.10 (the same as rhel7, except without backported fixes), and it isn't going to get anything newer.
- pjmlp 8y agoAMD also decided to abandon my Radeon, dropping DX11 class features and video hardware decoding on their rebooted open source driver, so where is the difference?
- xorcist 8y agoAndroid shows exactly what that would look like: You get a blob-like kernel/stdlib/driver package from your vendor, then build your operating system around that and never speak about it again because it's brittle mess of good enough. The only reason Google and a few big players can ever ship updates is by playing hard with those vendors, and negotiating upgrade paths in advance. Nobody is interested in doing that for the desktop.
- pjmlp 8y agoExactly the example of the FOSS religion I was talking about. Game devs just want to put shinny pixels on the screen, no one cares if it is a blob or not. AMD is open source and there is hardly any advantage, X routinely crashs, doesn't provide support for the GPUs that were dropped from the rebooted driver, being stuck with fewer capabilities than fxgl. Hollywood studios are quite happy with NVidia drivers.