You know what I want? I want a tag that I can use like <img> but more flexibly- I want to manage cache and authentication on images displayed in-browser, and the fact that I basically have to use URL or Cookie auth for image embeds is ridiculous. My entire API uses tokens, except for when it deals with image resources (and those images need to be protected to only display in the correct place, because they're not pictures of cats, but Highly Sensitive pictures of Important Cats).

I thought the futility of protecting image assets online was accepted a long time ago. Or are you being sarcastic? I don't get it.

> I work for a lot of artists and designers, these guys want fast, retina full-screen responsive images, and I’m not sure that it’s an unreasonable expectation, but I’ve got enough technological hoops to jump through to recall the days of “Netscape Now!” and “IE 5” badges.

Do the users want those too?

Do users want cellphones with 64bit CPUs, 1gb DDR4 RAM and an SSD, or a phone that turns on instantly and has near perfect responsiveness?

When I get the visuals dialed in a way that is quick and responsive, yes, the users seem quite receptive. I could do a better job for them with better tools at my disposal.

sure wish someone had explained why they disagreed instead of downvoting me :\