Need to do some speed testing since the images are served from a third party server, but does seem much faster on mobile devices, and will fill in the gap before the <picture> element becomes more widely accepted.
Anyone got other responsive image solutions they can recommend?
The benefit of these two is that it doesn't require changing the actual image code, so if you use an image slider plugin, for example, you don't have to customise the plugin code to have optimised images delivered.
The thing about all of those is that you need to change the embed code for the images, which is not always a simple thing to do depending on what plugins you might be using. Great when you have the time and it can be done easy enough, as you can also change framing if you want.
I'd like to compare speed of the other options to determine if they can be just as fast as needing to embed multiple images.
I neglected to say though that most of my email work is sent via Mailchimp now with the client uploading their own images into a template so that's why I didn't identify this particular solution as being useful to my own workflow.
I do agree that it's good news there are so many solutions being developed to this issue!
It's a very complicated subject... wurfl looks good, but my worry with things like that is you're dependant on them. If they cease to be then you've got some more work to do.
I do like picturefill also, Scott is legendary.
I used some code from this article to help achieve something I was developing for a recent WordPress site. It's not ideal but I like the concept and for budgets that are a bit tight I was able to provide responsive imagery where it counts for not much effort.
Apart from being very complicated, that doesn't seem to address images that might be displayed via a slider plugin, or say in Woocommerce ...etc.
That's the added complexity with this and CMSs, you need to find a solution that works within the limitations of a CMS. You could go digging into the code of every single plugin you ever use, and edit the image output code to cater for a solution like this, but then you wouldn't be able to update that plugin ever, and it certainly seems like a hell of a lot of work compared to other options that are available.
That's exactly what I used it for... a slider for background images in a hero unit. It worked brilliantly for that specific job.
But, yep, it's not ideal for dealing with site wide cms imagery. The images everywhere else on the site were of a lower image weight than what was in the hero unit, so I felt I didn't need to worry about them so much... I just focussed on the big guns.
The fact is there's always going to be that complexity until the spec is finalised and adopted for something like scrset... especially with cms'. I think we're at the stage of what SiFR was to webfonts with responsive images.