• 20 Posts
  • 250 Comments
Joined 1 year ago
cake
Cake day: February 17th, 2024

help-circle







  • Casual reminder, Sony and Intel tried to tether Blu-ray discs to SGX DRM, which was killed just a few years after they introduced the standard, rendering all of your SGX DRM Blu-rays unplayable on PC. They disabled it so quickly, because people could use Intel SGX DRM for remote code execution in your machine, below the operating system and kernel level.

    Also, if you have one of the CPUs which still has SGX DRM, congratulations, you have a hardware Trojan! Digital restrictions management is a cancer because look at what it does in reality, vs. what they say. Who came up with this?






  • Yes, and I agree with you. People should have choice of what format they use because different people have different needs.

    I don’t hate AVIF inherently for its technology. I hate it for what it stands for. Namely, megacorporation Culture. One rogue manager has their feelings hurt and everyone bends over to accommodate them. Google has a fully SIMDified Rust decoder for JPEG XL that is fully standard compliant. But it doesn’t go into Chrome, because everyone just parrots the one guy that once made up some lie about it not “having public interest”. Best example is Google Interop 2025 not taking in JPEG XL. Literally every graphics software on the planet supports it, as well as multiple newspapers and CDNs want to use it, and I don’t mean the newspaper next door, I mean newspapers like The Guardian and CDNs like cloudflare. You can call Apple a lot, but the jpeg-xl implementation is some objective good for computing, Microsoft is slowly but surely rolling out support in Windows as well. Literally the only missing link in the chain is the Google Chrome browser, because it’s a monopoly.

    And with that, I refuse to use it. Because if I were to use it and pump the numbers for AVIF, I would reinforce the blockade. Therefore I just can’t, even though the technology is very useful and that’s just another side of the Google Monopoly.




  • Agreed, I once knew a few people who kept them on indoors and their floors looked as appetising as you’d imagine, especially the carpets.

    Maybe it’s a way of accelerating natural selection. If you survive having direct skin contact with the carpet, you’d be the chosen one or something like that.



  • ZkhqrD5o@lemmy.worldtoLemmy Shitpost@lemmy.worldMy latest hyperfixation
    link
    fedilink
    arrow-up
    86
    arrow-down
    1
    ·
    edit-2
    5 days ago

    I’ll take any excuse I can get to dump my perspective here. I love AV1 for video and I hate AVIF with a passion. Every video that I create is delivered in AV1, because it is incredibly useful, versatile and extremely powerful. Right tool for the right job.

    Not that there’s anything inherently wrong with AVIF other than it tries to force a video codec into something that is that it is not meant for, namely a still image codec. I hate the drama around it that Google has created. Because the stupid cunt that created AVIF is an emotional slime, he tried to block JPGXL, a competitor for AVIF, from having official support in the Google Chrome browser. And because Google Chrome is a monopoly in the browser market, CDNs and other people who’d like to use JPGXL, since it has significantly better all around features for still images, cannot use it now.

    Features of JPEG-XL:

    • better still image compression than AVIF
    • lossless JPEG transcoding
    • progressive image loading
    • universally usable from capture to delivery
    • layer support with 4,099 channels
    • CMYK Compatible
    • 32 bits per channel
    • no limitations on image size or colour precision

    And all of that is thrown away because one bastard has his feelings hurt by user choice.

    Thank you for listening to my useless TED Talk.

    Edit: While I sound extremely black-pilled about this, because monopolies are bad, the positive thing is that it’s gaining traction, finally. Apple has fully embraced it some time ago. Now Microsoft Windows supports it natively as well. Literally the only missing piece is the browser. While Safari, thanks to Apple, - never thought I’d say that - now supports JPEG XL natively, Firefox and Google Chrome do not as of right now. So the browser is literally the last missing link for full native support. Also, I’d wish for the people at Mozilla to stop letting themselves be cucked by Google. But JPEG XL is around the corner, luckily, because sooner or later they will be forced to use the modern format to stay competitive, like Samsung already does for their phone cameras. Still salty about the attempt, though.