Slashdot Mirror


Linux Distributors Work Towards Desktop Standards

WebHostingGuy wrote to mention an MSNBC article discussing a move by several Linux distributors to standardize on a set of components for desktop versions of the operating system. From the article: "The standard created by the Free Standards Group should make it easier for developers to write applications that will work on Linux versions from different distributors. Linux has a firm foothold as an operating system for servers -- it's popular for hosting Web sites, for instance -- but has only a few percent of the desktop market."

42 of 247 comments (clear)

  1. Yea like they will ever agree with anything by jellomizer · · Score: 4, Insightful

    After the talk there will be 2 Major Faction. While one may win. The Second one will go Screw you and make their own design in-spite of the the talks. That is the problem with Ego Driven Software vs. Profit driven. While they both have their advantages and disadvantage. Ego Driven Software while the Code my be better quality but have a much harder time agreeing with other people. But Profit driven Software tends to be more consistent but software quality tends to be a little lower.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    1. Re:Yea like they will ever agree with anything by mugenjou · · Score: 3, Insightful

      and microsoft is a combination of both? they have the low quality of profit driven software as well as egoistic recreation/bastardization of standards just to be as incompatible as possible with the rest of the world.

      --
      DualBrain - Level Up Your Brain! - now available on your iPhone!
    2. Re:Yea like they will ever agree with anything by asuffield · · Score: 4, Insightful

      You're half right. The bit you got wrong is that the profit motive does not inspire people to produce consistent software. Most commercial software is just inconsistent, with everything around it and sometimes even with itself. This happens because each piece of software has a different project leader, and nobody in management above them understands enough to impose a single vision on the whole system. Given a choice, an individual project team will usually attempt to differentiate their project from all the others, in the hope of getting more money and/or recognition.

      So the conclusion is probably that different software created by different people is usually going to be different. That's probably a good thing and you should just get used to it. Nobody can invent a single way to do things that is right for every piece of software you might want to use in the future.

  2. reasons why by fl!ptop · · Score: 4, Interesting

    interesting that msn bills move as 'making the operating system compete better with windows' instead of 'making it easier for developers to write applications that work on different flavors.'

    i would think the former is a result of the latter, instead of the other way around.

    --
    When you recognize love in another and realize how precious it is, everything else seems so insignificant.
  3. I don't know what they are on about by MichaelSmith · · Score: 3, Informative

    I can run KDE applications under fvwm and Gnome, as long as the runtime libraries are there. I don't see why it is hard to have QT and GTK libraries on each system.

    The only remaining issue is cut and paste with rich content but the article doesn't talk about that.

    1. Re:I don't know what they are on about by jellomizer · · Score: 4, Insightful

      It is an issue of consistency. If I am running Gnome I know when I am running a KDE app because it looks a feels slightly off. The same if I am using a straight X11 App. Linux for the desktop is not about Window Managers. It is about giving Developers tools to make their Apps Desktop Friendly, And ability to make sure Linux Apps look good no matter what WM you are using.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:I don't know what they are on about by moro_666 · · Score: 2, Insightful

      i wouldn't start my kde if it would look and behave like gnome ;)

        now about the `issue` itself, redhat is dragging along a bunch of people to push some kind of one-standard-for-all (cough-cough-bs-cough-cough-profite-cough). they want to unify some things (the article didn't really elaborate what ...), and therefor make all the stuff more the same.

        i don't know about you, but if i'd want everything to look the same, i could aswell choose osx or winblows (nah, not really win, it's not ...). i chose linux many years ago because i wanted it to behave like i want it to and to look like i want it to. i don't want my desktop to look'n'feel like it suits a redhat salesman.

        i understand that this will help to push linux into the streets blabla, but is this really what we all want ? or is this the beginning of the end of linux as we know it ?

        we have seen many items out on the `market` that were supposed to unify and standardize linux (various package managers etc.), none of them have succeeded. for the broadband, i hope it succeeds, for my own's sake, i hope they fail terribly and give it up.

      --

      I'd tell you the chances of this story being a dupe, but you wouldn't like it.
    3. Re:I don't know what they are on about by Homology · · Score: 2, Interesting
      I don't see why it is hard to have QT and GTK libraries on each system.

      Because: - its ugly design

      It's not an issue of bad design, but of neccessity. As long as different applications are using different libraries, you end up installing those libraries.

      - it involves lots of code duplication

      There is no code duplication involved, however, there is some overlap of functionality

      - it sucks on lean platforms (for example Maemo)

      If your computer is very limited, then you don't want to run either KDE or GNOME.

      - it doubles your chances of being hit by a security flaw

      Care to elaborate on that?

      - it produces a lot of unmaintained basic infrastucture code (like VFS) where the implementation is the spec.

      Just because some random Linux distro is offering both KDE and GNOME does not imply that KDE or GNOME stops maintaining their own code.

      - standards are a Good Thing

      Yeah, yeah, sure. Except when the "standards" sucks.

    4. Re:I don't know what they are on about by IamTheRealMike · · Score: 2, Insightful
      The standards in question are things like "how do I install a menu item in a way that works across distributions" and "how do I distribute C++ apps in ways that don't randomly crash" and "what libraries can I expect a Linux system to have".

      The whole "as long as the runtime libraries are there" catch is what it's all about. It's not reasonable to expect people to deal with dependencies.

    5. Re:I don't know what they are on about by Homology · · Score: 2, Insightful
      The whole "as long as the runtime libraries are there" catch is what it's all about. It's not reasonable to expect people to deal with dependencies.

      It's the package maintainers job to deal with library dependencies. I a Linux distro is unwilling to do this, why should I use it in the first place since it is obiously of low quality?

    6. Re:I don't know what they are on about by wysiwia · · Score: 3, Informative

      Or say it with a single statement:

      "It's the first top inhibitor of the Linux desktop adoption"

      See http://www.osdl.org/dtl/DTL_Survey_Report_Nov2005. pdf

      and http://linux.slashdot.org/comments.pl?sid=183801&c id=15179906

      O. Wyss

      --
      See http://wyoguide.sf.net/papers/Cross-platform.html
  4. I have to ask... by MobileTatsu-NJG · · Score: 3, Interesting

    This question is going to seem rude, and I apologize for this, but why didn't this happen years ago? I'm asking out of curiosity, not as a jab at the community. It seems to me that this sort of standard would have been quite valuable as soon as GUIs became prevalent with Linux.

    --

    "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    1. Re:I have to ask... by Pneuma+ROCKS · · Score: 4, Insightful

      I think GUI, despite being prevalent for quite some time, have been very, very low in the priority list of Linux developers. The community has focused more on the low-level, kernel and architecture areas, and the rest has suffered from it. IMO, GUIs in Linux have always been an afterthought, and that's the reason they suck so much (again, IMO).

      This sheds light in a key problem with open-source software: developers will work in what they want to work, not necessaily in what needs to be done.

      Yeah, mod me down, see if I care.

      --
      Favorite quote: "
    2. Re:I have to ask... by Kjella · · Score: 2, Insightful

      Well, if I get to pick my preference it goes like this:

      1. Make it work
      2. Make it work well
      3. Make it work fast
      4. Make it work fancy

      Besides, I don't think it's wrong to say that for many Linux has been and is only a server OS and they couldn't really care about a GUI. But somehow I get the impression that those most deeply into inner mechanics of kernels and drivers might not be the most qualified to make good GUIs either, so I'm not sure it's suffered that much. And even so, GUIs are really subjective and hard to make an authoritative source for, my impression is that OSS has focused more on flexibility than design. For example, look into some of the "photoshopifier" plugins of GIMP. They basicly redo the entire UI. So go ahead, come with your suggestion for a good UI - my bet is it'll be quite different from someone else's idea of the same.

      --
      Live today, because you never know what tomorrow brings
  5. "One big things that's difficult is consistency" by wysiwia · · Score: 2, Informative

    Yes and consistency can only be achieve by standardizing. Unfortunately this doesn't only hold true for the desktop, it's equally or even more important for the applications. So far Jim Zemlin, executive director of the Free Standards Group, doesn't seem to realize this else the FSG would have already standardized on a single set of application guidelines as outlined in wyoGuide (http://wyoguide.sf.net/). Since this isn't the case so far we still have to wait for the breakthrough of the Linux desktop.

    If anybody is interested in a Linux desktop and don't want to wait much longer, he should persuade the FSG to come to terms and at least delve and evaluate wyoGuide.

    See also http://lxer.com/module/newswire/view/54009/index.h tml

    O. Wyss

    --
    See http://wyoguide.sf.net/papers/Cross-platform.html
  6. Finally! by yootje · · Score: 3, Interesting

    What Linux needs is standardization. Having 921034 options to choose from is sometimes a good thing, but sometimes you have the feeling: why don't they just work all on 1 fantastic piece of software?

    1. Re:Finally! by Coryoth · · Score: 5, Insightful

      Having 921034 options to choose from is sometimes a good thing, but sometimes you have the feeling: why don't they just work all on 1 fantastic piece of software?

      Because the worlds open source developers are not a giant slave pool designed to do your bidding.

      Open source will always be chaotic and involve a great deal of duplication because that's that nature of the beast. The gain you get from that cost is much more open software that's developed rapidly and tends to work as a free market for ideas: the better ideas eventually win out (though that may take some time). If you want something different then you want Apple or Micrsoft with their rigid top down control structure which ensures that everyone is working toward a single unified goal (as much as is possible), and all the work is directed. The upside is consistency and a unified vision, but the downside is that the whole thing is more locked up, an often slower development cycle, and a tendency to get hit with the same stupid mistakes release after release after release just because it appeals to the guy at the top.

      It's a choice and you can pick the software ecology that suits your needs. Just don't go expecting one to behave like the other on your whim - there are deep fundamental philosophical divisions about how to develop software (to let it evolve from the bottom up, or direct it from the top down) that are largely irreconcilable.

      Jedidiah.

    2. Re:Finally! by JanneM · · Score: 3, Insightful

      why don't they just work all on 1 fantastic piece of software?

      Because there is no one answer to what makes a piece of software fantastic.

      When intelligent people can reasonably disagree on it, don't be surprised - or dismayed - when the end result is several divergent designs. That is truly a case where any one of the designs are good, and importantly, better than a compromise between them.

      --
      Trust the Computer. The Computer is your friend.
    3. Re:Finally! by TERdON · · Score: 5, Insightful

      why don't they just work all on 1 fantastic piece of software?

      Because there couldn't be such a thing - it's an oxymoron.

      Basically, the requirements of the piece of software would be heavily contradictory - dead-easy to use, but still incredibly powerful. Few such programs exist - because they are virtually impossible to make.

      Example: file managers. On the one hand, you have explorer, finder, nautilus et al, which all are at least relatively easy to use even for a newbie. Many find them far to little powerful, especially on /., where the favourite probably is raw /bin/bash, which is far more powerful, but also really hard to learn.

      The same principle holds for most other software. Either you make an easily usable, or a powerful version. The powerful version will, by definition, need a lot of learning on the part of the users, and thus can't be easily usable.

      When you try to unite these two conflicting requirements, the most likely outcome is one of:

      1) Cluttered interface, which intimidates the newcomer
      2) Clean interface, but with all powerful features hidden away from sight so the advanced user has to look for them.
      3) Millions of settings in an unmanagable settings dialog, toggling the different features on and off.

      Conclusion: One software normally can't be the great software - not for every single user. The shifting requirements different individuals have will without doubt make them prefer different software - and that isn't really a bad thing. If everybody ran the same software, there wouldn't be as much incitement for developing new, powerful features!

      --
      I have a really elegant proof for Fermat's last theorem. If this sig was only a bit longer...
  7. On the desktop and haven't looked back... by i_want_you_to_throw_ · · Score: 3, Informative

    I have tried using Linux on the desktop MANY MANY times and always found myself stymied by getting printers to work and so forth. I have always been adamanat about using it for servers where it's very much worth the time to figure out Linux to have the benefits of it as a server product (bulletproof security, etc).
    As a desktop product though I wasn't about to spend all day dicking around with trying to get it to work. That's was then.... this is now...

    I have been using Linux as a desktop for several months now and it has flawlessly detected all my perpherals, and I Have now been able to spend more time doing development which is what I get paid to do.

    Linux is getting better in this area and Linux is going to start making inroads. Slowly but surely...

  8. Standards wont make a difference by gimpimp · · Score: 3, Insightful

    We've had standards bodies for a long time. LSB, Freedesktop, etc - none of will help increase market share. Sure, they make like easier for developers, ie a gnome icon theme will soon work on a kde desktop. But the single major problem on linux is dependancy hell. I have nightmares about this.

    Repository based installation is NOT the way to go. Autopackage is just a pretty frontend around the same problem. Until we can install and remove applications as easily as OSX users can, we don't stand a chance.

    If you were a new user to unix, what would you prefer:
    A) open synaptic, search the thousands of packages, hope you find what you're after, install it.
    B) download an app folder, drag it to your appliactions folder. go.

    Without this ease of use, there's no chance. I still laugh at people who say linux is ready, whilst at the same time they can't install the latest firefox on their box because it depends on the latest gtk which depends on the latest glib, which depends on....

    --
    i wish i was but oh well
    1. Re:Standards wont make a difference by IamTheRealMike · · Score: 4, Insightful
      Repository based installation is NOT the way to go. Autopackage is just a pretty frontend around the same problem.

      Well, autopackage was designed to deal with many of the problems repository based distribution has, so, I would strongly disagree with the notion that it's just "a pretty frontend around the same problem". We've put many, many times more effort into things like reliable/easy installs than making it pretty (though there is still much to do).

      Without this ease of use, there's no chance. I still laugh at people who say linux is ready, whilst at the same time they can't install the latest firefox on their box because it depends on the latest gtk which depends on the latest glib, which depends on....

      This problem affects any OS. You can't install Safari on MacOS X 10.1 either, if I remember correctly. It's true that Linux suffers this problem worst of all though, because there's no unified platform, and because there's no profit motive so little incentive for developers to go "the extra mile" to reduce system requirements. But it's a separate (though related) problem to how you install software.

    2. Re:Standards wont make a difference by Florian · · Score: 3, Interesting
      download an app folder, drag it to your appliactions folder. go.
      Unfortunately not. OS X programs often spread their files all over the file system, with a mess of binary configuration files, possible netinfo entries (akin to the Windows registry...), etc. There is no standard method in OS X to cleanly remove them - just deleting the application won't do the trick in most cases. Even Windows is superior in that respect.

      Besides, downloading binary code somewhere from the Internet and installing it in your system is a security nightmare and practice that should be abandoned ASAP. I find the Linux/BSD model of providing all software in distribution-provided repositories blessed by the distribution's maintainers vastly superior to OS X, with unmatched clean and safe installation, removal and upgrading of software. (How, for example, do you upgrade all your Mac OS X software with one command or click?) I use both Debian and Mac OS X and find Debian vastly superior in this respect.

      --
      gopher://cramer.plaintext.cc http://cramer.plaintext.cc:70
    3. Re:Standards wont make a difference by tomstdenis · · Score: 2, Insightful

      I dunno. I don't subscribe to the dumificiation of humanity. I agree that things shouldn't be harder than they need to be. But it isn't like "emerge -uD firefox" is so fucking hard to type. I mean look at how many people can hardly use Windows as it is. I think the trend should move towards "let's document our system and stick to standards".

      Remember the days of the 200-page MS-DOS 5.0 user manual showing off all the commands with examples? What happened to that? For $300 [full XP pro] you think they could include a 100-page primer on using Windows. I mean it isn't like the CD cost them $300 and when they fully admit they're making money hand over fist you think customers have a right to demand more.

      It isn't like there are not Linux books though. So if the user has to learn how to user their computer is that really so bad? It means they get better use of it and are not at someone elses mercy as to what they can run and how. I think that's a good thing. I could be wrong...

      Tom

      --
      Someday, I'll have a real sig.
    4. Re:Standards wont make a difference by i_should_be_working · · Score: 3, Informative

      If you were a new user to unix, what would you prefer:
      A) open synaptic, search the thousands of packages, hope you find what you're after, install it.
      B) download an app folder, drag it to your appliactions folder. go.


      You forgot the part in B) where you search through the internet for the home page of the application. Then you read the home page trying to find out how to download it. Once you see the "download" link you go through a couple of pages asking you what version you want and what mirror you want to use. Then after waiting for the download you finally start the actuall installation.

      Whereas with A) it's more like: Open Synaptic, use the search field to find the app faster than you would on the net, install it.

      I prefer option A. It's more convinient for me and the repository based system has other benefits I'd rather not do without. I can see where you are coming from, but different people prefer different things. I'm just glad the distros agree with me (or rather I agree with them).

      And for the record, it's not the distribution or Linux devs who are stopping app folders from coming to GNU/Linux. They already exist. Nothing stops someone from bundling everything a program needs in a self-contained folder. That's how most of the proprietary apps I use are packaged. Open source devs could do this with their programs too, but it would be more effort without much benefit when the distros are going to package it anyway.

    5. Re:Standards wont make a difference by baadger · · Score: 2, Informative

      I agree.

      You know sometimes I wish I could just goto Help -> Check for Updates in Firefox on Linux as easily as I can on MS Windows. It's laughable that the most well known of open source software doesn't function as seemlessly on an open source operating system as it does on a proprietary Microsoft one.

      Hell, if my repository doesn't have the latest version of Opera (it doesn't) I say sod it and get it from the source, run Opera's 'install.sh' and i'm happy if it works (it does). Yet, theres no safe way to uninstall or manage that installation thereafter.

      Microsoft's registry and filesystem arrangement isn't as pure as us geeks would like, everything thrown in a single 'Program Files' folder, the start menu and registry practically pissed upon, user documents stored in a subfolder of the user profile and settings folder on the same partition as the operating system ecetera ecetera.

      The fact is though on Linux, you're forced to engage with the community to get what you want in the repositories, rely on using the distro flavour of the month to get the best choice, or get down and dirty with configure, make and the filesystem yourself. Some people never want to have to do *any* of that, and they shouldn't have to. How anyone can claim Linux will every make it to the average mom's desktop, without constant nannying by a geek (and yes lots of Windows users struggle by without one, and the spyware awareness situation is improving), unless they address these issues is just funny.

    6. Re:Standards wont make a difference by javanree · · Score: 3, Informative
      This might have been an issue years ago, but these days there isn't any serious "dependancy hell" anymore. Tools like yum sort that out. As long as you pick a sane combination of repositories things will "just work"
      For Fedora (only one I'm familiar with), there's freshrpms , Dag and a few others that work great. For the distro I use (CentOS) I maintain my own repository, so all other users just have to click to get what they need.

      And if you want one-click install, have a look at Klik, which is now available for many distro's already. Although I personally prefer RPM's (since it's easier to clean/upgrade) it's a good idea for novice users.

      Things like LSB and freedesktop ARE making a difference, although some of it might not (yet?) be visible on the surface.

    7. Re:Standards wont make a difference by cozziewozzie · · Score: 3, Informative

      Repository based installation is NOT the way to go. Autopackage is just a pretty frontend around the same problem. Until we can install and remove applications as easily as OSX users can, we don't stand a chance.

      We can do this already: Klik

      The problem is that you end up with 200 versions of the same libraries, and the resulting memory and disk space overhead.

      That's why this sort of installation is generally used for easy testing of things instead of a sane installation procedure.

    8. Re:Standards wont make a difference by asuffield · · Score: 4, Insightful

      Nothing stops someone from bundling everything a program needs in a self-contained folder. That's how most of the proprietary apps I use are packaged. Open source devs could do this with their programs too, but it would be more effort without much benefit when the distros are going to package it anyway.

      Actually, it's not because it's more effort. It's because it is fundamentally a bad idea.

      If you bundle everything you need into one blob for each application, then suddenly your system has installed several hundred copies of gtk, all at different versions. Obviously this is quite wasteful of space, but even that is not the real problem. This is:

      A security advisory was just released for all copies of gtk before a given version.

      What exactly do you do now? You don't know which of your hundreds of applications has got that code included in it. Even if you could figure it out, you now have to either rebuild all of those by hand (if you can), or go to each individual upstream developer and download an updated version from them. If you're a desktop user then you probably aren't going to get this done, so you'll be running with known security holes in some applications. If you're a sysadmin then you're probably going to find a new job.

      I would say that the ability to install security updates in a reasonably painless and secure manner is one of the most fundamental tests of any distrbution method. Applications-as-self-contained-blobs fails it badly.

    9. Re:Standards wont make a difference by zerblat · · Score: 2, Informative
      You know sometimes I wish I could just goto Help -> Check for Updates in Firefox on Linux as easily as I can on MS Windows.
      If you're using Ubuntu, Update Manager will take care of the updating for you. You don't even have to ask it to check for updates, it does that automatically and notifies you if there are any updates. Plus, it works the same for all of your software, not just one application.

      Other distros have similar things.

      --
      Please alter my pants as fashion dictates.
    10. Re:Standards wont make a difference by tal197 · · Score: 2, Interesting
      Repository based installation is NOT the way to go. Autopackage is just a pretty frontend around the same problem. Until we can install and remove applications as easily as OSX users can, we don't stand a chance.

      You already can: 0install.net. More easily, in fact, because Linux will automatically fetch the dependencies and check for updates. Things have moved on since the days of centralised APT repositories where you have to be root just to install something.

      Take a look at the screenshots!

    11. Re:Standards wont make a difference by Rich0 · · Score: 2, Informative

      Couple of things -

      1. On windows the bundled DLLs definitely cause problems. I'm sure I still have PCs in my home which are vulnerable to that gif/jpg/whatever vulnerability that came out a year ago or so (the one where the flaw was in a series of DLLs that got bundled and repackaged with just about everything). On linux you use shared libs (which support multiple installed versions) and you can dodge this mess.

      2. The .so setup on linux is designed so that you can have multiple versions of the same library installed (thus discouraging every app from just keeping their own private copies). In theory if two verisons are compatible you can just symlink them. In any case, as long as you run configure it should link the app against the appropriate library version - the problem only comes when you go to install binary software without using a packaging system of some sort.

  9. Why doth the rumours continue? by Psychotria · · Score: 4, Insightful

    Unfortunately, those added software libraries differ among Linux distributors, making it hard to know if an application like a word processor will function on a particular Linux computer.

    What a load of rubbish...

    When I read a comment like this, I have to question a) the qualifications of the article author; and/or b) their motives. Any assertions made in the article need to be critically examined and their validity questioned after such false hoohah.

  10. Standard don't remove freedom by MarkByers · · Score: 3, Insightful

    i understand that this will help to push linux into the streets blabla, but is this really what we all want ? or is this the beginning of the end of linux as we know it ?

    No. There will always be distributions that do it their own way despite what any standards organisations say. You will always be free to use these distributions. No-one can force standards into Free software (if you try, people can fork), but you can make the standards so good that distributions (and their users) want them. If people don't want them, they won't be successful.

    --
    I'll probably be modded down for this...
  11. ONLY a few percent? by penguin-collective · · Score: 5, Insightful

    A few percent desktop marketshare is what Macintosh has. Seems to me that the "fractured" Linux desktop is doing pretty well already.

  12. Re: I'll take A! - Repositories are The Answer by anon+mouse-cow-aard · · Score: 2, Interesting
    If you were a new user to unix, what would you prefer: A) open synaptic, search the thousands of packages, hope you find what you're after, install it. B) download an app folder, drag it to your appliactions folder. go. download from where? How did you find the place to download from? You did a google to find it first, on what term? the name of the software? the purpose? If the first step is to do a search in synaptic (btw... Adept in ubuntu is nicer) that looks only for packages for your distro, version, and architecture. It is far simpler. And from now on, all your security updates are applied automatically, so the user does not have to worry about the latest and greatest.
    • A) is more:
      1. Start up a software repository browser. (Click'n'run, Adept, Synaptic, whatever)
      2. Do a reasonable search, to find the package, read among a few descriptions.
      3. click on the install button. (which downloads and installs.)
    • B) is more like:
      1. google search to find the web site of the software.
      2. figure out where the download link is.
      3. Try to figure out which package is correct for the computer (This step completely defeats most ordinary folks.)
      4. Download it somewhere... (OK, it's on my desktop, now what do I do with this package thing?)
      5. drag it into the applications folder (That assumes that you know what an applications folder is... again, inexperienced people will not know or worry.)

    Folks hear about downloading, and expect to download, and application developers find packaging a pain, a barrier to distribution, but once people look at it critically, it is really about what people are used to, not about what works better. Downloading random packages off the net is a bad idea on any OS. Getting supported packages from a repository that tracks your OS is the right idea. Vendors of proprietary software should (and the good news is that many are) simply provide repositories for distros that provide for this kind of automatic updating.

    People who say that repositories are not uptodate are not reasonable. Most people want software that has undergone some testing, want software to update itself automatically once it is installed, want the correct version for their system to be chosen automatically (i.e. asking people to be able to answer the question "on glibc 2.1 based distributions..." is too much.) The the software provider cannot find the time to perform proper packaging, and will not arrange for updates to be easy to do when there are security issues or improvements available, then you should not install the software unless you are prepared to do that sort of support on your own. That is a choice that most people do not think about.

    Making repositories easier to deal with is the thing to concentrate on. For example, A missing piece right now would be to have an XML ''download selector'' which would contain a list of repositories for various distros, that frontends for apt/yum/whatever could just download and automatically select the appropriate repository for a given distribution. ISV's would just create the XML file (and the requisite repositories behind them.) And the whole manual download/install process would disappear. That would be a big end user improvement with only a small change existing tools.

  13. Cynicism is popular on /., but not always right by swillden · · Score: 4, Interesting

    After the talk there will be 2 Major Faction. While one may win. The Second one will go Screw you and make their own design in-spite of the the talks.

    History disagrees. While the Linux Standards Base and Freedesktop.org projects haven't solved all of the problems -- and probably aren't fully adhered to by any distribution -- they have already made a huge difference in the compatibility of Linux distributions, and I think efforts like this are exactly what we need to continue pushing interoperability forward.

    I say this, by the way, as a developer who just finished developing a cross-platform, commercial, binary-only application for Linux. The app I was working on definitely pushed the limits of the interoperability, since it was an authentication system that replaced key system components, and in spite of that it went very smoothly. The differences between the half-dozen Linux distros I had to tweak the package for were very small. Actually, the more difficult issue was making things work in spite of customizations the admin may have made -- I just had to punt on that one, making the installer intentionally brittle in the face of unanticipated modifications to, for example, the X startup scripts, and then providing the admin with the ability to customize the installer to adapt to local changes.

    After my experience of the last year, I wouldn't have any hesitation about developing more "normal" applications to run on multiple Linux platforms, and I expect initiatives like this one (which is from the same consortium that brought us LSB) will continue to reduce the platform differences that cause problems. I think we may even be able to get to the point where app developers may actually be able to target LSB (or whatever its successor is called) rather than having to tweak for individual distributions.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  14. you mean... by penguin-collective · · Score: 2, Insightful

    You mean like in the commercial world, the Apple faction said "screw you" to the Microsoft/IBM faction and did everything their own way? Or like the MS Office group said "screw you" to both the MFC and Vista groups and keeps violating GUI guidelines on Windows? Or like Mac developers can't agree on a consistent toolkit (there are half a dozen different ones in common use), consistent look, or consistent installer?

    It's good that the Linux desktop is being unified further, but it certainly has to fear no comparison with other platforms. You can start complaining again once Apple and Microsoft sit down together and decide on a consistent place for the menu bar. (KDE at least gives you a choice.)

  15. Real news at the end of TFA by standbypowerguy · · Score: 3, Interesting

    At the end of TFA I found the following quote: "Installation by the user is easy..." Imagine that! An acknowledgement that linux installation is easy published in a major media outlet. Hopefully, this will encourage some folks to try linux. Installation of any OS may be beyond the "joe sixpack" crowd, but IMHO, most linux distros' installation routines now rival or exceed Windows' simplicity, and you don't have to type in a long, cryptic CD key ;-)

    --
    This isn't the sig you're looking for... Move along.
  16. Cut & Paste by xerxesdaphat · · Score: 2, Insightful

    Hang on, hang on... cut & paste? I know ctrl-v doesn't always work, but I haven't found one app in which good old middle mouse button doesn't work. Maybe I've just been lucky and not tried to use it when it doesn't work, but hell middle-mouse even works from firefox to vi. And at least for me, I prefer middle-mouse button anyway... ctrl-v also requires ctrl-c in addition to selecting the text. And as far as it being preferable due to it being a keyboard shortcut, well cut & paste is largely a GUI thing anyway (vi has it's own built-in cut & paste thing of course) so you're likely to be using the mouse and you got to use it to select text anyway.

    Please correct me if middle-mouse is not universal.

    --
    The Shoes of the Fisherman's Wife Are Some Jive Ass Slippers
  17. Re:"One big things that's difficult is consistency by PitaBred · · Score: 2, Insightful

    Because unpopular software on Windows like Winamp religiously follows the Windows design guidelines . How the hell did this blatant turfing for his own, really tangental site, get modded up? People will deal with new and non-standard apps quite well for the most part. This isn't about the interface presented to the user, it's about the parts that are common to all desktops like menus and hooks to the WM.

  18. UNIX wars redux by Danathar · · Score: 3, Interesting

    I love LINUX...use it...endorce it...but...

    The fact of the matter is, NOT having standardized methods for things like graphical installation of software (like MS installer) is a BIG drag on desktop adoption.

    Having so many linux distros is good for competition between distros and innovation, but horrible for commercial software vendors wanting to create products that will be bought by many people.

    Graphical installers that pull software from repositories are still (generally) too complicated. I have to hand-hack X11 config files to get multi-monitor configurations to work. Stuff still just does not work "out of the box" as well as windoze in many important respects.

    Get ready...if Apple ever decides to use the LINUX kernel (unlikely) it should put a WHOLE lot of pressure on LINUX distros to clean up their acts.

    you can flame me now...I have my asbestos fire suit on