[sqeaky]

I think it is even more extreme. It is the normal result of having multiple teams making UIs. Each team is going to try things that are different.

Consider how different the iPhone and windows 10 are. Or windows 7 and windows 8. Because the community driven teams don't stop when they run out of money they stick around, but they also have really small marketshare.

[gorkonsine]

The problem is too many people with too much time on their hands. For the commercial teams, they're in-place and receiving a paycheck, so their managers want to make themselves and their teams look like they justify their salaries, so they come up with New!! stuff to do. For the FOSS people, it's partly the same: the Gnome3 devs are largely employed by Red Hat. For others serving in a volunteer, it's a lack of discipline and too much time on their hands which could be used for more productive stuff (like documentation, fixing bugs, etc.).

[sqeaky]

You imply being able to write code for fun in your leisure time is bad, but so many great things have come out of leisure time.

[gorkonsine]

Writing code in leisure time has given us some really great FOSS applications. But like many things, it's a double-edged sword: it's also given us Gnome3 and a lot of today's unnecessary churn. However, unlike little 1-man projects, Gnome3 isn't just a leisure-time project, it's largely led by paid developers at Red Hat. So honestly, I'd say that the volunteers really aren't the problem, and if you eliminated the salaries of the Gnome devs working for RH, maybe we wouldn't have some of these problems; the volunteers aren't going to sustain all that effort on their own. The commonality I see with UI churn across the industry (proprietary and FOSS) is that UI people are being paid to do UI work. That means they have to justify their pay and their existence by doing more such work, even when it isn't needed and it's downright bad.