• 0 Posts
  • 29 Comments
Joined 16 days ago
cake
Cake day: June 11th, 2025

help-circle


  • ViatorOmnium@piefed.socialtoTechnology@lemmy.mlPNG is back!
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    2
    ·
    edit-2
    1 day ago

    Congratulations, your noob user is now using JPEG-XL. It’s not working on old devices, or any mainstream browser besides Safari. The less mature library also has a bug that allows for RCE and now everyone is running a cryptominer.

    Now you say, but webp is supported everywhere, so let’s go with that. Now the noob is using wepb for a bunch of rasterised vector graphics with 4 or 5 flat colors, and he’s wasting more disk space than before.

    So I repeat, if you need one size fits all, PNG is better, it works everywhere, and it’s even more efficient in cases where lossless graphics matter the most.


  • ViatorOmnium@piefed.socialtoTechnology@lemmy.mlPNG is back!
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    edit-2
    2 days ago

    The title is hyperbole. PNG is lagging behind modern lossless formats in terms of new features.
    This doesn’t mean it’s a bad format or that it shouldn’t be used. In fact, it should still be the default unless you need something it doesn’t support or really need to reduce file size.




  • ViatorOmnium@piefed.socialtoxkcd@lemmy.worldxkcd #3106: Farads
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    2 days ago

    They were all done by scientists or engineers.

    The meter was defined based on what they calculated as 1 millionth of the length of Paris’ meridian.

    The second was 1/86400 of a day, which makes sense with the angle/circle nomenclature on the clock.

    The gram was initially set to be the mass of 1cm³ of water at 4°C - which is why 1l of water ≈ 1kg.






  • You don’t even need to go at a low level. Lots of programmers forget that their applications are not running in a piece of paper in general.

    My team at work once had an app running Kubernetes and it had a memory leak, so its pod would get terminated every few hours. Since there were multiple pods, this had effectively no effect on the clients.

    The app in question was otherwise “done”, there were no new features needed, and we hadn’t seen another bug in years.

    When we transferred the ownership of the app to another team, they insisted on finding and fixing the memory leak. They spent almost one month to find the leak and refactor the app. The practical effect was none - in fact due to the normal pod scheduling they didn’t even buy that much lifetime to each individual pod.