![](/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
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!!!
true, but totally irrelevant. Gps has nothing to do with sim cards
if i park in the shade, and therefore don’t have to turn on the ac as soon as I get in, I think that would be about the same, savings wise.
you mean it doesn’t work when the device is turned off? weird! /s
sometimes, a script needs to be edited in a plain text editor, without having access to an lsp or any other dev tools.
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
atmega328. It’s not the most powerful chip, but it’s what’s on most arduinos, which is what got me into electronics in the first place.
deleted by creator
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! "
that’s not how asymptotes work.
but they have a lot more disadvantages for most scenarios (if you’re not a faang scale company, you probably don’t need them)
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.
it’s all the same web 2.0 bullshit, but for anything with crypto in its name
it’s opt-in, per app. Meaning unless old apps are patched and recompiled, they will be inaccessible.