Message: previous - next
Month: November 2011

Re: [trinity-devel] KDE vs. Trinity: Is One Really Better?

From: Darrell Anderson <humanreadable@...>
Date: Tue, 15 Nov 2011 18:33:22 -0800 (PST)
> Sell concepts like this:
> You get work done faster and easier.
> The work-flow is what you are used to and have used for
> years.
> The work-flow is easier and it takes fewer movements to
> access what you need.
> What you learned previously still applies and you don't
> have to
> unlearn anything.
> You don't have to waste time learning how to do something
> you already
> understand in KDE3.
> etc, etc...

I think we identify those points in our proposed draft About/FAQ page in etherpad. Please review the page and feel welcomed to help.

> I think most people resist having to learn new things but
> they
> absolutely HATE having to learn to NOT do something that
> they have
> done continuously for years.  If you play on that you
> can get people's
> attention.

I don't think people resist change as popular as that adage might be. :) I think people resist change they did not ask for or resist when timetables for the changes are unrealistic. People want to move forward incrementally, comfortably. Changes like those in KDE and GNOME are unwelcome by many because most users did not have a meaningful vote and the changes are too dramatic without providing fallbacks to familiar territory. Same thing is happening in the Windows market, by the way. Some people love the new interfaces and work flows and that is expected. Many others could adapt if they had been treated with respect and compassion rather than as objects.

This is much like the frog in boiling water parable. If features are changed incrementally most users never object. They adapt. Change too many features at once with no forewarning and training and the frog jumps out of the water. :)