alwillis

Joined 16 years ago

Karma
9,013
Submissions
3,414
Member since
Sep 24
[ my public key: https://keybase.io/alwillis; my proof: https://keybase.io/alwillis/sigs/RYx1MNFlb1gNi9psXIHPpAttI8VT-rNbYRWt-Ex0gqo ]
View on Hacker News

Recent submissions

Comment · 5 days ago
Comment · 5 days ago
> I suspect they are going to drip feed it through their products as a cheap spec bump (vs adding extra RAM or storage).

The iPhone sells way more units than the iPad, so it makes sense that it's not a feature for the iPad mini yet.

Comment · 10 days ago
Comment · 14 days ago
Comment · 16 days ago
Comment · 17 days ago
Comment · 17 days ago
Comment · 19 days ago
> Even the biggest sites like Amazon, for example, still use old-school passwords+2FA.

While that is an option, I've been using passkeys on Amazon since 2023.

Comment · 21 days ago
Comment · 21 days ago
Actually Google engineers in Switzerland started jxl.
Comment · 23 days ago
I didn't intend to give the impression that Apple was definitely going to use jxl-rs. You're correct; there's been total radio silence from the Safari/WebKit team regarding anything related to Rust.

But it makes so much sense for Apple, Mozilla, and Google to support jxl-rs. Of course, that doesn't mean it's going to happen.

Keeping quiet and then adding jxl-rs to a dot release like Safari 27.4 or something is also a very Apple thing to do.

Comment · 24 days ago
> Apple refused to support it because they wanted to patent-laden alternative to thrive.

Where do people get this stuff?

Apple finally supported WebP in 2020, 10 years after it was released by Google. Firefox added WebP support in 2019, a year before Safari. Was Mozilla also part of conspiracy to undermine WebP? Come on now.

Seems to me neither Apple or Mozilla wanted to be forced to support a format they had no say in developing. Usually there's a process for coming to consensus on standards.

WebP is ubiquitous now, not the case in 2010 when it was released.

It had advantages compared to JPEG, but not enough at the time to justify changing workflows, etc. WebP initially had better compression than JPEG, but as encoders/decoders improved (MozJPEG, Jpegli, turbo-libjpeg, Guetzli) the lead WebP had mostly went away regarding compression and visual fidelity.

Going forward, WebP is becoming less relevant by the day; it doesn't support wide gamut color; it only supports RGB. It's max pixel count is quite limited compared to AVIF and JPEG XL. Newer formats have use cases beyond the web; WebP doesn't.

Comment · 24 days ago
There were obviously some internal politics going on—Google joined the Alliance for Open Media, a consortium of the who's who of the media/tech industry: Apple, Facebook, Microsoft, Amazon, Netflix, Nvidia… the list goes on. They supported AVIF as the next generation image format.

Google apparently wanted to be one of the "cool kids" supporting AVIF. When they removed the JPEG XL code from Chrome, they created the excuse that there was little demand for it, along with some other disingenuous talking points that didn't quite make sense. Ironically the project that ended up becoming JPEG XL was started by Google employees in Switzerland.

Anyway, I’m glad Google is supporting JPEG XL now. I wanted to use JPEG XL files for a project I started a month ago, but it was a non-starter with global usage under 20% at the time.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton