308
Here comes a new JPEG challenger (programming.dev)
submitted 1 year ago by to c/programmer_humor@programming.dev
51 comments fedilink hide all child comments
 

For anyone curious - https://flif.info/

EDIT: am a dumbass, JPGXL extends from FLIF

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 year ago (5 children)

Maybe if web pages weren't also loading like 25mb of javascript it wouldn't be such a big deal to load 5mb of uncompressed images.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 4 points 1 year ago (4 children)

    Lol uncompressed images could easily exceed 25 MB for a single image. I've seen some egregious cases of js sizes but I've never seen 25 MB

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] [S] 3 points 1 year ago (2 children)

    I've once worked on a project where the compressed .JS shit was ~27MB. Uncompressed it was ~600MB.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 year ago* (1 child)

    That was a fucking webpage...?. I am honestly wondering how a browser could even handle that much code...

    I'm gonna say I've seen 5 MB uncompressed before but not much more than that if at all. Imo 1 MB is borderline unacceptable for the typical web page.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 3 points 1 year ago

    It was an internal system for keep track of several projects. That still used 600MB more javascript than it actually needed for what it ended up doing anyway; purely static pages could've done everything needed, except maybe the animated graphics, but the create/edit forms were a fucking pain to even test, because not a single fucking element had an id and the date picker was literally impossible to target with Selenium

  • permalink
  • fedilink
  • source
  • parent