![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
it means that you have to manually reposition every single window, every single time. for any and all apps, by design
it means that you have to manually reposition every single window, every single time. for any and all apps, by design
note: on most computers, it worked the opposite to how one would think. Turning it on slowed your cpu to around 33 MHz
you know that the confidence value is generated by the ai itself right? So it could still spew out bullshit with high confidence. The confidence score doesn’t really help much
you mean it doesn’t work when the device is turned off? weird! /s
rule of thumb: multiply by 4 to convert from years to quarters. You’re welcome.
no, the truth is it’s impossible even then. If the result involves randomness at its most fundamental level, then it’s not reliable whatever you do.
suffers from all the same problems features. It’s inherent to the tech itself.
it never knows what it’s saying
not stole. Were given.
If code is law, then they just found the right way to ask. And the code gave the money to them, because they asked nicely.
and how, pray tell, do you think contactless cards work?
so your main complaints are that its most basic usecase sucks, but it works quite well. which is it?
on android, it is the only app I have found that’s not compatible with my keyboard. You read that right. How the hell do you fuck that up?
sometimes it takes minutes to load the calendar, only to still fail
because of ai stuff. For these kinds of things, they are perfectly happy to advertise unprecedented 99% accuracy rates, when in reality, non ai tools are held to much higher standard (mainly that they are expected to work). If the code I wrote had a consistent, perpetual 1% failure rate (even after fixing it, multiple times), I’d have been fired long ago.
that’s not how asymptotes work.
by issues I mean breaking existing users’ workflow, possibly literally locking them out (I personally use a yubikey with my keepass db, for example).
There is a very simple solution he could have done: not rename the existing package. Just give his fork a new name. That’s it, everybody is happy.
So yes, he is the one causing issues. Because the issue isn’t in the features he removed, but by breaking the users’expectation that the package they installed yesterday, is the same one they’re updating today.
this has “draw the rest of the fucking owl” vibes to it. especially step 3
well it is that one person causing issues
when in need, cry out for mommy!
it’s opt-in, per app. Meaning unless old apps are patched and recompiled, they will be inaccessible.