Review: HTML5 for Web Designers (A List Apart book)
paulstamatiou.com
paulstamatiou.com
Instead I was greeted with this quote in the book:
The [JavaScript] APIs in HTML5 are very powerful. They are also completely over my
head. I’ll leave it to developers smarter than me to write about them. The APIs
deserve their own separate book.
Fair enough. Those are rather technical subjects and this is an introductory book. I can live with that.More than this being an introductory book, it's a book for designers. The target audience is neatly contained in the title of the book. This means that developers aren't going to get everything they might want out of this book. As he mentions in the article, the term "HTML5" has become an abbreviated moniker for a fairly large set of new-ish web technologies and standards. I'd expect a book entitled HTML5 for Web Designers to read more like CSS3 for Web Designers.
I find that his quote about "completely over my head" being a little shocking.. he's written a book on DOM scripting and another on Ajax. If he can't grok these JS APIs I'm a bit worried.
Perhaps he's using exaggerated modesty to get himself (and the book) off the hook?
The muddle of knowledge that's expected of SV designers, and other designers in general is a result of the fragmented and confused state the web was/is in, IMO. Frankly, with the current toolsets available, there's no reason a web designer should have to focus on anything other than their design, and pass that off to someone that's skilled in the programming aspect to get their vision functioning. Personally I'd rather hire someone along those lines, rather than a jack-of-all trades.
I could easily say that it's preferable to have someone understand the core facets of every part of any field, but the truth is that you're lucky if you can find someone that has the core competencies in any specialized area.
I've successfully separated our designers from the code that implements their designs for the past 5 years and have got only positive results. The designers don't need to learn anything else, or fumble with code, they enjoy living in Photoshop/fireworks and passing it off. Developers shouldn't be doing any interpreting, the designs should be such they can clearly see what things should be.
Nobody said anything about static-mock ups, I said they should be focused on design, not coding. There are plenty of tools available that can allow them to mock-up an effect without coding.
I don't know what idealized world you live in, but sometimes you have to accept the situation and work with it. In any event, we can agree to disagree. Since we clearly have 2 different sets of opinions and 2 different sets of work experience history.
The [JavaScript] APIs in HTML5 are very powerful, but knowing that their neither relevant to or comprehensible by who I'm expecting (or fear) you may very well be we're just not going to go into any further detail right now.
really have been a better line?