How about the way Firefox complains about its DRM blobs crashing if you visit Dropbox, even if you have it set to disable all DRM functions and not run scripts? If you delete said faulty suspicious blobs, it automatically starts installing something without my consent. Mozilla deserves a creepy rating. Oh look, despite having telemetry disabled, after doing that test it's been writing new files under a folder named datareporting. The UI has been actively growing worse as well, featuring things like not telling you why it's concerned about SSL certificates, or why it redirects to https when explicitly instructed to use http.

It's a nice jest, but that's still what we're typically working with; pick a program, then use that program to create a document or open a recent one. The transition to work-centered rather than tool-centered interface mostly didn't happen. Side note, the oldest Windows installation I had didn't have a Program Manager; it started along with Excel, and opened no other windows.

Sure, it could. But that would require a coordinate remapping layer... like the at least three that already exist, for scaled windows ("non-HiDPI"), for multiple monitor layouts, and for the taskbar. And this is Windows they're talking about; let's not pretend they'll remove the APIs just because they're too lazy to make their phone ports use them. Besides which, all the other phone platforms now have APIs to avoid screen regions like the annoying camera notches. The excuse is the usual bullshit, made up on the spot.

"Open Source does not and never has meant anything other than being able to get the sources" - bullshit. Open Source has a very clear definition as a term, laid down in the Open Source Definition, in turn based on the Debian Free Software Guidelines, in turn based on the Free Software Foundation's Free Software. You can argue the term lacks legal protection, but stop spreading lies about what it means.

Wrong lesson. They're conflating separate things that may or may not all be crap. In particular, there is no "metaverse", and the incompetent software vendor here was "decentraland", which appears to be mostly scam. So Samsung spent advertising budget on something that doesn't work (not unusual), but happened to invite the press to report on how badly.

Both those places of course have existing codecs optimized for their use cases, such as ASTC and DSC. And deployment in hardware is what matters for them; they have no benefit from the byte orientation of QOI. QOI is does not satisfy either case: entirely serial breaks texture use, and 33% base expansion breaks the monitor case. Only perfectly flat horisontal runs of 3 or more pixels achieve lower than 8 bits per pixel.

I'm sure you could already tell, but it offers nothing for that use case. For instance, it doesn't support high bit depth or one channel per pixel (as caused by Bayer filters and the like). If you're looking for something that might compress more than your camera does, but preserves sensor data, DNG is more relevant. If you're looking for easier to parse, FITS.

No, because he had complete veto to shut down alterations that would eliminate pathologically poor cases for not feeling right to him. And now he's got the format 100% specified with meaningless padding and no version field. But the compression usually outperforms PPM!

It's not likely to see any use as an in-GPU texture compression format; it's 100% serial. No 2D lookups into the compressed image. You could make a sort of checkpoint by storing the 192-256 byte palette, 3-4 bytes of prior pixel, and offsets into image and compressed stream, but I don't think people would bother. Of course, decoding the format could be done by compute shaders, but wouldn't make much sense with less than some dozens of images to decode simultaneously; CPUs are often better at these tight loops.

The pixel to pixel diffing doesn't do anything to the runs, I think. It's basically 8-bit RGB, running 64-entry palette, RLE, and two variants of HAM. And a completely redundant end marker that only complicates things (by overlapping with the palette format). The main feature of the format is a codec that'll fit in L1 cache and uses simple byte based processing. By the way, who uses 8-bit linear?

Slashdot is regurgitating the marketspeak remarkably recently. We had denuvo's "protection" (not what that is or does), and now youtube's "intent" (that's spelled excuse over in sanity land).

They're just boiling the frog slowly. Or applying divide and conquer. Specifically to get these "I don't care" posts to hopefully outweigh those who do.

It's usually precisely about the content of the video, because those downvotes appear on the announcements. Such as, for instance, the announcement that Google decided to remove the Dislike button from YouTube to spare EA's fragile feelings.

These are not "protected", that's simply what denuvo's marketing team wants it called. They're sabotaged. Modified to fail. There's no upside - publishers, and thus customers, are literally paying to have the product destroyed.

Yes, I completely ignored a common constant in a comparison; why did you feel the need to bring it up? What does matter in relation to when the interrupt is posted is what work remains to be done, and what time has already passed. In the case of PS/2 vs USB, both weigh in favour of USB (aside from truly exotic devices like host controllers behind SPI).