Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
KDE GUI Programming Software Linux Technology

International OSS Desktop Conference aKademy 2004 161

Torsten Rahn writes "The KDE Project is pleased to announce the successful completion of the KDE Community World Summit ("aKademy 2004") in Ludwigsburg (Germany) taking place from August 20th to 29th. With more than 230 KDE core developers, usability and accessibility experts, translators, editors and artists participating, the event is expected to have a huge and lasting impact on the next major releases of the leading Linux and Unix desktop environment. In addition, 270 visitors from the KDE user base and from other Free Software projects brought the total number of attendees to 500. The international participants, coming from 5 continents, took part in 65 talks, 10 full-day tutorials and numerous BoF-meetings over the course of 10 days. Thanks to this huge turnout and the numerous activities, the event evolved into the largest conference ever held that focused on a single open source desktop environment."
This discussion has been archived. No new comments can be posted.

International OSS Desktop Conference aKademy 2004

Comments Filter:
  • WOW! (Score:5, Funny)

    by donscarletti ( 569232 ) on Sunday September 05, 2004 @02:14AM (#10161081)
    Wow, one post and this still hasn't degenerated into a gnome-kde flamewar, I am impressed.
    • Re:WOW! (Score:1, Funny)

      by Anonymous Coward
      what's to argue about? gnome is faster. who wants graphics over speed? stupid kde users.
      • Weird. Way back in the day, when I used to use Linux as my primary desktop OS, KDE was the fast one and GNOME had the eye candy. That was about three to five years ago... Haven't used either one since. Ah, how things change.
        • Re:WOW! (Score:3, Interesting)

          by be-fan ( 61476 )
          Except for startup-speed, KDE is faster than GNOME. Poor resize and redraw plagues GNOME apps.
          • Re:WOW! (Score:5, Insightful)

            by Anonymous Coward on Sunday September 05, 2004 @03:24AM (#10161261)
            This is such a pointless arguement. If I wanted speed I wouldn't even install X, I'd use the console the whole time.

            Features that YOU want should come first, speed should only be a concern if it actually has a major affect over what you are trying to get done, which really isn't the case on modern hardware. After all, some people are happy using Windows XP.

            So what if KDE is slower than Gnome and uses more memory? (That's just an example, I have no idea what the actual case is here) That's why you have the hardware, it's there to be used and abused to get the results you want.

            And for the record, Gnome runs just fine here, fast enough speeds everywhere. I obviously don't have the 'plague' on my system...
            • Re:WOW! (Score:5, Informative)

              by be-fan ( 61476 ) on Sunday September 05, 2004 @04:22AM (#10161368)
              You probably do, it's just that you're so used to it that you accept it as being normal. I've got a 2.0GHz P4. Using GNOME for me is very hard, because it feels "heavy." The heavy feeling comes from three major places:

              1) Menus are displayed before icons are loaded, so the first time you use a menu, all the icons get loaded from disk, and you have a blank menu for about a second until the loading is done.

              2) Window redraw and resize is handled poorly. Even the simplest GNOME apps (eg: Gedit), can't resize smoothly without the content area lagging behind the window frame. Moving or resizing a window above another window causes all sorts of ugly effects as the toolkit takes it's sweet time handling the expose events.

              3) The lack of multithreading causes the UI of apps like Epiphany to lock for several seconds when loading/rendering complex pages. This is a major no-no. I don't care if the app is simulating the universe --- the GUI should always respond immediately to the user.

              Yes, most of these things are cosmetic, but cosmetic things can have deep psychological impacts. The redraw problems, in particular, make it seem like the computer is having trouble keeping up with my workflow, and destroys the otherwise solid feel of the GNOME desktop. The lack of a solid feel, in turn, makes the desktop irritating and tiresome to use in the long-run.

              PS> You're "if I wanted speed I wouldn't even install X" comment is bogus. I like lynx a lot, but I'd rather surf Slashdot with a graphical browser, thank you very much.
              • Re:WOW! (Score:3, Interesting)

                by renoX ( 11677 )
                Personnaly it is 3) that bother me the most in many applications: Mozilla also freeze way too often when it opens a new page, which of course reduce the "user's experiment" of having several tabs or window at the same time (BeOS was great in this regards: very responsive)..

                Changing applications to use more multithreading to improve "user's experiment" is unfortunately a very big job, which won't happen soon, but I hope that with the multi-core CPU coming soon, perhaps developpers will be more receptive fo
                • Now if the menu contains mixed entries: icons and text, then there is a good solution which is sometimes used...

                  Or why not use the Qt/KDE solution? Create the icons the same time you create the menu and keep them in memory. This will cause a slight delay in loading the application if you load icons from the filesystem, but it doesn't bother me nearly as much as the delay at the point of menu display.
              • Re:WOW! (Score:3, Interesting)

                by Cthefuture ( 665326 )
                Gah, it's probably your video card and/or your settings more than anything else (make sure GDK_USE_XFT is defined in your environment).

                nVidia is the only way to go on Linux. Sorry but everything just works so much better with nVidia.

                GNOME starts up hella faster than KDE. It feels a lot better, the fonts look better, I like the consistant button placement, and after getting used to the GUI OK-button-always-on-the-right I wish everything was like that. KDE feels "clicky", I don't know how else to explain
                • Re:WOW! (Score:3, Informative)

                  by be-fan ( 61476 )
                  Gah, it's probably your video card and/or your settings more than anything else (make sure GDK_USE_XFT is defined in your environment).
                  It's not my video card or settings. It's been the same on every Linux distro I've ever used, and I've used a lot of htem.

                  nVidia is the only way to go on Linux. Sorry but everything just works so much better with nVidia.
                  I've got a GeForce4Go running the NVIDIA drivers.

                  GNOME starts up hella faster than KDE.
                  Who cares how long it takes to start up?

                  It feels a lot better,
              • > of ugly effects as the toolkit takes it's sweet time handling the expose events.

                Please explain why this doesn't happen on xfce. It uses the same toolkit.
            • Re:WOW! (Score:3, Insightful)

              by Tim C ( 15259 )
              After all, some people are happy using Windows XP.

              2.4GHz CPU, 1/2 gig of RAM... yes, XP runs perfectly smoothly, as do Java GUI apps, etc.

              As you say, on modern hardware, for 90%+ of applications resource usage is a non-issue.
      • Re:WOW! (Score:2, Interesting)

        by timmarhy ( 659436 )
        if you want a fast desktop which is completely usless and painful to do anything in just go the whole hog and use twm. the rest of us who want our desktops to be useful and a pleasure to use will stick to kde
    • I think gnome looks like macOS.

      I like macOS.

      My next machine will be a mac.
  • So, what exactly, if anything, was decided about KDE 4 at aKademy? Osho
  • by 3seas ( 184403 ) on Sunday September 05, 2004 @02:47AM (#10161179) Homepage Journal
    KDE may be the most popular but its not the best that can be done.

    getting to the best may just require siome stepping stones, like kde, gnome, your favoirite desktop, etc..

    But I think it is amazing how there is still a lack of a standardized general user accessible IPC port so that users who so chose can automate some things on their own.

    Free software will never be free until it is easy enough to create that most anyone with a basic undertsanding of software concepts can create software thru the use of general automation tools. Be it that they use such tools to do simple scripting or complex programming.

    But one thing is for sure. A standardized user accessible IPC port is required to reach that level of computing usability.

    Flamewars? I'm sure there is plenty better to do..... Or are you all waiting for MS to show you via "software factories" of which they are pursuing.
    • You want IPC? On UNIX? Have you heard of little things called "pipes" and "shell scripts"? : )

      On a more serious note, this sounds like a job for freedesktop.org [freedesktop.org]. You might find the bit about CORBA (the first bullet on the page) interesting...
    • by Anonymous Coward
      DCOP?
    • by latroM ( 652152 ) on Sunday September 05, 2004 @05:38AM (#10161495) Homepage Journal
      Free software will never be free until it is easy enough to create that most anyone with a basic undertsanding of software concepts can create software thru the use of general automation tools. Be it that they use such tools to do simple scripting or complex programming.

      Free software is free already. You don't need to know how to program to use your freedoms, like you don't have to be a carpenter to build your house.
    • by kalpaha ( 667921 ) on Sunday September 05, 2004 @05:55AM (#10161527)
      If you think KDE is lacking a standardized general user accesible IPC port, you obviously haven't heard of DCOP, which can be used to control programs from the command line (with the dcop utility), python or perl scripts, C++ programs, etc. and is easy to add support for.

      Some command line examples of dcop in action:
      dcop kmail default checkMail
      tell KMail to check for new mail
      dcop kwin default setCurrentDesktop 4
      switch to desktop 4
      dcop kmail default compactAllFolders
      tell KMail to compact all folders
      dcop kdesktop default logout
      logout
      dcop konqueror default openBrowserWindow www.kde.org

      open new konqueror window with www.kde.org

      I am _not_ new here, but it never ceases to amaze me how people are so eager to flame away without any factual support for their rants.
      • by 3seas ( 184403 ) on Sunday September 05, 2004 @07:05AM (#10161648) Homepage Journal
        to those comments refering to dcop and dbus...and even corba

        Yes guys, I'm aware of these, however neither are standard in the general scope of linux or FSF software but are instead desktop specific or to complexicated, and this only helps the divide of flamewars.

        for whats it worth I even have a bounty set up for anyone who wants to create a bridge between linux and AROS (Amiga Research OS -- a FOSS project on sourceforge -- that can run hosted on linux. bounty thru Team AROS) via such existing projects as dbus ... or dcop... or hell, a bridge that will allow communication to/from AROS to linux IPC whatever used.

        but ease of use and ease of adding to existing open source applications (this IPC port) and documentation of what functionality is accessible thru the port in such applications, is needed.

        perhaps there is something to be learned from how Amiga did it, and it became standard, easy to impliment and use and generally the apps include documentation of accessible functionality.

        dcop only deals with a small percentage of available packages... and dbus currently even less, but not even a handful of apps.

        Standard doesn't mean having numerous and obscure way of doing it (IPC at the user level), as that is quite the opposite of standard.

        So.... there are better things to do than flamewar over destops... as such is only a non-productive distraction.

        its important, I cannot stress that enough, given what MS is up to in teh direction of "software factories" methodology --- their book has missed two publishing dates so far but they are doing what they do instead.... collect feedback on the scope of this direction via shorter articles, websites dedicated to software factories, etc...

        google on - software factories MS book - and if you really understand what they are up to, then you too will realize the importance of getting an easy to use and impliment standard IPC in use. ... shrug...

        Maybe that will be dcop or dbus.... A plan, good, fair or poor, is better than no plan at all. Being destop specific is not a plan for the bigger picture or scope of FOSS packages.
        • From your post, it seems you're not aware that both gnome and kde seem to be moving towards using dbus.

          I can't say for sure that kde will use dbus, but if I was a betting man, I'd say it will :)
          • I'm aware of the goals of dbus. Its these goals that inspired me to name it in the AROS bounty I mention above.

            I am also watching with interest DragonflyBSD, as not only does Matt Dillion seem to understand a direction towards simplicity but also wrote a C compiler for Amiga. He also was the originator for csh on the Amiga, which interestingly enough provided a way to send and receive messages via the Amigas IPC ports typically recognized as AREXX ports, however... AREXX didn't need to be running in order
    • Umm Old News... (Score:3, Insightful)

      by nurb432 ( 527695 )
      Lets see, you have 'pipes', 'dcop', 'shell scripting', 'scripting in kde', 'kparts'...

      All these allow for what you are talking about..

      Perhaps kde is not the best that can be done, as you put it, but it does what you are asking for... today...

      A tad bit of research before you toss in the pro-MS line might help your credibility..

      • I'm not pro MS and you would know this had you read my response above. which BTW does address your points.

        somehow it just doesn't seem to be research, for you to simply have read it. The research would come in what you would find in the mentioned google search.

  • by kad77 ( 805601 ) on Sunday September 05, 2004 @02:52AM (#10161189)
    Forget flamewars... How about some efficiency standards?!?

    Why is it that this candy-coated windowmanager runs like a *DOG* when it's just moving windows and drawing text on a 512mb 550MHz PIII system, and BeOS 4.0 (pre)release could run multiple video streams effortlessly without lag (may as well mention almost instant boot) on a 166Mhz PPC 604 with 128 MB RAM? 5 years ago.

    Maybe getting paid for your work and quality go hand in hand in some products?
    • I don't know anything about BeOS. So can someone enlighten me why BeOS used to kick so much ass (supposedly) but it's not in production anymore? I read several posts in slashdot about it being really good so I want to know more about it...
      • by mrchaotica ( 681592 ) on Sunday September 05, 2004 @03:08AM (#10161230)
        They didn't have enough marketing clout to get a real foothold into the market. They couldn't get PC makers to ship PCs with BeOS because of Microsoft, they didn't have the established reputation to get distributors for their own hardware like Apple, and they weren't giving away their stuff for free like Linux.

        Also, it's possible that it was too expensive (I don't really know, though).
      • by be-fan ( 61476 ) on Sunday September 05, 2004 @03:19AM (#10161245)
        Well, the first thing to remember is that good technology doesn't ensure success. Indeed, the general rule is that the first product to be "good enough" is the winner, not the "best" product.

        Now, there are a couple of reasons why BeOS was so great:

        1) It was pervasively multithreaded. Each window had it's own rendering thread that ran independently of the application logic. This allowed apps to be very responsive, even under heavy load. It's sad that even on my 2.0GHz P4, Mozilla still blocks the UI for several seconds when certain pages take too long to load or render.

        2) It had a phenomenal scheduler. It wasn't comparable, in many ways, to Linux's O(1) scheduler (it wasn't very scalable), but it was wonderfully optimized for interactive use. It's interactivity estimation was lightyears ahead of what's in the O(1) scheduler now.

        3) It's multimedia subsystem was very good at moving data around the system efficiently.

        4) It's toolkit was well-coded with respect to smart redraw and resize behavior.

        Interestingly, the OS wasn't all that structurally different from Linux. It had a fairly POSIX-complient modular kernel. It run it's video and audio subsystems as a seperate process (like X, aRts, and Jack). It was just very well-implemented with an eye towards a fast and elegant UI.

        Of course, the OS had it's darksides. The toolkit wasn't font-sensitive and layout-based, the VM was antiquated, I/O and network performance was only decent, etc. However, for the average desktop, this really wasn't a big deal, and not something that couldn't have been fixed had BeOS survived to today.
        • Thinking back, I was asking that rhetorically. However, I am really glad that someone else that used/uses this wonderfully designed and very well thought through OS decided to recite some specifics that made it so.
          That's why we come back to Slashdot!

          I'd also like to point out, that in the interest of fostering development, once I signed up with the company, without cost to me they sent pressed OS releases very often, updated MetroWorks compiler and toolkit releases, and even some clothing!

          Would Be, I
          • by IamTheRealMike ( 537420 ) on Sunday September 05, 2004 @06:17AM (#10161570)
            It's worth pointing out that the pervasive multi-threading of BeOS was arguably as much a weakness as a strength.

            Multi-threaded coding is hard and don't any coding jocks tell you otherwise. It is significantly harder to do 100% correctly (and nothing less than 100% correct will do) than single-threaded coding.

            Indeed, according to one of the ex-Be engineers one of the things that hurt BeOS was that writing software for it was quite tricky, it basically meant writing robust thread-safe code even for a simple text editor. There's a good discussion of it here [osnews.com].

            Anyway it's sort of academic. One of the main uses of multithreading in BeOS according to be-fan was to do window rendering in a separate thread. Linux will get something very similar within a few months when X compositing lands. OK so it won't be a thread inside the same app, it'll be a separate process which is rendering the entire screen at once but the effect is the same - no matter how busy the app is, you won't be able to "rub out" the contents of the window.

            • I agree that multithreading is hard, but it depends also of the problem: let's suppose you have two totally independant task to complete, firing two thread to do it won't be complicated whereas if you have two closely related task a synchronisation nightmare is in order..

              I'm not convinced that X composition will be as good as the multithreading of BeOS, it may help a little but if your application is busy doing something complex the UI will not be responsive even if the window won't be "rubbed out".

              Now ho
              • The biggest problems with multithreading came from apps (like Mozilla) that were designed for single-threading. The Be API was also part of the problem, because it didn't force a seperation fo model and view, which would have made it easier to put each in it's own thread. It's interesting to note that Longhorn will run each Avalon window in it's own thread, since Avalon has a much better seperation of model and view.
            • Well, the complexity of multithreading depends very heavily on your synchronization model. The "locks around shared resources" model is a great deal more complicated than the message-passing model. The message-passing model tends to be avoided, because it has inherently more overhead, but with multicore hyperthreaded processors becoming more common,, it might be the case that the overhead of message-passing is outweighed by it's ability to let the code utilize the extra processors.

              If you consider that kern
        • Changing of Linux applications to become multithreaded is obviously a *huge* task (3 and 4 are also complicated), but I wonder why the point 2 hasn't been solved yet?

          Has someone tried to replicate BeOS scheduler on Linux? Is BeOS's scheduler described somewhere?
          • Well, Con Kolivas has his staircase scheduler patch that's trying to get better interactivity, and recently Nick Piggen also has a scheduler patch designed to get better interactivity. See these kerneltrap.org stories:

            Nick Piggen's scheduler patch [kerneltrap.org]

            Con Kolivas's scheduler patch [kerneltrap.org]
      • Check it out here: BeOS Max Edition [bebits.com]. It's freeware now and has a pretty good selection of apps. It has BeFS which is everything WinFS wants to be but never will be, and BeFS has been around since 1996. There are some really great things about the OS, but the lack of supported hardware, and afew other things are reasons why I don't currently run it anymore (although that may change). Linux is great and if tuned right, performs really well. If you want fast boot times, there are a few articles about making li
    • It's Desktop Environment (or something similar, I'm not even quite sure either). I'm sure that the devs behind KDE would love nothing more than to have a media friendly, zippy desktop, but as Daniel stone mentioned; the state of X is a mess, and since that's what KDE libs are built upon there isn't really much that can be done to speed up past a certain point. With X currently being optimized and maybe even modularised we'll see noticable speed gains in the future.
    • by MrHanky ( 141717 ) on Sunday September 05, 2004 @07:44AM (#10161729) Homepage Journal
      But one reason why BeOS was so snappy was because apps also took advantage of its pervasive multi-threading and the scheduler. This was, AFAIK, because the API sort of forced you to write multi-threaded. So Be had a lot of small, snappy, but crappy, applications that you could use to show off its responsiveness. But most of the serious apps had to be ported, and then the advantages just disappeared.

      Have you tried running Mozilla on BeOS? I mean, not a rotten old port of M18, but a recent build of Firefox. Yes, it's still being developed, and it's been getting a lot better. But its responsiveness is a lot worse than under Linux (not to mention the font rendering). Even when comparing a 266 MHz, 64 MB Powerbook running Linux to a 1.4 GHz, 256 MB Athlon XP running an RC of Zeta.

      But no, the PB can't run multiple videostreams. It has problems running just one. But video codecs have become much more demanding since the sub 200 MHz days. And so has computer use in general. Net+ was a small and simple browser, but it's practically useless these days, like all small and simple browsers are. You need features to do stuff, and stuff takes up space. That's why a small and simple OS is hopelessly outdated, and big and bloated environments like KDE (500 MB for a basic install?) and OS X (~2.5 GB for a basic install) are the future.
  • neat (Score:5, Interesting)

    by NanoGator ( 522640 ) on Sunday September 05, 2004 @02:56AM (#10161204) Homepage Journal
    " the event is expected to have a huge and lasting impact on the next major releases of the leading Linux and Unix desktop environment."

    I personally hope they are all having a good hard look at Apple's stuff. The main reason I'm not running Linux is that there's a lot of choice out there, and it shows. I hate running to Google every time I want to do something simple. Despite my many years of using Windows, I had no trouble using a Mac when the need arose.

    Anyway, sorry if that sounded like a rant. I'm just hoping some of the work that comes out of this gathering deals with the end-user experience. I'd love to get away from Windows.
    • You said you'd used Apples. And didn't mind them.

      So why not use them? OS X is easy to use, sure, but it's BSD under the hood, so it has more than enough to play with. ;-) Believe me, I know -- OS X user for almost a year (Linux was my main OS before that - I still use Linux for a small IRC server and some other minor projects).
      • Re:neat (Score:3, Insightful)

        by NanoGator ( 522640 )
        "So why not use them? OS X is easy to use, sure, but it's BSD under the hood, so it has more than enough to play with. ;-) Believe me, I know -- OS X user for almost a year (Linux was my main OS before that - I still use Linux for a small IRC server and some other minor projects)."

        I have given that a lot of thought, and I'm actually fairly close to it. There are a couple of hurdles, though:

        1.) My main machine is a TabletPC. I use it for drawing. To the best of my knowledge, Apple hasn't moved in that
        • Re. 1: Do you need to draw while standing around away from a desk or table? If not, you can just get a drawing tablet and a regular Mac desktop or laptop. Drawing tablets work with Macs too, you know -- and they have the best handwriting recognition also.

          Re. 2: They say Macs are usable longer than PCs (I haven't had mine long enough to find out yet). Also, when you get the urge to upgrade a component, stick the money you would spend in a jar (or an interest-bearing savings account) and then once you'v
          • Re:neat (Score:3, Interesting)

            by NanoGator ( 522640 )
            "Re. 1: Do you need to draw while standing around away from a desk or table? If not, you can just get a drawing tablet and a regular Mac desktop or laptop. Drawing tablets work with Macs too, you know -- and they have the best handwriting recognition also."

            I moved from a tablet to a TabletPC for a couple of reasons:

            1.) I wanted to be able to dry right on the screen. The only device I've seen that does that is a Wacom Cintiq, and those cost $2,500. Plus, they only run at 1280 by 1024. My TabletPC cost
            • "My TPC is only 1.5 ghz, and despite the fact that my main machine is a dual 2.0 athlon, it isn't significantly slower."

              Oops, I didn't clarify this very well. I meant that from a getting-work-done point of view, it isn't significantly faster.

              Sorry, I'm really bad at expressing myself sometimes.
            • Well, okay, but I still think you should consider an iBook or PowerBook -- after all, tablets aren't that big or heavy (right?); you can stack it on top [of the closed laptop] and take it with you.
              • "Well, okay, but I still think you should consider an iBook or PowerBook -- after all, tablets aren't that big or heavy (right?); you can stack it on top [of the closed laptop] and take it with you."

                Hehhe. The problem with stacking them is that it'd interfere with my tablet's configuration. It has two modes. Laptop mode and slate mode. I can either use it like an ordinary laptop, or flip the screen around on top so it looks like I'm carrying a small monitor. (and yes, it's very small.) Adhering an i
                • Naw, what I meant was just to take the drawing tablet along with the iBook, and set it next to it when you want to use it -- I didn't mean for glue to be involved! I just meant that a drawing tablet doesn't take up much space and you could put it next to the laptop in your bag.
                  • Oops sorry. Can ya tell I'm a little foggy tonight?

                    Unfortunately, I'm not sure what that'd buy me. I'm at a point right now where the OS is pretty much invisible to me. At least for the next 6 months until I need to reinstall. ;)

                    Don't worry man, next computer purchase I make, Mac'll be seriously considered.
    • I second Justin205 -- you should just use a Mac then! The only thing worse than a Mac fanboy is a Mac fanboy who doesn't actually have a Mac! (just kidding, really! I like my Mac)
    • Yea choice sucks, I mean who would want to choose what works best for them whether its a Mac, Windows, Linux running whatever, Solaris..., yea choice is the bane of software.

      Good thing you made your decision, getting away from Windows to Linux, just can't wait till someone shoe horns Linux into what you want, something like OS X it seems, if only there was something that you wouldn't have to wait so long for.
      • "yea choice is the bane of software."

        That's not quite where I was going, but actually yes, it can cause nasty problems. If there were 10 browsers (heh there probably is, good thing Firebird seems to be the de-facto default) for Linux all specialized at doing their own thing well, would that be good or bad? Well, let's see, web developers would have a hard time writing pages that'd conform to all of them, and there'd be a lot of noise on the web to the tune of "Which is best?!?!?" Choice good until ther
        • Re:neat (Score:2, Interesting)

          by RdsArts ( 667685 )

          That's not quite where I was going, but actually yes, it can cause nasty problems. If there were 10 browsers (heh there probably is, good thing Firebird seems to be the de-facto default) for Linux all specialized at doing their own thing well, would that be good or bad?

          Good. Guess what, not every app is a swiss army knife. Most shouldn't be. Users are different. This is why you have 2000 computer types and, wait for it, 2000 different type of people buying them. People's wants and needs differ. If there a

          • "But even with that said, you'll note that of the handful of browsers out there most use Gecko or KHTML. So they share backend code, which is good, but can do different things for the user, which is... Oh, ya, good."

            I like how you're agreeing in a disagreeing tone.

            • Top poster said there should only be one browser. (Firefox) I said there should be only few backends. Two entirely different comments.

              Unless Galeon, Firefox, Mozilla, Epiphany, Stepstone, Konqueror, Safari, gnuWebCore, et al suddenly merged.
              • "Top poster said there should only be one browser. "

                No, he didn't. If you actually understood what he said instead of arguing with what he didn't say, you'd find you're both pretty much on the same side. Your goal here is to argue, not to discuss.

                • If there were 10 browsers (heh

                  there probably is, good thing Firebird seems to be the de-facto default) for Linux all specialized at doing their own thing well, would that be good or bad?

                  From the top post. Direct quote with emphasis added. If me and the poster agree, rocking, it's just another post I've made that people can ignore. IMHO, we've one sticking point in that they want one browser and only one browser AFAI understand what they wrote, and for that to be the "standard." Which seems to be a common

        • Like choice is the bane of television?

          Does it really cause people nasty problems that there are over ten different manufacturers of NTSC decoding circuits, and over 100 different combinations of NTSC decoder and display device? Do people really find it difficult to produce content that conforms to all the combinations of NTSC receivers that exist?

          The problem in software is simply that we're not very good at producing software standards, or at keeping to them. If we had good standards properly implemented

    • by Hal XP ( 807364 )
      I personally hope they are all having a good hard look at Apple's stuff.

      The Gnome folks appear to be doing just that. I suspect Gnome is an attempt to clone the Mac UI (elegance over features) and KDE an attempt to clone the Windows UI (features over elegance).

      Take a look at the difference between Nautilus (the Gnome file manager) and Konqueror (the KDE file manager-cum-web browser).

      Nautilus is easier to use if all you want is to copy a file from one local "folder" to another. But if you want to copy a

      • by EdMack ( 626543 )
        Gnome's vfs lets you open local and remote filesystems identically, and copy between them. In Computer you can set up permanent connections for speed too.
      • by brunes69 ( 86786 ) <[slashdot] [at] [keirstead.org]> on Sunday September 05, 2004 @07:42AM (#10161724)
        It has to do with KDE's superior underlying IO subsystem, that Gnome is just starting to try to duplicate with VFS.

        The fact is with KDE you rarely would every *have* to copy the file over, since every KDE app can just access the file as if it was local anyways. You can edit a KWord document on an FTP/SFTP/WebDAV server just as easily as you can in your $HOME.
  • by Anonymous Coward
    From the GUI, OS, Drivers, Firmware, Hardware. Organisation is key to modularity. In case people haven't noticed, we've been slowly losing both in almost all technology nowadays.

    Also, the lack of modularity leads to more proprietary technology, which only increases the difficulty of defeating evil, evil DRM et cetera.

    Oh, it'd be nice if someone could point me to a good open source perfect 1:1 CD and DVD copying utility. CD protection is pissing off my ideas of Fair Use (I actually AM creating backups,
  • Krap... (Score:4, Funny)

    by Anonymous Coward on Sunday September 05, 2004 @03:05AM (#10161223)
    ...i missed it :-(
  • of the damn K. Stop putting in front of everything.
  • by Anonymous Coward on Sunday September 05, 2004 @03:25AM (#10161263)
    Now there are of course a lot of interesting things on could talk about. For example the integration of NX technology into kde, the new search feature, better integration between gnome and kde, the changes Qt4 might bring, etc.

    But unfortunatley these things won't be discussed on /.

    So, what can we expect?
    Easy, on one side we will see the old gnome vs. kde flame war.
    People will tell us that kde is bloated (of course without telling us what bloated means), that only gnome gets it right, etc.
    And some people will of course react in the same kind, telling us that gnome is unusable, that all the gnome devs are bad people, etc.
    For good meassure there will of course be someone telling us that anyone using anything with more features then twm is no real man and that real man only need the command line anyway.

    And of course there will be a lot of posts claiming linux isn't ready for the desktop.
    We will here that they had never had any problems with windows, that their XP install has been running happily on their PI 100 for 5 years now and that linux just doesn't cut it.
    And we will for sure see some expert telling us that it isn't ready because photoshop doesn't run on linux, as if everyone needed or even wanted photoshop.

    I could go on and on of course and people never cease to surprise me with the stupid topics they can come up with, but what annoys me most is that a lot of these incredibly boring and dumb posts will be modded interesting and insightful.

    Now there will probably be a lot of people filing me under linux zealot who can't stand anyone critizising his religion, but that is not the point here. There are of course a lot of things that could and should be better and yes, these things should be discussed, but that is something entirely different from the flaimbaits we can expect here.
  • by twener ( 603089 ) on Sunday September 05, 2004 @04:43AM (#10161402)
    The original posting [kde.org] which also includes the links to the archived video and audio recordings.
  • by Anonymous Coward
    Since it seems that Gnome 3 (from what I've heard anyway) is going to be coded mostly in C# via Mono does anyone know if KDE has any plans to move to a managed code solution?

    I'd like to see a natively compilable Java solution myself.
    • by Anonymous Coward

      Coding everything in C# would be ultimately stupid. I'm not sure if Miguel was misquoted there. I'd like to think that he's intelligent enough to understand how big a mistake that would be. I've been a GTK+ and C fan for years. Only recently I've started doing some application coding with Qt and C++. Boy, what a difference. The UI code was about half the size of the equivalent GTK+ code. I know you can use glade these days, but it should tell you something.

      Back to the KDE/Gnome thing, in my experience K

  • by Pecisk ( 688001 ) on Sunday September 05, 2004 @05:21AM (#10161467)
    because it has done many good things. Really, KDE and GNOME is for different user groups, so I really hate those all flamewars. I love GNOME and you love KDE. That's all and great - because it's all about choice. Someone else uses OS X, and someone else - some BSD flavor...

    What I really love to see that freedesktop.org starts to really matter for developers. I love that colobration stuff that we can share easily data without breaking each other goals.

    Remember, colobration and easy data migration between platforms is the key to the future of Linux *mainstream* destkop.

    And yes, kudos KDE team as always for superior translation tool - KBabel.
  • Am i right in thinking that kde 4 will start to use real transparenceny and shadows etc ala its own composite manager? since the current xorg manager is only proof of concept. I'm sure with a little time they can think of some innovative uses that don't just copy apple. any suggestions?

    i also think i heard that qt4 may be opengl accelerated which would be rather nice.

"May your future be limited only by your dreams." -- Christa McAuliffe

Working...