You are probably aware of that you are missing some points: - There are different use cases in some of which CLI has advantages, in others GUI has advantages. (To give you an equally one-sided example: No, i do not want to create graphics via CLI or write them in the shape of an XML file.) - A GUI is easily discoverable, a CLI is not. - A GUI is attractive (if done right), a CLI is not. Attractiveness matters, even if it's not adding/partly deminishing productivity.
André. On Thu, 2007-03-15 at 06:31 +0000, Jonathon Blake wrote: > Chris wrote: > > > >A GUI interface is intrinsically user hostile,and best avoided. > > >Any GUI is going to be "awful:" and dysfunctional. The only question > > >is how dysfunctional it is going to be. > > > > with that kind of attitude a lot of the stuff i see in the openoffice > > 'user experience' makes a lot more sense > > I forgot to include the trivial example. > Add 1 000 colours to the colour palette of OOo, using the GUI. > Add 1 000 colours to the colour palette of OOo, by editing the raw file. > > Which one takes less time? > Which one is easier to do? > > I know which option I use, when I create new OOo colour palettes. > To create my 16^8 colour palette for OOo, I cheated, by writing a > python script to generate it for me. > > As I said, that is the trivial example, that clearly demonstrates the > unproductive nature of a GUI. > > xan > > jonathon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
