Are you sure? They just blogged about supporting it in Chrome with their Google developed jxl implmention in Rust.

They're bringing it back. Chrome 155 onwards will support it.

https://developer.chrome.com/blog/jpeg-xl-in-chrome

Perfectly stated. Thank you.

This ^

Dude, Daring Fireball’s post really shed a light on this matter. Your post here seems like you’re hiding a lot more.

Famous last words: easy fix.

The Rovo MCP server manages scope credentials securely with “bring your own LLM”. Yet somehow they still fucked up with their own agent

This comment strikes me as being in bad faith: "Oh so you don't like A? You must be on the side of ¬A!"

I ask, humbly, that people please not do this. Nothing good has ever come of it.

Why is this the top-most comment when the user obviously didn’t know how to use HTMX?

I used HTMX to serve my HTML partials. My HTML partials got too big. Not HTMXs fault. How do I fix that? Split them up? Use lazy loading? Pagination? That isn’t clear. I settled on a solution that gave me the least compromises while not abandoning the sprit of HTMX and HATEOAS.

HTMX has a whole section on their site dedicated to reasons not to use HTMX: https://four.htmx.org/essays#counterpoints

Alpine Ajax is actually promoted on their site as an alternative option but to stay within the HATEOAS universe: https://four.htmx.org/essays/alternatives#alpine-ajax

I tried building something more than a like-button or simple search. It wasn’t that easy to wrangle once it got more complicated.

Internet, enable Streisand-effect mode.

One word: crazy

I’d love to know too.