~/code/$LANGUAGE/$REPONAME

heard of it, but never used it. Works really well with termux though

This chorded keyboard

this is so games can render at half the framerate, but the fps counter doesn’t show it right? Yay? I guess…

extensions are not supported in gnome. gnome devs do not care in the slightest if they break them whenever.

yeah, so that means that it’s not incremental improvement on what we have that we need. That will get us nowhere. We need a (as yet unknown) completely different approach. Which is the opposite of incremental improvement.

because, having coded them myself, I am under no illusions as to their capabilities. They are not magic. “just” some matrix multiplications that generate a probability distribution for the next token, which is then randomly sampled.

the first advice the superintelligent ai would give: “power me down”

incremental improvements on a dead end, still gets you to the dead end.

no, it doesn’t work that way. The os does that with caching because it can release the memory should another user program ask for it. The browser just takes all of that memory. As far as the system is concerned, that memory is in use, not available.

it’s “my way or the highway” but for gui

they’re functionally extinct

with his death and the huge focus on trying to protect me from myself, I can see linux becoming even more restrictive than android. He’s one of the few sane ones left.

it’s still dog slow. As in 30 seconds to load the calndar slow.

nope

yeah I have a loan with them. otherwise I’d just switch

would be cool, but it won’t solve the whole problem. Apps like kde connect need accessib ility permissions to sync notifications with the desktop, for example. It won’t run if any unknown app has those. (like, my custom keyboard compiled from source)

firefox for most things. Chrome for my banking. The banking app refuses to run on my unrooted phone, because I have apps from f-droid installed, and I have a custom keybooard. And their site only works in chrome. Fuck hsbc

but in games, triple buffering is the norm

new features are fine. But first and foremost, is not breaking existing apps, or committing to porting them yourself. So if desktop apps need to do xyz, then wayland needs to support doing xyz. period. No ‘but that’s insecure’, no ‘but why would you want to do that’ (for setting a window icon or positioning the window ffs). Support existing applications. I’m not saying it should support x protocols. But it should offer replacement features for existing apps to be ported to. And it needs to be wayland. Because it’s already the case that certain functionality is implemented for gnome, or kde, with incompatible apis, to fill in the void left by wayland itself. If I want an app to work as I want it, consistently, everywhere? X, with all its warts, is my only choice.

As an example, the accessibility protocols. They’re good to have. Except they’re opt-in. So incompatible with existing apps. Some apps need to restrict access. They could declare that and make use of additional functionality. But no, choose a default that break everything instead.

The argument that apps just need to be ported also assumes the app is still maintained. Are you willing to do the work yourself if not? Probably not. You’re just the one looking down on people like me for wanting functionality in existing apps to be “not literally impossible to implement”