

As a browser-supported web image format, the only real runaway advantage of JXL is the ability to losslessly reencode existing JPEG files, when the vast majority of image files that people already have are stored as JPEG “originals.”
But as an overall image format, JXL has a much more ambitious scope: much higher limits in the spec to resolution, bit depth, layers, etc., showing an intent to be used as a raw image capture format and printing format, not limited to screen resolutions and bit depth like AVIF is.
So if the original file gets stored as JXL, the workflow and pipeline of a JXL native process the whole way may have an advantage over exporting to a screen-friendly AVIF at the end of the process, while the original still gets stored as another format.



In what world is JavaScript considered buggier than Flash, either in the actual content in the wild or the client-side software rendering/running that content? It wasn’t true when Flash died and certainly isn’t true today.
Flash was a security nightmare, with all sorts of kludges patched on to try to deal with fundamental flaws in how it handled privileges. If you want to go back to the days where zero click exploits can take over your machine just from a browser visiting the wrong URL, leave the rest of us out of that vision.
Mm, and what makes you think that handing Adobe the keys to control everyone’s web experience would make it better?