Context: Even though Chromium has native support for AVIF, a very nice image format, Microsoft goes out of their way to remove it from Edge, which is a chromium fork. Jpeg XL (JXL) (not to be confused with Jpeg (JPG) or Jpeg 2000 (jpg2k) ) is another nice image format, which, IIRC, is only supported in Firefox.
When it comes to pronunciations of obscure computer acronyms, my favourite is btrfs (the filesystem), because I’ve never seen anyone advocate for any specific pronunciation, not even the devs/official documentation. Bee Tree Eff Ess? Bee Tee Arr Eff Ess? Butter Eff Ess? Better Eff Ess? Whatever bloats your goat!
Someone needs to make a website that uses jxl heavily then contact a journalist about a weird website they found that opens 10x faster in safari vs chrome
I said it in another comment, but I’m actually working on a website right now, which happens to lazy-load a lot of images with Javascript. I think I’ll store all the images in webp, avif, and JXL formats, and have the javascript code automatically load the one which is supported by the browser. Hopefully if it takes off, it can promote support for modern image formats!
Do you write postscript by hand? I once got the change to take a postscript programming class, but sadly I didn’t (I wish I did tho). How does it compare with SVG? I know SVG has a lot of limitations (for example, you can’t change the color of a shape filled with a pattern), so I guess eps’ turing completeness lets you overcome things like that, since you can just program in whatever functionality you need?
WebP cause small size, can be transparent, can be animated, can use either loseless and lossy compression. Also it pisses of many people which is funny to me.
Add comment