the guy who invented the segway is still alive. The guy who bought his company later drove off a cliff, though it is suspected he had a heart attack while driving
the guy who invented the segway is still alive. The guy who bought his company later drove off a cliff, though it is suspected he had a heart attack while driving
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.
they aren’t. The only difference is that the state transition table is so unimaginably gargantuan thit we can only generate an approximation of a tiny slice of it, instead of it being literally a table
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
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.
I mean with the “move fast and break things” mentality of most companies nowadays, I’d say he was spot-on
so the creator of gif himself was deliberately transgressive?
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”
I do not care about security risks. If something made its way onto my system, I’ve already lost. I just want one implementation of something that gets the job done. And by “gets the job done” I mean it allows us to do things better, not disallow us from even having the option to do things because someone had their tinfoil hat on too tight. Ffs you can’t even set your window icon. I don’t care if kde has implemented that feature. If I use that, I’d be supporting kde, not wayland. It won’t work on other des and so the maintenance burden increases drastically.
“almost” being the key word there.
xwayland cannot ever be removed, because wayland, by design, will not have enough functionality to replace it. So one can either support X desktop environments with their own individual bugs, or one X implementation that has the needed features and works consistently for all DEs
because for most of them, there is nothing to port them to. Wayland is incomplete… by design.
~/code/$LANGUAGE/$REPONAME