That depends on where you sit in the working class. At the bottom are people who earn almost nothing and price it the only consideration. As you move up though you find people who have some disposable income and start caring about style. At the top end of the working class you find people who can afford a new car (where this is aimed!) and those people tend to care about style.
Drat! I hoped this was going to cover the internal battle where Google executives trying to stop JPEG XL and how engineers finally convinced them to change their minds.
My guess: the engineers didn’t win the argument. The executives just gave up once all the other browsers had added support.
> The executives just gave up once all the other browsers had added support.
The big turning point seemed to have been Adobe adopting JpegXL as an approved image compression algorithm for the upcoming PDF spec. update. With that, since all browsers seem to also want to be PDF renderers, meant they had no choice but to include a JpegXL decoder. The win, if there was one here, was that the decoder they have to ship anyway now was exposed for use by tags as well as by the PDF renderer.
JPEG XL is largely a Google effort including in creating the specification, the reference implementation and later a safer Rust implementation. Why would Google executives want to stop it? From what I gather it's Chrome engineers that didn't want it because it was huge, had little adoption (at the time), and was rather redundant with AVIF and WebP (for Web purposes). Not saying they didn't have related mandates from executives but they also have a lot of say in what goes in and what doesn't.
It's interesting how different theories come about when there is a lack of information and a high degree of preexisting bias. Reality is a lot simpler - it wasn't deemed worth the cost of addressing the security problems in the existing library so someone chose to abandon the format. However as industry adoption increased and a newer safe library appeared, the decision was changed. Also, note that while Google developed the new rust library, it wasn't the chrome team who made the investment.
> Reality is a lot simpler - it wasn't deemed worth the cost of addressing the security problems in the existing library so someone chose to abandon the format.
As evidenced by what? When first rejecting JPEG XL, Google did share their reasoning, but security problems hardly figured in it.
My guess is that Apple supporting it natively in iOS (there's an option in iPhone 16+ to save taken photos as JPEG-XL instead of Apple's proprietary format) likely also pushed the needle
I think it might have something to do with a Rust based decoder becoming available. IIRC one of the reasons for not implementing it before was expanding the attack surface.
WebP is 15 years old, and Google cares about it less than anybody else. Pretty much everybody else supports WebP but Google can’t even be bothered adding support for it to Google Docs.
They added enough fear/uncertainty/doubt around jpeg xl that no sane organization will adopt it now. God Google might decide to remove support again in 2027
It was one of AT&T’s attempts to “kill the internet”.
The people working on it were down the hall from me when I was at AT&T.
It only worked on Novell networking. I asked how they plan on dealing with various Novell limits and they’d respond with blank stares.
The plan was to restrict it to only work on AT&T networks. So, it was more of a marketing ploy than a technology.
When I’d ask “how could this little project beat the internet, which is huge and growing exponentially?” And was told basically they believed if they could act fast enough, nobody would know the internet existed.
And people wonder why I had no faith in AT&T management.
Because ownership can change. I can still use Gmail to send email from my old university address that I lost access to 15+ years ago. This should not be possible.
Isn't this just using SMTP through whatever mail server you have connected to Gmail?
Either way, this is likely going to stop me from using Gmail as my mail aggregator, I've used this feature for nearly a decade to send and receive from 6 different addresses, Gmail recognizes the to address and automatically sets the from address to the correct account.
Is Thunderbird still decent nowadays? What's a decent mobile + desktop replacement?
> Right now you can forge email from any email address you can verify ownership
I find this sentence confusing. Do you mean “forge” in a technical sense of “this email came from a server unassociated with the domain”? I don’t really get it. I’ve know this feature existed in Gmail for 15+ years and have made regular use of it. Plus I’ve used it to help older relatives keep an old address alive.
What an odd choice of inflammatory language for a feature that uses standard email headers. It doesn't forge anything since it clearly says it was sent from the GMail account on behalf of the other email address in the headers.
This is FANTASTIC! I laughed so hard I nearly fell out of my chair.
Have you seen DNSControl?
If you want a serious alternative to the Route53 API, there's an open source project called https://dnscontrol.org/ DNSControl. It's like Terraform for DNS but it doesn't suck like Terraform.
Version v5.0 just shipped. It's a major rewrite that makes it much more extensible.
I'll recommend dnscontrol as well, although the post is an unseasonal April fools joke, so helpful suggestions may be out of place.
The is-a.dev project uses dnscontrol to manage a subdomain registration service in GitHub, which is really clever. See https://github.com/is-a-dev/register
reply