But I think one should be careful about the distinction between front-end design and development. This book seems to focus on development, and as someone who's taken a couple of courses from Frontend Masters, I trust it to be solid.
I had a chance to work with Cody on the jQuery Cookbook, and he's a smart guy. So Cody, if you see this, my apologies for poking fun at your new book's mobile experience!
My chapter of the jQuery Cookbook had a much bigger blunder. In a "recipe" called Coding Bare-Metal Loops, I recommended a particular loop style as the ultimate in speed...
> Use a for loop instead of .each(). To iterate over an array, it’s hard to beat this loop:
for( var item, i = −1; item = array[++i] ) {
// do stuff with item
}
Well... It didn't quite turn out that way. This loop style can kick you out of the optimizer because it tries to access the nonexistent element after the end of the array. That's perfectly legal in JavaScript, of course - any nonexistent element evaluates as undefined - but code optimizers do not like it when you do that.
So a conventional loop turned out to be much faster:
Just like cotton in a bag isn't a comforter, a website with itsy-bitsy manuscript is not a fucking book.
So ...
> Poking fun?
Not at all.