The first couple of points that sprang to mind after reading this – which have both been mentioned by lots of people already – are the time spent coding up a design that a client may or may not like, and the issue of presenting different aesthetics to different users, depending on what browser they choose to use (or have to use in their place of work).
If a PhotoShop/Fireworks mockup is created by somebody who understands designing for the web, then no false expectations will be created – body text will have no anti-aliasing and will be in a generic, web safe font, and so on.
I think ultimately, this kind of exercise is fine for articles on sites like 24ways.org, but on a day-to-day basis, in the average web shop, I really don’t think it’s practical – or even appropriate.
If web designers don’t want to be restricted by current browser standards, they should go and design for print instead.
Robin
The first couple of points that sprang to mind after reading this – which have both been mentioned by lots of people already – are the time spent coding up a design that a client may or may not like, and the issue of presenting different aesthetics to different users, depending on what browser they choose to use (or have to use in their place of work).
If a PhotoShop/Fireworks mockup is created by somebody who understands designing for the web, then no false expectations will be created – body text will have no anti-aliasing and will be in a generic, web safe font, and so on.
I think ultimately, this kind of exercise is fine for articles on sites like 24ways.org, but on a day-to-day basis, in the average web shop, I really don’t think it’s practical – or even appropriate.
If web designers don’t want to be restricted by current browser standards, they should go and design for print instead.