Forgot your password?
typodupeerror
GNOME GUI KDE Open Source Linux

Linux Desktop Summit Program Announced 121

Posted by Soulskill
from the scheduled-for-2002 dept.
jrepin writes with this excerpt from an announcement by KDE: "The Desktop Summit is a joint conference organized by the GNOME and KDE communities, the two dominant forces behind modern graphical software on free platforms. Over a thousand international participants are expected to attend. The main conference takes place from 6-8 August. The annual membership meetings of GNOME and KDE are scheduled for 9 August, followed by workshops and coding sessions on 10-12 August."
This discussion has been archived. No new comments can be posted.

Linux Desktop Summit Program Announced

Comments Filter:
  • Re:Interesting times (Score:5, Informative)

    by DNS-and-BIND (461968) on Sunday May 22, 2011 @07:49AM (#36207474) Homepage
    Wow, you mean they're going to replace Unix pipes with some new system based on javascript? Good riddance to old rubbish! What have Unix pipes ever done for anyone?
  • by lkcl (517947) <lkcl@lkcl.net> on Sunday May 22, 2011 @07:51AM (#36207486) Homepage

    what happened to enlightenment, xfce, fvwm, python-plwm and all the others? i hate to mention EvilWM (1000 lines of c), or XMonad (1200 lines of haskell i believe) as it's hard to have any kind of meaningful discussion around 1200 lines of haskell, but, seriously, why weren't all the other window managers more seriously represented? oh wait - there's _one_ talk (an overview) on the EFL classes: https://www.desktopsummit.org/program/sessions/quick-overview-enlightenment-foundation-libraries-and-e17 [desktopsummit.org]

  • by Anonymous Coward on Sunday May 22, 2011 @07:58AM (#36207512)

    They should be clubbed with hardcover copies of The Art of Unix Programming by Eric Raymond -- http://www.catb.org/~esr/writings/taoup/html/index.html -- particularly the chapter "Basics of the Unix Philosophy"...

            Rule of Modularity: Write simple parts connected by clean interfaces.
            Rule of Clarity: Clarity is better than cleverness.
            Rule of Composition: Design programs to be connected with other programs.
            Rule of Separation: Separate policy from mechanism; separate interfaces from engines.
            Rule of Simplicity: Design for simplicity; add complexity only where you must.
            Rule of Parsimony: Write a big program only when it is clear by demonstration that nothing else will do.
            Rule of Transparency: Design for visibility to make inspection and debugging easier.
            Rule of Robustness: Robustness is the child of transparency and simplicity.
            Rule of Representation: Fold knowledge into data, so program logic can be stupid and robust.
            Rule of Least Surprise: In interface design, always do the least surprising thing.
            Rule of Silence: When a program has nothing surprising to say, it should say nothing.
            Rule of Repair: Repair what you can — but when you must fail, fail noisily and as soon as possible.
            Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.
            Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.
            Rule of Optimization: Prototype before polishing. Get it working before you optimize it.
            Rule of Diversity: Distrust all claims for one true way.
            Rule of Extensibility: Design for the future, because it will be here sooner than you think.

    GNOME: Stop your "War On Users" by hiding user configurations or ripping them out!
    KDE: Let up with the eye candy for once! Simple is beautiful.
    CANONICAL: Admit Unity is a total failure, ask for our forgiveness and never, ever do it again! /Rant off

  • by drinkypoo (153816) <martin.espinoza@gmail.com> on Sunday May 22, 2011 @09:55PM (#36213212) Homepage Journal

    The Network Manager is just a wrapper around ifupdown, so that follows the Unix way nicely...

    WTF happened to this idea of the 1970ies that giving the user a chance to improve her understanding of the system should be part of what's called ergonomy?

    Apple.

All warranty and guarantee clauses become null and void upon payment of invoice.

Working...