But when I look at websites, many of them go out of their way to have them make "unique", instead of just using defaults.

I think one big reason for that is that, with websites, it isn't so far "out of their way" as it is with GUI toolkits. It's relatively easy to significantly spice up a web page. Moreover, it's easy enough that a designer can design a website without interacting much at all with the programmers.

Really, I think the abberation is the slew of programs that adhere to the (usually drab) defaults. Unlike windows programs, Java programs, and Tk programs, most human creations are distintively styled. Publications included. Consider the variations in books... cups... doors... If programmers made all the furniture in the world, would we all sit down to eat our dinners at gray card tables with matching folding chairs?

I think GUIs will need to mature a great deal before consistent and intuitive interfaces that don't suck aesthetically will become commonplace. Of course, by then, the "intuitive" requirement will take on a whole different meaning by virtue of the fact that most people will be exposed to computing from a very early age.

-sauoq
"My two cents aren't worth a dime.";

Really, I think the abberation is the slew of programs that adhere to the (usually drab) defaults ... sit down to eat our dinners at gray card tables ...

I dont care what the application is, design requires proportionate attention to competing and complementary criteria. For instance if usability is ignored at expense of performance, users are not going to succeed. Consider that in a study done by Nielsen, users failed in achieving successful outcomes for 35% of web sites out of 139 web sites. Trade-offs are required.

Firmess, commodity and delight, (Marcus Vitruvius Pollio, 90-20 BC) is an often repeated phrase in design literature. Applied to software, the correct balence between this trinity of ideals is critical.

For in-house built applications as the user suggests, the workmanship required for extra polish (delight) is not warrented ... at least until version 3 - 4 when all the other issues (firmness, comodity) have been addressed.

I never forget the day pickles bagged his first hippy - mr. burns

I dont care what the application is, design requires proportionate attention to competing and complementary criteria.

Did I say otherwise?

I'm not even sure how to reply to your post because it seems, well... axiomatic.

I can say this: usability is as much a function (if not more) of the user as it is of the application. More sophisticated users tend to have less trouble, even with non-inuitive interfaces, than less sophisticated users. We all learn how to adapt ourselves to various interfaces, and adapting to new ones is itself a skill. Part of the point I was making in the node to which you replied was that, as computing becomes more and more a natural part of daily existence and users become more and more sophisticated simply by virtue of exposure, the focus will naturally shift toward 'delight' because usability will be second nature. As usability becomes less of a focus with the growing sophistication of users (as well as that of designers) aesthetics will play an increasing role in interface design.

Note that I also think aesthetics currently plays a larger role in web-based interface development because the medium makes it easier to separate presentation and "content" than, for instance, most GUI toolkits.

-sauoq
"My two cents aren't worth a dime.";

Some GUI programs do go out of their way to look different, and offer the user a way to change the look as they see fit. In particular, MP3/Media players tend to do this a lot.

I've worked at a place that provided "skins" for their web app. It was actually quite simple. *shrugs* Granted, the skin had to be stored server-side, but that's because HTML doesn't provide an easy way to choose images on the client machine.

------
We are the carpenters and bricklayers of the Information Age.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

Web "skins" can be implemented much better by using an all CSS design. The HTML doesn't have to change, only the CSS. Here is a site with tons of examples:
CSS Zen Garden

All the designs all use exactly the same HTML file only the CSS and images called by the CSS change.