- From: Ilya Grigorik <igrigorik@gmail.com>
- Date: Sun, 10 Nov 2013 09:29:55 -0800
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: WHATWG <whatwg@whatwg.org>, Yoav Weiss <yoav@yoav.ws>, Ian Hickson <ian@hixie.ch>, Adam Barth <w3c@adambarth.com>
On Sun, Nov 10, 2013 at 8:59 AM, Tab Atkins Jr. <jackalmage@gmail.com>wrote: > It's easy to look at something more complex than what you're used to > and dismiss all the excess as unneeded, but it's really, seriously not > in this case. The things I'm addressing are the things that RICG > research found were common and necessary, no more and no less. > Big +1 to that -- src-N addresses all the RICG use cases in a consistent and coherent way.. and is the only option that does so. Serving images in our new multi-device / responsive design world *is* a much harder problem and the "complexity" of src-N is simply a reflection of that.. Sticking our heads in the sand and pretending that this is not the case, or punting the problem down the road (as we've already done for the past few years), is not a sound strategy.
Received on Sunday, 10 November 2013 17:30:59 UTC