10 Reasons Linux Gamers Might Want To Pass On The NVIDIA RTX 20 Series

[Weasel]

I do not know why you talk about open source libraries here, my point is that I do not want binary only library stuff on my system, let alone kernel space at all.

What has that to do with you quoting me then?

The context was this (which I replied to from pal666): He said "it is hard to develop without sources", which is just bullshit.

What has that to do with what you want on your system again? In fact, cross-developing is a thing to begin with, you can even write Windows software from Linux, even though the "target" is closed source so you only have the interface and SDKs.

[rene]

Who the hell is "we"? I don't know how you code, but when I code against a system call on Linux, I read its interface man page, I don't go and look at its source code, that's just dumb and a waste of time. Not to mention that the source code can change, but what's documented in the interface is stable.

Of course, in many cases having open source is a great thing and to read such code, but not when just targeting a well-documented interface, which was the point. You need it when you want ideas and algorithms and to see how something reacts. You don't need it to interface with something. God damn.

I do not know why you talk about open source libraries here, my point is that I do not want binary only library stuff on my system, let alone kernel space at all. If you'd wanted this then you could also just use macOS and Windows. The point of Linux is open source, and not having binary blobs in the kernel, libraries, or whatever. Btw. this prevents innovation, as newcomers can not just get the existing hardware working on their new systems, such as BeOS^W Haiku, DragonflyBSD, QNX, you name it. https://www.openbsd.org/lyrics.html#39

[Weasel]

If we wanted to interface with binary only SDKs we would have stayed on Windows, but alas, we want a stable, secure, reviewable, and re-architectable system.

Who the hell is "we"? I don't know how you code, but when I code against a system call on Linux, I read its interface man page, I don't go and look at its source code, that's just dumb and a waste of time. Not to mention that the source code can change, but what's documented in the interface is stable.

Of course, in many cases having open source is a great thing and to read such code, but not when just targeting a well-documented interface, which was the point. You need it when you want ideas and algorithms and to see how something reacts. You don't need it to interface with something. God damn.

[rene]

It doesn't really take away from your point, but I think Tesla lock down their cars quite a bit.

thats why I don't buy a Tesla ;-)

[cybertraveler]

If we wanted to interface with binary only SDKs we would have stayed on Windows, but alas, we want a stable, secure, reviewable, and re-architectable system. PS: Did NVidia release a driver for BeOS^W Haiku yet? Oh, I see, not their responsibility, target, focus? Yeah, I would not even wanted it, but with an open SPEC everyone could just tinker around however they feel like it on a rainy^W or sunny afternoon. When was the last time your car vendor locked down your car so much you could not go to an independent service, tune or swap the engine as you please? Yes – another famous car analogy ;-)!

It doesn't really take away from your point, but I think Tesla lock down their cars quite a bit.

[rene]

No you only need the interface or SDK "to develop" for something. Maybe stop speaking about crap you've no clue of.

If we wanted to interface with binary only SDKs we would have stayed on Windows, but alas, we want a stable, secure, reviewable, and re-architectable system. PS: Did NVidia release a driver for BeOS^W Haiku yet? Oh, I see, not their responsibility, target, focus? Yeah, I would not even wanted it, but with an open SPEC everyone could just tinker around however they feel like it on a rainy^W or sunny afternoon. When was the last time your car vendor locked down your car so much you could not go to an independent service, tune or swap the engine as you please? Yes – another famous car analogy ;-)!

[Weasel]

i didn't say everyone, we were discussing developers. it is hard to develop without sources

No you only need the interface or SDK "to develop" for something. Maybe stop speaking about crap you've no clue of.

[Weasel]

lol. i've accidentally lived in wayland session few weeks without realizing it. i thought that i broke something in vdpau land because vdpau was not working (it's x11 only, but that's not protocol's fault. vpdau is nvidia's stuff btw - see pattern ?)

As if I care what casual crap you use your PC for.

sway is an implementation of protocol. you need implementation no matter what is in protocol

It adds more features than just what's in the protocol, and that's the problem. They just want to steal the spotlight. Then it wouldn't have to exist since there's other compositors already, no need for extra libraries.

[rene]

Let me summarize your argument here because I cannot comment on your blog page. You asked Nvidia to give you the register specifications for their product, because ... you had been doing Linux kernel, driver, libraries, gcc, development since 1998. You actually thought that because of your "qualifications" Nvidia should have done that. Amazing. Then they said no ofcourse (please use the APIs and platforms that we support and leave all the register banging to our driver - FYI this is called encapsulation) thank you very much funny little man. I was right you are utterly clueless about serious development practices and collaboration between organizations in the real world.

🐟 Either you are just a braindead troll, or something is seriously wrong with you. In the later case I suggest visiting a Dr. Why do you even hang in a Linux forum? Just to get on Linux developers nerves? 🐟 Maybe you better join the MSN, ..!

[zoomblab]

Just for clueless trumps like you, I wrote a blog post – wanted to do for some time, now it is out: https://rene.rebe.de/2018-09-07/resi...lly-for-linux/ just if my G5/PowerPC point & use-case was not enough, ..! But oh well, I have totally no clue nor insight, ..:-/ https://t2sde.org

Let me summarize your argument here because I cannot comment on your blog page. You asked Nvidia to give you the register specifications for their product, because ... you had been doing Linux kernel, driver, libraries, gcc, development since 1998. You actually thought that because of your "qualifications" Nvidia should have done that. Amazing. Then they said no ofcourse (please use the APIs and platforms that we support and leave all the register banging to our driver - FYI this is called encapsulation) thank you very much funny little man. I was right you are utterly clueless about serious development practices and collaboration between organizations in the real world.