[jwtanner]

But you offered themes as a solution to a statement about UI quality, which is it not. Also you don't have to do what your users ask for, saying no to bad ideas is important.

Your not alone, the chromium team should have said no to themes as well.

[swah]

Curious... why do you think themes are a bad design choice for Chrome?

[jwtanner]

This may just be a matter of taste in the case of chrome, I think they are extremely ugly.

http://is.gd/b0ydO

[swah]

The "Themes by Google" ones are a little better.

[papachito]

Well it's open source dude, if you think you can do better at UI quality feel free to give it a try. And thanks for the advice... Also, theming is a good features, not all out users want to have the same UI. They can also fully customize the CSS. And for the matter, SO UI is far from perfect.

[jwtanner]

I was too harsh earlier. The main point I'd like to make is that themes are independent of the core UI refinements that need to happen. Shapado faces 6+ months of work before it can have quality of SO.

I support open source software, but who is going to sit down and do this painstaking work. It's easier to work on theming or mongodb, rather than make the titles spaced correctly ( for example ).

[papachito]

> Shapado faces 6+ months of work before it can have quality of SO.

Gotta love random estimates by people who never looked at the code or anything.

[jwtanner]

SO has being in development for more than 1 year, during that time the UI has being under constant refinement. Lets see where Shapado is in 6 months, my guess is exactly where it is now ( GUI wise ).