I agree with your arguments when the purpose of a mockup (Photoshop or otherwise) is for visual concept / art direction / client presentation. But when you mov

I agree with your arguments when the purpose of a mockup (Photoshop or otherwise) is for visual concept / art direction / client presentation. But when you move past that stage, and begin to integrate HTML/CSS with server code, things get messy real quick, and that's the problem I think this article is proposing to solve. I think the terminology may be confusing. For example, in the vernacular I'm familiar with, "mockups" are in Photoshop, "templates" are static HTML, and "views" run on the server. And even so, I find these terms are often used interchangeably.