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!!!
followed by “worcestershire sauce”
so, you have gigabytesper second of disk io, and the game relies on the couple of megaBITS of internet bandwidth most people have to stream textures? As opposed to downloading and installing them once as an update…
This does not pass the smell test.
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
no, there hasn’t. What games called ai has nothing to do with the generative ai bullshit of today
these actions already admit defeat
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.
well it is that one person causing issues
when in need, cry out for mommy!
the reason there were multiple skus is due to binning. So now they’re telling me that they have much better yields where they don’t need to bin, where most chips could be top tier, Making it cheaper for them and more expensive for anyone else?
m
usually the commits at the end of the day when I haven’t finished a task yet. It will be squashed and disappear eventually.
i have one, it’s not very good tbh. You would need to modify the software yourself to make it actually practical. some way to lock the screen, some way to vibrate more than one 250ms blip when an alarm is triggered, stuff like that.
“but all interdependent”
As it fucking should be! Yes the tools should be aware of each other. Yes the tools should be integrated. Yes, the tools should not have a bunch of different ways and formats for their config files.
These are not optional components of a system. I’d rather they work together, instead of needing yet another project in between as a kludge
there is the keepassxc-cli command. And it also supports ssh keys with integration with ssh-agent. So yeah
more like "move glacially and declare things as "will not support’ so technically we had nothing TO fix!"