I’ve had a similar case in my department, and the guy couldn’t even be let go because he’s family of some important man in the company.

You’re totally allowed to blame him. He had a choice and he decided not to do what it takes.

I’m not even sure why you’d allocate only 20% to the dude.

The Jr Dev is worse at the job than AI. We get the cheaper AI to oversee the Jr Dev

deleted by creator

Written in PHP

Makes sense. Thanks for your knowledgeable response!

Thanks for the iPhone hint! Do you happen to know or have an idea why Apple chose to offer JPEG XL only as ProRaw format? For “normal” photo capture, they still use HEIC only.

For all I know, the 4K thing is misinformation.

Oh wow, Mozilla reconsidered JXL support. They said no after Google pulled out, but “now” (well, since an entire year ago) they’re at half a yes again.

https://github.com/mozilla/standards-positions/pull/1064

https://github.com/libjxl/jxl-rs

Edit: neat, it has recently landed in the Firefox codebase: https://phabricator.services.mozilla.com/D263393

Still behind a flag, but Apple seems to have decided for JXL, and Mozilla seems to have gotten their mind made up and following suit.

Glad to hear JPEG-XL is still making its way. It deserves to become the most widespread image format.

Regarding web usage after the Google situation:

I do disagree about AV1. Its AVIF image format spinoff is very good. Often better quality or smaller file size than webp, and has browser support as good as webp nowadays. And of course,

I work on a lot of web projects, and I used to serve webp and AVIF for a while (based on the browser’s HTTP Accept header). Recently, I decommissioned all webp handling and serving code.

See https://caniuse.com/?search=image+format. You can serve an AVIF for every requested JPEG or PNG file.

Forget webp. AVIF is the image format.

(Especially after Google killed JPEG-XL.)