Submitted 2 months ago by Toes@ani.social to technology@beehaw.org
https://www.w3.org/TR/2025/REC-png-3-20250624/
Not seeing how this would affect uptake. Lossless is great for production images, but standard JPEG will do (at low compression) for most Web use cases. Until OS developers coalesce around PNG as a standard (Windows has for screenshots), this is that old standards xkcd.
Alpha channels are nice and all, but how many end users A) have a need for that and B) understand the underlying concept, let alone implementation?
Alpha channels are critical. The ability to have images have transparency in them is much more useful than you believe it is. Many end users have a need for it, more than they know they do; so this argument really isn’t doing much for your stance supporting PNG. Similarly PNG has supported alpha channels for quite a while.
For production, yes. What percentage of images produced are for production, though? I know damn well how important alpha channels are, but for posting something on social media, which is orders of magnitude more output than image creation within the context of a larger presentation, no one cares.
The vast majority of people aren’t graphic artists. That you and I know what alpha channels are has no bearing on daily use by the masses.
I’ll agree for those use cases, but not everyone is making icons, stickers and emoji.
dormedas@lemmy.dormedas.com 2 months ago
I said in a previous article that this is great, but we should be adopting JPEG-XL as it is current and can now compress pixel-perfect / lossless images better than old PNG. IIRC this revision of the spec doesn’t improve compression yet but it’s coming.
skullgiver@popplesburger.hilciferous.nl 2 months ago
dormedas@lemmy.dormedas.com 2 months ago
JPEG-XL is only really in limbo because Google chose to kill it in Chrome in favor of AVIF. Had that not happened, there would have been far more demand for it to be properly implemented everywhere. Sucks, but you’re right that we’ll have to stick with AVIF/HEIG/WebP.