2026-09-16 03:52 UTC
@gianni@disobey.net @wbrowar@hachyderm.io @nhoizey@mamot.fr All those "should a browser support rendering big files" questions get murky anyway. Should it render a 10 MB PNG, a huge SVG with thousands of elements, a 50 MB PDF, a 100 MB audio file, a 200+ MB video? All these could be rendered server-side to some smaller preview.
But ultimately the support comes down to "do we already support the format anyway?" and/or "how much demand is there?" I remember when audio, video and PDF rendering were not the browser's problem and needed plugins or downloading a file to open it with other software; this changed because of demand, not because PDFs, AAC and say VP8 are magically tiny files smaller than a JPEG thumbnail.
Replies (2)
-
@gianni@disobey.net 2026-09-16 04:28
@fvsch@hachyderm.io @wbrowar@hachyderm.io @nhoizey@mamot.fr everything you’re saying makes sense, I’m just not compelled we need a new image codec for any of it; especially if the cited use case is massive camera files.
-
@fvsch@hachyderm.io 2026-09-16 04:06
@gianni@disobey.net @wbrowar@hachyderm.io @nhoizey@mamot.fr I wonder what demand Mozilla and Google are seeing or anticipating for JXL. Is it just spam in their bug tracker and votes on Interop? Or is there demand from some publishers (say, Canva)? Or possible inclusion of JXL in PDF?