Actually light does experience time in its own frame of reference. For somebody observing(us in this example) the light or any object that moves at the speed of light in vacuum, it would seem that object is not experiencing time at all, that is, if there was clock on the object and we tried to measure the time that clock reads, it would give the same number as the result of the reading irrespective of when or where we measure it in our frame of reference.
I’m not sure if mobile AMD users have to do the same
No we don’t. Mesa and the kernel automatically decide to use the dGPU for intensive tasks. It is only on rare ocassions that I have to use the DRI_PRIME=1 to force the use of the dGPU. It has been months since I last did it
But if you need the help of his code and products, then you should begrudging acknowledge that he is not an idiot. If you truly believe that he is an idiot, you should find a solution to your problem without pulseaudio or systemd because if not you are just an hypocrite.
It has been some time since I tried out Nobara so I might be wrong. I just remember that Nobara page lists having amf encoder support out of the box as a feature
While I don’t know how, I do know that there is a way to have mesa for most things while having AMF encoder for encoding. Nobara has this set up out of the box so there is some way. Maybe you could search for it using a search engine
You most probably won’t need to donate to cancer research. It is already being funded in the hope that the medicines developed will bring in the dough once they are ready
In the meantime please share that these issues exist on nvidia forums. Issues caused by nvidia drivrers shouldn’t come under the purview of the kde devs.
Yeah I forgot about monitor support. Guess that’s pretty important. But is pixel shifting gnome’s responsibility or should that be done through monitor firmware so that it’s OS agnostic¿?
I am also sure that it will land as well. As a gnome user I hope it lands sooner than later. I am just frustrated because the pursuit of perfection is keeping us from having a better experience now. It’s the calculator on iPad situation. Just because the perfect solution has not been found yet does not mean there should be no implemented solution at all.
These discussions took place several years ago if I remember correctly. The problem seems to be that cursor seems to want to refresh at a different rate than the content in screen and the people at gnome want the cursor to not feel choppy by being refreshed at the vrr determined refresh rate