In related news, I was fortunate enough to attend the 2015 Smashing Conference in Freiburg, Germany this year and one of the presenters was Eric Portis, one of the leading voices behind responsive images. If you want to see the epitome of an enthused and inspired web geek, here is the video of that presentation. :-)

And just in case you’ve been huddled under your desk hoping all this responsive image talk would simply go away, here is a pretty simple, yet thorough, run-down of where responsive images stands as of now.

Lastly, here is a little more detail about that WEBP thing you might have also missed… If you’re going to offer more than one image option, this really needs to be one of them…

In the last Today’s Readings I included a link to, and a few quick thoughts about, Google’s AMP Project. Here are the thoughts from a few other (smarter) people…

• AMPed up, by Jeremy Keith.
• Accelerated Mobile Pages Project, by Robin Rendle
• AMP and Incentives, by Tim Kadlec

I’m intrigued by Jeremy’s comparison of AMP to RSS, because I don’t think I noticed from Google’s initial post that the intent of AMP was to be “an alternate representation”… If that’s the case, maybe I don’t mind so much, but I do still believe that the web is strong and powerful enough that if developers build things correctly, then we really only need to build one web…

Got "use strict";? Then maybe you need "use strong";! Or do you? Doesn’t this also just solve the problem of developers not doing what they should be doing, and basically solving problems before they exist? I really start to worry about fragmenting the web into so many “pieces”… But at least this one just affects developers, sort of telling the browser that “I plan to code by this set of rules, so please let me know if I sway outside of that”…

So, maybe to help us all get to the elevated JS playing field, we could start with these 6 Free JavaScript Books for Advanced Learners.

And after reading all of those, I guess we should be able to answer Eric Elliott‘s 10 Interview Questions Every JavaScript Developer Should Know. (Eric starts off with a bit of a rant against class-based programming, which is certainly worth reading, but if you want, you can jump right to the actual questions.)

At this point we should all be used to technology knowing everything about us, so maybe the information that Your Browser Is can reveal shouldn’t be so surprising, but it still kind of is…

A nice collection of front-end tools. How many are in your toolbox?

Speaking of toolboxes, for any remote workers out there, here are 19 Tools to Stay Connected, Productive and Sane (Disclaimer: I make no promises on that last one…)

Something we don’t hear much about is browser-based databases. Sure, they made quite a stir when HTML5 first rocked the scene, but different browsers chose different databases, then there were reports that they were really slow, and we soon things went kind of quiet. Well, Nolan Lawson is here to help fix that quiet with a nice article comparing IndexedDB, WebSQL, and LocalStorage.

Based on some actual facts and stuff and things, Richard Howe offers up a few Takeaways From Mobile Web Behavior. Well worth reading before your next big redesign project!

Did you know you can use an SVG as your site’s favicon? Well, you can! Sort of… Note the big names in the first paragraph that “continue to ignore the format”… Bummer, makes total sense.

And finally, and Tetris lovers out there? Got anything you need to store somewhere? Then I have just the benches you’ve been looking for!

Happy reading,
Atg

Top⇪