![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/zXqqvadAXQ.png)
more like "move glacially and declare things as "will not support’ so technically we had nothing TO fix!"
more like "move glacially and declare things as "will not support’ so technically we had nothing TO fix!"
it’s when devs of a graphics stack just suddenly feel the need to protect your own computer from itself, so they say fuck you to any features that they deem “insecure”, including accessibility features (they will claim they fixed this, but it’s opt-in per app. old apps will just be completely unusable for some people with special needs.)
But they eliminated tearing on the desktop! woo!!!
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
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.
celsius or fahrenheit?
the results are random therefore the dataset is useless.
tell that to any fpga toolchain
you released it under a non open source license. So very clearly: no it is not
it is only open source if i can build it myself. Which I can’t if you just give me the weights.
The weights are the “compiled” version of the dataset. It’s the dataset that’s the source, not the weights
it never knows what it’s saying
3 monitors, any day. I already hate 16:9 over 4:3
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?
cue the "one of our devs slipped and fell on a keyboard, completely coincidentally hitting all the right keys in the right order to code this. Completely coincidentally! "
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.
note: on most computers, it worked the opposite to how one would think. Turning it on slowed your cpu to around 33 MHz