![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
I’ve seen enough blurry software on Windows to know this is not quite true 😅
I’ve seen enough blurry software on Windows to know this is not quite true 😅
The way I see it, GTK is really a framework for building cross-platform GUI apps. Then handling display server compatibility makes perfect sense to me.
If this was meant to be a dig at Wayland, I’m pretty sure GTK also needs explicit and direct support for X11, Windows and MacOS. It just already exists.
I’m pretty sure Louis is just another recipient of FUTO’s funding, not “the” other partner to this dude.
I pressed Your Story and it worked just as well.
The flipside of this is that you as the BDFL are not in any way entitled to community contributions. If they decide to not like your furry board, they are free to fork the project, but splitting the development efforts could very well kill both projects, so sometimes it is better for the project to listen to the community.
Maybe the kernel version on Debian lacks hardware support fixes?
Love the part where he claims that if your users are authenticated, it’s not untrusted input. I mean, surely you trust all of your users to run any code on your server, right?
In pretty much any language I’ve used there is some standard for doc comments that would show up as mouseover text in the IDE.
PascalCase is standard in C#
Oh that is not just some person, that’s the CTO of "Open"AI when asked, if YT videos were used to train Sora.
I saw a comment from an nvidia dev somewhere that XWayland support is enough to resolve the flickering, but compositor support is needed for best performance.
Maybe if your games are Wayland native or you’re still running the 535 driver? I saw fbdev=1 as a workaround, but that made things very jello-y.
Desktop 1660S
Plasma 6 X11, 550 proprietary driver.
Yes, but that’s bound to be merged quickly, the protocol itself was the main holdup from what I understand.
Yes, for that to change we have to wait for the NVK based driver - nova.
Nouveau should have already been fine, this should fix the proprietary driver’s issues. AFAIK this is a core issue of the proprietary driver, so should affect all cards.
I tried Wayland on my 16xx series GPU, Electron apps were only annoying, but games were unplayable. The desktop itself and Wayland native apps worked fine, though.
Well, this is the root cause of this specific issue if you treat nvidia’s part of the stack as some barely changable black box (which is what it is right now). It’s not that I disagree open source drivers would be better, I just already own an nvidia GPU :/
Yeah, still gonna be a couple of months, but that is the last signifficant issue for me, fingers crossed.
No way they will ever be in sync.