Slashdot Mirror


Could Apple's Intel Desktop Threaten Linux?

esavard writes " If Linux enthusiasts don't want Mac OSX on Intel to become a threat for the future of Linux Desktop, they must rethink the concept of Desktop as we know it today. Symphony OS did exactly that and propose some fresh concepts about how a desktop should and should not be. If you want to know more about Symphony OS, a good starting point is a Wikipedia article describing the innovations proposed by this new desktop OS. The Linux Desktop Community must encourage such initatives massively to compete against Mac OSX and Windows."

818 comments

  1. Beautiful by AKAImBatman · · Score: 5, Insightful

    After looking at the screenshots, allow me to be the first to say: Wow. That's so beautiful, it brought a tear to my eye.

    The one thing that stands out at me is that Symphony uses Yet Another(TM) packaging system that is supposed to fix all the woes of the previous packaging system. Haven't we learned yet? In a complex system, packages are just as bad (actually worse) for users than DLL Hell. And they certainly don't solve the issue of maintaining the sanctity of applications, and maintaining file associations across deletes/manual installs/program moves. These are some of the greatest break points in the Windows OS. Yet Mac OS X has none of these problems thanks to its amazing .APP application scheme, and IOKit interface which tracks files by INode instead of path.

    Under OS X, installation consists of downloading the application, and optionally extracting it from an archive. That's it, nothing more. You can run the app from any location (although the "standard" is the Applications folder), including right out of the DMG archive! File associations are easy: Just have the program on your hard drive. That's it! The OS takes care of querying the program for its associations. If you move the program, the OS knows. And if you delete the program, the OS removes the association. No mucking around with manual configuration. The *only* thing you can change is the default program!

    Given that OS X has shown us the power of this method, why haven't any distros latched onto it? Yes, it means that the OS must promise a base set of shared libraries, but the user experience is so much better!

    1. Re:Beautiful by Professor_UNIX · · Score: 3, Informative
      Given that OS X has shown us the power of this method, why haven't any distros latched onto it? Yes, it means that the OS must promise a base set of shared libraries, but the user experience is so much better!

      Well, you can get a similar experience by using static binaries. They have the libraries compiled into the binary and have no other dependencies. The downside is increased disk and memory footprint. Also if there is a vulnerability in the library it uses the entire binary must be recompiled. Personally I like the way the .APP structure works and it's easy to backup programs that use that structure. I remember having some program though that didn't and insisted on installing thousands of files from a sit archive or something. I think it was Windows Media Player.. the version before the current one for MacOS X. Seems much more efficient to distribute a single .dmg file with your APP binary directory structure in that.

    2. Re:Beautiful by antiMStroll · · Score: 0, Troll

      By the standard applied above Win XP's 'package manager' isn't ready for the desktop, which has been proven untrue hundreds of millions of times. Draw your own conclusions about the standard being applied.

    3. Re:Beautiful by dabadab · · Score: 3, Informative

      "[i]In a complex system, packages are just as bad (actually worse) for users than DLL Hell.[/i]"

      I think you have missed something.

      Packages are a GREAT way to handle things.
      The simple & dumb way as OS X handles packages is just that: it can not handle dependencies, or anything, it just puts some files on your computer.
      It works moderately well, if you only use it for applications and those are statically linked, but nothing else.
      Now, take Debian's package system: it handles dependencies, version conflicts, alternative packages that serve the same purpose, etc, etc, ec. And it is absolutely easy: an apt-get install xyz installs/updates package xyz and all the necessary shared libs, updates file associations, whatever (and it does not takes exactly rocket science to create some GUI for that single command line).

      --
      Real life is overrated.
    4. Re:Beautiful by Bruce+Perens · · Score: 4, Informative

      The main problem with package management is managing dependencies upon other packages. The installation system you write about is elegant, but you don't describe how (or if) it fixes that problem. Most naive-user packaging systems fix the problem by including the kitchen sink (all applicable DLLs) in their own package to reduce dependencies. Debian's package system works fine for their users because there is one huge repository with management of the proper cross-dependencies within that repository, rather than many repositories with little coordination. Once you add repositories, they go out of phase and the problems pop up.

    5. Re:Beautiful by m50d · · Score: 1

      There's already gnustep using exactly that package system. (Well at the moment most gnustep .apps are simply folders, but I think that's very easy to change). Look at how popular it is.

      --
      I am trolling
    6. Re:Beautiful by AKAImBatman · · Score: 4, Interesting

      By the standard applied above Win XP's 'package manager' isn't ready for the desktop

      Ok, for one, that's just putting words in my mouth. I never said that any package systems "were not ready for the desktop". I said that package systems create a dependency hell in complex systems that's just as bad as DLL Hell.

      Secondly, my post pointed out that Windows tends to fall flat with mislinked associations, broken application, and other "minor" issues that are quite annoying to users.

      Thirdly, *what* Windows XP package manager? The closest thing Microsoft has to such a beast is the MSI format. And that's not so much a package format (where package format is defined as a standard structure to track dependencies and thus maintain system integrity) as it is a standardized installer archive. And even then, I've met a couple of programs that I couldn't install because something was screwed up in the checks done by the MSI or Installer program.

    7. Re:Beautiful by DenDave · · Score: 2, Interesting

      I think that x86 Mac is attempting to threaten Linux. Apple is a very Linux unfriendly company with no moves to support anything that smells like linux. rather they are pushing their Open Source concept Darwin. Marklar (secret OSX/X86) program has reportedly fed enormously on the Darwin project and will continue to do so. By pushing their apps on a mass market platform it is obvious that the Apple digital lifestyle (iLife etc..) is coming to a Joe Bloe near you. Whether they will succeed to put a dent in Linux remains to be seen. For many commercial users OSX on X86 will be a great alternative for Windows and that is the main market. I would suggest to many x86 users to consider the move sincerely. However, as a recent x86/linux to Mac/PPC switcher I must say I am unhappy as I feel left in the cold. Not only has Linux/OpenSource on PPC been a slow mover, it now looks dead in the water. All future developement will be on x86 and even Bill Fink will have to acknowledge that much of his efforts have been in vain.

      Oh well, my macs will be up for grabs (to be shoved up Stevo's you-know-what) as I move back to Fedora on 64bit.. I wanted OSX because it was 64 bit and Open Source.. I was a sucker, I believed the marketing ... OSx's future is 32 bit and not nearly as OpenSource as their drumbeating would suggest..Why heck even Linus was using a PPC64...

      --
      -if at first you don't succeed, stay the heck away from paragliding.
    8. Re:Beautiful by Anonymous Coward · · Score: 1, Insightful

      > Given that OS X has shown us the power of this method, why haven't any distros latched onto it?

      Well, that power was already avalaible in NeXTstep. I remember arguing in slashdot nearly 10 years ago about that, and 5 years ago with Mac OS 9 zealots.

      It is such a simple a great idea. An application is a directory. The GUI treat it as a single object.

      But techies don't like it because it is quite conceptually simlar to static linking (the same lib will end up beeing several time in memory). And it is such a simple idea...

      And OS 9 junkies hated the fact that this mecanism is based on the file extension...

      And of course, *all* the UI have to agree about that, because it is a user-land illusion. Good luck getting gnome, kde agreeing on that...

    9. Re:Beautiful by grumbel · · Score: 1
      ### Given that OS X has shown us the power of this method, why haven't any distros latched onto it?

      Rox and the Zero Install System provide that. I was quite stunned the first time when I drag&dropped a Rox Applet on my panel and saw a XTerm poping up that automagically run the compile for the Applet.

    10. Re:Beautiful by Anonymous Coward · · Score: 0

      Are you kidding? Hideous Mickey Mouse candy-looking garbage.

    11. Re:Beautiful by ssj_195 · · Score: 2, Insightful
      why haven't any distros latched onto it? Yes, it means that the OS must promise a base set of shared libraries
      You just answered your own question :) Seriously, the need to guarantee the presence of a basic toolkit is the only real obstacle here - the rest is pretty much cake - just add a GUI wrapper around dpkg/ whatever such that the act of dragging an app somewhere installs it at the given place; create some kind of meta-deb/ RPM that contains its dependencies as sub-debs that are installed as a shared library if they are not already present (no real need for big, statically linked binaries, I don't think...?), etc. Personally, I haven't had any trouble with file associations, so I'm not sure if this is a hurdle - I think the .desktop spec solved this a while ago. Most of the basic tools are already in place, except for this "meta-debs", but these would be easy to implement, if the community showed interest, and given automated tools would spread across pretty much every active project in the OSS world.

      So the major problems here would be settling on some kind of Linux Standard Desktop Base of libraries, and persuading the community that "meta-debs" are a good idea.

    12. Re:Beautiful by lotsToLearn · · Score: 1

      I for one dont like the four icons on the corners... yes they look beautiful but how do i get to them when i m running my programs maximized say...

    13. Re:Beautiful by deacon · · Score: 1
      Under OS X, installation consists of downloading the application, and optionally extracting it from an archive. That's it, nothing more.

      Interesting. Perhaps someday OS X will catch up with Synaptic (based on apt) package manager for Linux, where all you have to do is click a checkbox for the program you want, and click "Apply".

      All deps are taken care of, the program is downloaded and installed automagically.

      Updating your system is even easier: "Mark All Updates", and "Apply"

      To set all this up on a Fedora system, refer to the Stanton Finley guide.

      More on topic, the Apple desktop is no threat to Linux, and never will be. Apple provides a turn-key solution which some people find appealing. Linux provides more power, flexibility, runs on a wider choice of hardware, and comes with better support at a lower cost.

    14. Re:Beautiful by MuMart · · Score: 1
      The one thing that stands out at me is that Symphony uses Yet Another(TM) packaging system that is supposed to fix all the woes of the previous packaging system. Haven't we learned yet? In a complex system, packages are just as bad (actually worse) for users than DLL Hell.

      Proper software management is a vital part of a modern operating system. The proper package management with strict dependency checking that linux systems use are the safest way of ensuring software compatibility. Are you perhaps suggesting we stop trying to use shared libraries and go back to the bad old days of enormous buggy, insecure static-linked binary packages in /opt?

      Under OS X, installation consists of downloading the application, and optionally extracting it from an archive. That's it, nothing more.

      And this is different from Debian how? The grass isn't that green in OSX land. If every Linux distribution was Red Hat we wouldn't have package management problems either, and linux packages would be small, portable and consistent.

    15. Re:Beautiful by Ford+Prefect · · Score: 1

      Yet Mac OS X has none of these problems thanks to its amazing .APP application scheme, and IOKit interface which tracks files by INode instead of path.

      I do like the .app application bundles (reminiscent of applications on Acorn's RISC OS!) but I wouldn't say everything was lovely - such drag-and-drop bundles don't work so well when something needs to install frameworks, drivers or whatever.

      For instance, I've yet to find out the proper way of removing something that's been installed by an installer package. Is there one? It doesn't seem to be like, say, RPM where I can easily remove a package (or get a list of packages which depend on it) - it all seems to go a bit ... manual...

      It's not as if applications don't use that system for installation, either - I recently installed iLife '05 (yeah, I'm slow) and it appears to have spread files out all over the place. Not as bad as your average Linux application admittedly, but I'm not sure how one would go about tracking them all down. (Okay, so I'm not likely to remove it, but I'm using it as an example, okay?)

      But surely I'm just missing some terribly obvious utility?

      --
      Tedious Bloggy Stuff - hooray?
    16. Re:Beautiful by listen · · Score: 2, Informative

      Your rosy eyed view of Mac OS X packaging is quite amusing. From someone who actually knows something about the issue, Mike Hearn of the autopackage project, in his own words:


      Does the Mac fare any better? Unfortunately not. MacOS X has (in theory) totally eschewed installers in favour of App Folders, which are specially marked directories, the idea being that you simply drag and drop the app into the Applications directory. To uninstall, just drag it to the wastebasket. This is good UI, but bad everything else. By eliminating (un)install logic, it becomes extremely hard to check for dependancies, to provide system components, to clean up configuration changes, other application metadata and so on. Although technically apps can have dependancies via bundles, the lack of OS side install logic means that in practice it's not possible to install these bundles into the OS if required - the user must do it for the app. As such, apps can only rely on funtionality that was known to ship with the operating system. That suits Apples goal of selling more copies of OS X, but is rather limiting for the user. By trying to hide the problems dependancies pose all together, it creates bigger problems further down the line. As such, some Mac apps ship with install apps anyway which rather defeats the point. Note that my beef with appfolders are more to do with the way they have been implemented in NeXTStep - you can use autopackage to install apps into an appfolders style arrangement (for instance i test with /apps/packagename) and one day there may well be a VFS plugin that lets you view installed packages as folders/directories. I think it is highly unlikely that you'll ever be able to just drag app directories off a CD onto the system however.


      And you will note that even Apple do not universally use the app folder method of installation.

    17. Re:Beautiful by AddressException · · Score: 1

      RISC OS had a similar approach in the late 80s. A directory prefixed with a "!" would show up in the UI as a single application object

    18. Re:Beautiful by lxs · · Score: 1

      Windows XP is good enough for daily use, but why settle for 'good enough', when you can make something better?

    19. Re:Beautiful by binkzz · · Score: 1

      Under OS X, installation consists of downloading the application, and optionally extracting it from an archive. That's it, nothing more. You can run the app from any location (although the "standard" is the Applications folder), including right out of the DMG archive! File associations are easy: Just have the program on your hard drive. That's it! The OS takes care of querying the program for its associations. If you move the program, the OS knows. And if you delete the program, the OS removes the association. No mucking around with manual configuration. The *only* thing you can change is the default program!

      You mean like Gentoo's emerge or Debian's apt-get? They don't even require you to download the application; they calculate all the dependencies, download them, install them, then download and install the main application.

      AFAICT, there is no mention that this intel processor will be x86. If it is, I think this will only boost Linux, because apps on the Mac OSX will run under Linux too (or even with minor modification).

      --
      'For we walk by faith, not by sight.' II Corinthians 5:7
    20. Re:Beautiful by MyHair · · Score: 1

      Given that OS X has shown us the power of this method, why haven't any distros latched onto it?

      Klik is a one-folder package system, but it is styled as a "run without installing" system for KNOPPIX and Debian. I like the idea but haven't used it extensively:

      http://klik.atekon.de/

      I don't think you can freely (freely as in it would work) copy the directories around the fs or to another machine, though.

    21. Re:Beautiful by Anonymous Coward · · Score: 0

      The future of OS X is 64 bit.

      The Pentium 4 that Steve was using during the keynote was the 'Pentium 4 Extreme Edition', which is the same architecture as Athlon 64.

      The new PowerMacs will ship with the dual core versions of those.

      And BTW, OS X is as open source as it ever was.

      And OS X is NOT moving into the commodity PC market. A Mac will still be a Mac. A top-of-the-line computer, built specifically by Apple for OS X. They're not going to start licensing OS X for your beige Dells and HPs.

    22. Re:Beautiful by grumbel · · Score: 2, Informative

      ### And it is absolutely easy: an apt-get install xyz installs/updates package xyz

      $ apt-get install xyz
      E: Could not open lock file /var/lib/dpkg/lock - open (13 Permission denied)
      E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

      Ok, next try:

      $ sudo apt-get install xyz
      Reading Package Lists... Done
      Building Dependency Tree... Done
      E: Couldn't find package xyz

      Both of the aboves gives you a pretty good summary of why Debians way of handling packages isn't really any good in the long run.

      First of you can't install a application as a user, now how stupid is that? If *I* want to install a bleeding edge version of Gimp, I neither want to bother the admin with it nor do I want to force it an all the others users, yet Debian requires me todo exactly that.

      Secondly Debian packages work great, but only for stuff that is in Debian, which might be a lot, but is *far* from everything and its also often *way* outdated, remember those three year release cycles... Software packaging should be done by those that provide the software in the first place, the distro might run a quality check on it, but thats it. What good is it to release a software today and having to wait three or more years till it finds it way into Debian?

      There are of courses dozens of other problems, but those above are probally the main ones. You can of course work around them by compiling yourself, but didn't we invented packaging system to avoid exactly that.

    23. Re:Beautiful by wild_berry · · Score: 1

      In the wake of the announcement, I got sidetracked into arguing why I pick AMD over Intel chips in the computers I build. The key answer is price, and the value of a Linux distribution make me say that OSX on Intel is not a threat to GNU/Linux on my hardware (and I may pick up dead-end G5 cheap to run Linux/PPC).

    24. Re:Beautiful by Anonymous Coward · · Score: 0

      This is probably true, as Intel should be 80% 64-bit by next year. BUT .. the published Apple developer documentation only covers IA32.

      Also OSX 10.4 will never have a 64-bit GUI layer on any platform.

    25. Re:Beautiful by mattdm · · Score: 1

      Yet Mac OS X has none of these problems thanks to its amazing .APP application scheme, and IOKit interface which tracks files by INode instead of path.

      It's not so amazing -- it's basically just "dump your package in /opt/ApplicationName" plus some cover-up candy. It doesn't do anything like track dependencies, so using shared libraries other than the absolute core OS is pretty much out.

      Given that OS X has shown us the power of this method, why haven't any distros latched onto it? Yes, it means that the OS must promise a base set of shared libraries, but the user experience is so much better!

      Your "yes it means" is pretty huge. And it glosses over the fact that *nothing but* that base is usable.

    26. Re:Beautiful by dnnrly · · Score: 1

      Ah, those were the days. Installation was a matter of dragging the application directory to the necessary location and making sure !System had been updated.

      I cried the day I realised I had to move to the PC platform. (All to do with cost and community issues, nothing to do with technical ones!)

    27. Re:Beautiful by Anonymous Coward · · Score: 0

      Bruce, why are you selling out and sucking up to MSFT? What about Free Software?

    28. Re:Beautiful by AKAImBatman · · Score: 5, Informative

      Hi Bruce!

      The installation system you write about is elegant, but you don't describe how (or if) it fixes that problem.

      True. I was running out of time, so I ended up shortening it to "the OS must promise a specific set of APIs". What I was trying to get at, is that nearly all APIs that are useful to multiple programs that you may have installed (i.e. I probably won't have two Word processors, so sharing Word processor specific APIs is pointless) tend to be provided by the OS vendor. Apple handles this via the use of "frameworks", a package similar to APPs. The catch is that only Apple tends to distribute these frameworks. As a result, Apple has made themselves the only source for system wide APIs.

      It is of interest to note that the same is true of Windows. While the ability to install system wide DLLs exists, the reality is that only Microsoft tends to distribute anything that's useful for multiple programs. Modern Linux distros have started down the same path with a set of default APIs, but they tend to fall flat due to a lack of standardization and incompatible library versions.

      For the APP concept to work on a Linux system, the system must promise a very precise set of APIs with precise minimum versions. Programs should be aligned along the use of this standard, with programs upgrading when the OS upgrades the standard. (Analogous to OS X 10.3 -> 10.4 and Windows 95 -> Windows 2000.) If a developer wants to use a newer version of an API or a non-bundled API, then he should bundle it with his program. It's possible that he's use up slightly more memory than necessary, but it shouldn't matter in the grand scheme as long as he doesn't try to replace the entire OS. (In which case, something is wrong with either the programmer or the OS.)

      Now traditional packaging systems are sufficient for core OS components like these. You *want* a consistent OS at that level. But at the application level, these dependencies (or more often, dependencies of dependencies) tend to get messed up and deny the installation of a program that will function correctly. There's no reason for this. A prelink can be done, and the program can gracefully error out if there's a problem. There's no reason to place the user through the teeth gnashing pain of solving those dependency issues.

      An excellent example of a system that manages to use this scheme is the Java Virtual Machine. Love it or hate it, programmers always have access to a specific set of APIs, then are able to add more as they're program requires. The only duplication of libraries tends to occur in places where the JVM had not yet added an API. (e.g. XML parsers, Logging, etc.) Once an API is added, then the number of duplicate libraries drops. Rinse and repeat.

      Is that a little clearer? (Not sure if I'm coming across too well.)

      Debian's package system works fine for their users because there is one huge repository with management of the proper cross-dependencies within that repository, rather than many repositories with little coordination.

      There's a couple of problems with this:

      1) Even singular repositories screw up. A few years ago when I tried Debian, I ran into dependency hell out of the main repository. That wasn't supposed to happen. I've even had it happen in my favorite repository, the FreeBSD ports tree.

      2) Repositories are useless for commercial software. I understand that OSS developers think everything should be free as in Airplane Peanuts, and free as free to go to a Hawaian Backyard Party, but there are still plenty of examples of commercial software that can't go in these repositories.

      3) There are still constant arguments over where to put things on a Unix system. The APP solution solves everything, as everything always goes in the APP folder. This is actually *closer* to the Unix philosophy of having a standard set of subfolders (e.g. bin, lib, man, src, etc.) inside every major folder. So if someone invents a new sort of meta-data (e.g. desktop icons, info pages, etc.) there would no longer be a question about where to standardize on their location.

    29. Re:Beautiful by IAmTheDave · · Score: 1
      I think that x86 Mac is attempting to threaten Linux. Apple is a very Linux unfriendly company with no moves to support anything that smells like linux.

      You mean like Apple's X11, or Safari and KHtml and the new Apple Webkit?

      I wanted OSX because it was 64 bit and Open Source.. I was a sucker, I believed the marketing ... OSx's future is 32 bit and not nearly as OpenSource as their drumbeating would suggest.

      Um, I doubt that they'll be moving to 32 bit processors. The Pentium D (speculated to be the Mac OSX processor) supports 64 bit:

      Processors with Intel EM64T allow platforms to access larger amounts of memory and will support 64-bit extended operating systems.

      You're also assuming that OSX will install on white-box hardware, which has never even been suggested. Apple will continue to roll proprietary hardware and software, and will not allow installation of OSX on normal white-box hardware.
      --
      Excuse my speling.
      Making The Bar Project
    30. Re:Beautiful by iwan-nl · · Score: 1
      Actually, there is a GUI frontend for apt. It's called synaptic and it comes with the Debian based distribution Ubuntu.

      I agree that apt-style package systems are the best way to manage applications. This Mezzo thingy (the SymphonyOS desktop) combined with synaptic for package management would, IMHO, make a great environment for average users.

      --
      I'm trying to improve my English. Please correct me on any spelling/grammar errors in this post.
    31. Re:Beautiful by Anonymous Coward · · Score: 0

      A Windows-style Wizard Installer is easier for the average dummy than the package system that requires the user to take four manual steps to upgrade an app.

      Which is a huge flaw. Software installation should be automatic.

    32. Re:Beautiful by Anonymous Coward · · Score: 0

      This post has so many inaccuracies, I don't know where to start...ok, thats not entirely true or I wouldn't be writing this...

      "Apple is a very Linux unfriendly company with no moves to support anything that smells like linux."

      Apple is BSD based. Would you accuse the BSD guys of being Linux unfriendly just because they develop solely for BSD? No, you'd be an idiot to do so. Most that I know, don't work on Linux for the fear that the virus will effect their code and their noble efforts of not forcing their religion down anyones throat will be effected by RMS and then'd then have to force others to follow a religion they didn't feel like. Instead, they make it easy for others to look at the code and incorporate the changes into their cult if that is what they want, but take no part in it.

      Apple's license is the same way.

      Darwin? Marklar? No fucking shit? Who would have thought Marklar was being fed by Darwin? I can't believe they've exploited all those OS programmers by doing so...oh wait, 99% of those OS programmers were paid for by Apple. The other 1% had moved Darwin to what is it? Open GNU/Darwin or something like that because they didn't like BSD type licensing...oh no! Someone might make a profit off of something I did!!! Oh No! I contributed this to the world and someone found it useful! I mean I gave to the world in hopes of increasing global knowledge and sharing and look what it got me! People are actually using it!!! Those bastards!!!

      As for 32bit x86 OSX? I have on good word that the target is back to being 64 bit...though the early efforts are on the cheaper consumer level items and as such, 32bit is good enough. The internal version of Darwin works fine on 64bit (heck, the external version might as well...but I don't keep up on that...about the only time I have to touch this as an OS is when I load OSX into single user mode and thats the closest I need to Darwin).

      As for Fink and Torvalds -- PPC will still be in the server rooms. Is the Power5 going away? Does this mean their work is wasted? Hell no...I'm sure IBM would hire either of them with no hesitation. Linus was using a PPC64 because IT WAS GIVEN TO HIM and he wanted to put some effort in the platform...its the cheapest way to develop towards IBMs bigger boys. Now, someone will just need to give him a mainframe to play with.

      All in all, you sound like a little and bitter man. Your machine didn't just magically stop working. You have 2 years before the G5 is even superceded (the G4 items are the ones being replaced by x86 next year)...and even then, it will be a great platform to work with. At this point, I'm happy to have both Macs and PCs (running Linux -- no need for BSD as I've already gotten that on my Mac)...

      Seriously, if you are getting rid of you G5s -- respond here with an email and I may be interested in taking them off your hands...after all, its not going to be for another 18 months before most of the sane people start thinking of getting rid of theirs (and even then, I'd imagine G5s and PentiumDs being sold side by side for a while because Apple NEVER gets it right the first time...and I am an Apple Apologist and admit this).

    33. Re:Beautiful by mattdm · · Score: 1

      After looking at the screenshots, allow me to be the first to say: Wow. That's so beautiful, it brought a tear to my eye.

      Slashdotted, so I found the backup server -- we'll see how long that lasts. But wow, it's so *not* beautiful it brought a laugh, not tears. It looks like it was designed with the same kindergartners-on-crack design philosophy that makes KDE so colorful and cluttered. (And WinXP, for that matter.) Bright colored cartoony graphics are fun to look at for a little bit, but for an OS, I want a nice, tasteful, muted *out of the way* theme so I can focus on my actual work. (OS X got this right, and so many imitators miss the point.)

      It's also kinda funny how it misses its own advice -- the "Laws of Inteface Design" on the site says "3.Scrolling sucks. A good user interface will minimize scrolling, and encourage the user to create volumes of information that do not promote scrolling." -- yet the first screenshot shows a browser window with both a vertical and the dreaded horizontal scrollbar.

    34. Re:Beautiful by Anonymous Coward · · Score: 0

      Installing from a repository isn't always going to work. If you buy a program on CD or download it from a website, it would be nice to be able to install it.

    35. Re:Beautiful by JCCyC · · Score: 1

      First of you can't install a application as a user, now how stupid is that?

      Man.

      You DO realize you just said computer security is stupid, don't you? What do you do for a living, write viruses?

    36. Re:Beautiful by mwood · · Score: 1

      Exactly the sort of problem I have with systems that try to be helpful instead of useful. If a computer is to anticipate my needs, it will have to possess an understanding of me which is far deeper than anyone today knows how to impart.

      I was only this morning explaining to someone how MS Windows' artificial sort-of-intelligence can bite when you want to do something that the designers never expected. Apparently OS X is infected with the same narrow view of the user.

      All of which goes to show why I prefer a hammer that can be used to nail together any sort of structure over a fancy gadget with a single "build doghouse" button. The only worry I have over the "Linux desktop" is that some well-meaning miscreant will achieve it.

    37. Re:Beautiful by AKAImBatman · · Score: 3, Insightful

      Your complaint that you can't install an application as a regular user makes me wonder if you're trolling. I think everyone here knows why it's a bad idea to let anyone install anything.

      Ok, why? Why should the user be prevented from having personal programs? There's certainly no restriction against fat binaries, so why not a lightweight binary?

      If the concern is system security, than the installtion level is not the place to worry about it. The place to worry about it is at the runtime level. Because a determined cracker will find a way to get a user to execute his program. And once its executed, it is the responsibilty of the runtime system to protect against anything malignant.

    38. Re:Beautiful by mwood · · Score: 1

      Aw, come on. The "x86 Mac" is hardware. Someone will have Linux booting on it a month after it ships. And then I can have one without all the desktop-environment candy coating if it gives me something other hardware platforms don't.

    39. Re:Beautiful by Bruce+Perens · · Score: 4, Insightful
      Thanks for going into depth.

      This seems to boil down to an argument that cathedral-style management of all APIs relevant to third-party applications is necessary if they are to work. Certainly they will be made to work more easily that way.

      But from a standpoint of supporting a diverse ecology of software producers and lots of competition, the cathedral isn't the most desirable structure. It seems that when one pays a draconian cost (central control) to solve smaller problems (package dependencies, file locations), it might not be the best deal in the end. I'm still endeavoring to provide a better solution to this problem.

      Bruce

    40. Re:Beautiful by Walkiry · · Score: 1

      > but why settle for 'good enough', when you can make something better?

      Because resources are finite and there're many more things to worry about to make a "Desktop Linux", would be my guess.

      --
      ---- Take the Space Quiz!
    41. Re:Beautiful by jdhutchins · · Score: 0

      First of you can't install a application as a user, now how stupid is that?

      That's common practice among any operating system. Installing a program involves installing system files, which should not be touched by a normal user. Even in Windows XP, if you're not Administrator, you can't install programs. And if it's a desktop system, you're the sysadmin, so you can just type in the root password.

      Many package systems are very up to date. Even with Debian, you can get new releases usually within several days of when they come out, although large packages such as kde and gnome can be a bit longer becuase they are tested first. Yes, Debian's "stable" release can be years old, if that doesn't suit your needs, read the website and use testing, which works great for desktops.

    42. Re:Beautiful by Anonymous Coward · · Score: 0

      Because unless you are referring to home directory installations, which is a different matter altogether, allowing the user to install programs would mean that the user (one way or another) had write access to the rest of the hard drive.

    43. Re:Beautiful by Anonymous Coward · · Score: 1, Insightful

      Maybe you should try reading comprehension sometime.

      He meant installing the application in his own home folder.

      He even gave an example of a bleeding edge version of Gimp, which he wouldn't want to force on others, only install it for his personal use.

      Of course, you can already do that, just compile and install the thing in your own home dir, by tweaking the ./configure prefixes, but the point is the packaging system should allow for that.

      Where did you read that "computer security is stupid"?

    44. Re:Beautiful by Sentry21 · · Score: 3, Informative

      Ah, but you miss the point of OS X's simplicity. The standard OS X development environment provides the vast majority of functionality that programmers require to make all but the most complex applications. There's no mucking about with 'this application requires libpng 0.4.20b and libpcap 2.1.2' as on Linux, or 'this application requires msvbvr70.dll'. An application requires Mac OS X Panther or Tiger or 10.2 or somesuch.

      If developers DO require more functionality, they can put that extra code into libraries that are inside the application bundle. Since it's usually very application-specific code, it's not going to be something that other apps are going to need/want, so there's no issues with wasted space due to non-dynamic libraries.

      Thus is the beauty of OS X's design - provide a set of tools that provide what the majority of developers need, and you won't have to worry about the user having this dependancy or that, or installing this dependancy or that, and for those unixey ports, there's always fink, which is very handy indeed.

    45. Re:Beautiful by LordNimon · · Score: 1

      No, I don't think he said that at all. He just said he wanted to install an application without being root. How is that a violation of computer security? Are users not allowed to install their own apps?

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    46. Re:Beautiful by crawling_chaos · · Score: 1
      Because "something better" never makes it out of "testing"? To call Debian's release cycle glacial is an insult to glaciers everywhere. Apple has managed something like three major releases while Sarge was oozing its way toward release. In fact, wasn't Windows 2000 the supported release when Sarge began its long journey?

      Solutions need to be timely in addition to useful. A solution I can use now, with some flaws, is better than the perfect solution, as I must solve my problem now. The current models for package management across all operating systems just about suck equally, so they really aren't a factor in deciding which one to use.

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    47. Re:Beautiful by albanac · · Score: 1

      I switched away from Debian because of apt: which was ironic as I switched to Debian becasue of ... apt. It served me well for several years and then one day it broke. When it broke, there was no way in hell to disentangle the mess it had got its dependencies into: the only option remaining was nuke, format, re-install. It is possible that an uber-geek could have resolved the conflict. None of those I spoke to knew how, and I'm not one.

      I ended up with FreeBSD. The Ports system is fairly straight-forward. I've had dependency and versioning conflicts develop using ports: I've been able to resolve each one. It's slower: apt pre-compiles and ports compiles on my box, so it's slower. On the other hand, when it breaks even I can fix it. I'm pretty much happy with that.

      On my mac, the system has never broken. Go figure.

      ~cHris
    48. Re:Beautiful by AKAImBatman · · Score: 4, Insightful

      If I may be so bold, none of the "issues" leveled against the OS X APP system are inherent deficiencies in the design. For example, there is nothing that prevents a Linux APP design from adding installer/uninstaller hooks. And most installers on OS X are used for either upgrading system components (via auto-update), installing Unix components (which can't be APPed), or to manually build an APP from a highly compressed archive or tailored to the system. Nothing actually prevents such installers from being APPs themselves.

      I honestly have never understood this hostility toward the APP scheme. It's a good scheme, that actually *works*, as opposed to packages that constantly *don't*. Yet OSS developers just keep sticking their fingers in their ears and screaming "I can't hear you! La la la! I *like* having a completely unremovable mess of files across the entire system! La la la! I *like* the fact that I'm screwed if my package database should every get lost or corrupted! La la la!"

      It's just a... weird... reaction.

    49. Re:Beautiful by MsGeek · · Score: 1

      Umm, Sarge just became Debian Stable, and Windows 2000 is still a supported release until the end of this month. Your point is...?

      --
      Knowledge is power. Knowledge shared is power multiplied.
    50. Re:Beautiful by Saeger · · Score: 3, Funny

      "This application requires Linux Standards Base (LSB) 3.0" ... ah, who has time for that standards crap anyway.

      --
      Power to the Peaceful
    51. Re:Beautiful by AKAImBatman · · Score: 1

      Because unless you are referring to home directory installations, which is a different matter altogether

      Why yes, yes I am. But I can't have an application installed to my home directory because I need to install a package. And I can't install the package, because I don't have access to the package database.

    52. Re:Beautiful by iCEBaLM · · Score: 1

      Unfortunately the problem with this is that all packages have to be located in one or more repositories and maintained by the distrib maintainers for apt to work. Independant developers not associated with debian can't make packages and have them available to apt by default.

      This causes two problems: 1) Distros take longer to release (uhh, sarge?) as they're maintaning not just the OS but all the applications that go with it too. 2) If you install something that isn't packaged with your distros packaging system you break the package management completely, there is NO EASY FIX for this currently.

      Mac OS X's system is good considering the alternative, the package IS the application and everything to do with maintenance is super easy.

    53. Re:Beautiful by jedidiah · · Score: 0, Flamebait

      Debian's method of package management is quite excellent. All you've demonstrated is that apt-get might not be the right tool for a obstinate cluebie. All that proves is perhaps you don't have the chops to deal with a CLI and minor roadbumps and should instead use the available shiny-happy-gui tool instead.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    54. Re:Beautiful by Coryoth · · Score: 2, Interesting

      True. I was running out of time, so I ended up shortening it to "the OS must promise a specific set of APIs". What I was trying to get at, is that nearly all APIs that are useful to multiple programs that you may have installed (i.e. I probably won't have two Word processors, so sharing Word processor specific APIs is pointless) tend to be provided by the OS vendor. Apple handles this via the use of "frameworks", a package similar to APPs. The catch is that only Apple tends to distribute these frameworks. As a result, Apple has made themselves the only source for system wide APIs.

      And that's a very lovely idea and will make for very easy packag installation. It is not something you'll ever get on FOSS Linux however. The FOSS software community improves it software in an evolutionary sort of way - you get a whole lot of different versions of basic libraries and tools, and eventually you get some consensus on them. The key is that the whole system can be overturned - perhaps E17 will turn out to be truly amazing and a shift will occur, perhaps Y-Windows will get completed and turn out to be well worth pursuing... the point is that these decisions are made not by corporate management, but simply by what manages to get the most hackers interested in and coding for/with it.

      What I'm really trying to say is that FOSS is utterly chaotic, but draws strength from those chaotic qualities. What you're talking about is eliminating some of that chaos - and I think there's certainly merit in that idea, I just don't think it will mix well with FOSS. If you want a organised mandated structured set of required libraries and APIs use Apple (or start your own OS). If you want the masses of software and vitality of the FOSS world, you have to accept a certain amount of chaos in return. What we need is better mays of managing that chaos: I don't think we can eliminate it.

      Even singular repositories screw up. A few years ago when I tried Debian, I ran into dependency hell out of the main repository. That wasn't supposed to happen. I've even had it happen in my favorite repository, the FreeBSD ports tree.

      But things are getting better. Check out Smart a new dependency resolver with far better algorithms than apt (along with more flexibility at the backend package level). As I said, I don't think you can eliminate the chaos, but you can do a lot better job of dealing with it.

      Repositories are useless for commercial software. I understand that OSS developers think everything should be free as in Airplane Peanuts, and free as free to go to a Hawaian Backyard Party, but there are still plenty of examples of commercial software that can't go in these repositories.

      And that's where things like Autopackage come in. As long as your base libraries are managed by something like Smart, then Autopackage is fine for those 3rd party extras - it will use the libraries if you have them, but it can grab whatever else it needs if you don't.

      Don't fight FOSS's strengths, instead figure out how best to cope with the weaknesses that are the flipside of the strengths.

      Jedidiah.

    55. Re:Beautiful by rainman_bc · · Score: 2, Insightful

      I suppose it depends on if you're a home user or a corporate user.

      If I were an IT admin (I'm not - I'm a developer), I'd want to not allow users to install software for that very reason. They install crap like real player or yahoo toolbar or whatever that bog down their machines, then the whine when their machines bog down.

      But for home users it's imperitive that they be able to install software and IMO they should not have to be root to do so.

      All depends on what your audience is. And that's one of the problems.

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
    56. Re:Beautiful by lscoughlin · · Score: 1

      Assuming one of your six layers of abstractions doesn't smash itself into oblivion.

      Synaptic and apt is _not_ comparible to app bundles, be they NeXT bundles, osx, etc. etc. etc.

      and then -- ask a user to set it up!?

      *boggle*

      "catch up".

      Nice.

      --
      Old truckers never die, they just get a new peterbilt
    57. Re:Beautiful by Anonymous Coward · · Score: 0

      I call bullshit. I cannot even FORCE OSX to run an application that is in the trash and I have never, I mean NEVER seen it automount a DMG file when launching an application. DMG files automount when downloaded in Safari, but this is controlable behavior in the preferences.

    58. Re:Beautiful by FictionPimp · · Score: 1

      I install apps on windows XP all the time. I am not an admin. Its really simple c:\documents and settings\user\apps is a great place to point my install too.

      Now if the installer wants to update something in c:\windows or a driver, then no, I can't install it.

    59. Re:Beautiful by jedidiah · · Score: 1

      So?

      If you have a list of sources and a list of packages, recovering from this situation via the "nuke and re-install" option is likely going to be relatively painless with Debian for those rare instances that it happens.

      The algorithm of "dump whole OS" upon the occurence of strange boundary conditions is assinine.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    60. Re:Beautiful by Anonymous Coward · · Score: 2, Insightful

      That's just it. In order for ANY desktop OS to take hold, it has to be so mind numbingly simple to use that my parents could use it.

      With a mac, I insert a disk and run an installer. Or drag a file onto my desktop.

      For windows I insert a disk and run an installer.

      For the average linux distro, let's take an rpm-based one:

      First I have to know the difference between no-arch, 386, 586, 686, etc... and download the right rpm.

      If I can't figure that out, or if there isn't an rpm for my distro, I have to download the source, un-tar, it, configure, make, and make install.

      "no, mom, now type period, slash, no the other slash..."

      Then, if that all worked, 9 times out of 10, I'm going to get a message similar to: "lib-blah-blah.1.9 missing..." I'll have to hunt for that.

      Then to top it off, once all that is done, I still (99% of the time) have to add the icon to my desktop manually.

      This is fine for you and me, but my mom will never figure this out.

      "oh but gentoo, emerge...emerge..." right, ok mom, you want solitaire, open a terminal, yeah the black box icon. Now type ....

      Until application developers start packaging dependencies together with their app, linux will not take over the mainstream mom and pop user market. It is just too complicated to install software.

      And don't even get me started about trying to make xine play a dvd...

    61. Re:Beautiful by mmkkbb · · Score: 0, Flamebait

      Interesting. Perhaps someday OS X will catch up with Synaptic (based on apt) package manager for Linux, where all you have to do is click a checkbox for the program you want, and click "Apply".

      And maybe someday Synaptic's database will be up-to-date and complete.

      --
      -mkb
    62. Re:Beautiful by EggyToast · · Score: 1

      What's doubly interesting is that the article states that OS X is a threat to Linux, while demonstrating that the real problem Linux faces is the fracturing caused by so many different distributions all running their own package managers.

    63. Re:Beautiful by Anonymous Coward · · Score: 0

      "In a complex system, packages are just as bad (actually worse) for users than DLL Hell"

      Then why is it that I've never had the sligthest problem with my Debian and its packages?

    64. Re:Beautiful by Coryoth · · Score: 1

      Most of the basic tools are already in place, except for this "meta-debs", but these would be easy to implement

      It has effectively been done: Autopackage. There are some quirks because it tires to be distro agnostic, and hence can't assume too much in the way of default installed libraries, but the end results are excellent: it does exactly as you suggest - checks the file system for the libraries (and versions) it needs and if it can't find it downloads and installs those (as autopackages) too. It even allows for nice things like fallback functionality (use the new GTK file dialogs if GTK+2.4 is present, use the older file dialog otherwise). The only catch is that the app developers actually have to do a little bit (surprisingly little really) to make all this happen and create autopackages.

      Jedidiah.

    65. Re:Beautiful by marmoset · · Score: 1

      I've also had the OS automount a DMG file and run the app from there, instead of the applications folder.
      Are you sure about this?

      99% of the applications I download on OSX download as a disk-image file (compressed or not). Upon double clicking the DMG, the virtual disk mounts, and the Finder opens a window that shows me the contents of the "drive", which usually consists of a single application and sometimes a readme file or, more commonly, a graphic that says "drag --> this file into your Applications folder to install." My Mom (not being drunk or repeatedly hit in the head with a hammer) can figure this out...

    66. Re:Beautiful by badfish99 · · Score: 1

      Something other hardware platforms don't? Like what? Higher price?
      You can already get every variation of x86 hardware you could possibly wish for. All that Apple could possibly bring to the party is their desktop environment. Their hardware will be different, but that will just be to lock their buyers into their higher hardware prices.

    67. Re:Beautiful by AKAImBatman · · Score: 2, Interesting

      Thanks for responding, Bruce.

      But from a standpoint of supporting a diverse ecology of software producers and lots of competition, the cathedral isn't the most desirable structure. It seems that when one pays a draconian cost (central control) to solve smaller problems (package dependencies, file locations), it might not be the best deal in the end.

      The part that boggles my mind about this argument is that the Cathedral already exists. Distro maintainers that use central packaging systems have already agreed to be that Cathedral. If they could leverage that Cathedral slightly more (e.g. a standard API base), then there would be less work and fewer frustrations for everyone. :-)

    68. Re:Beautiful by jusdisgi · · Score: 1

      The one thing that stands out at me is that Symphony uses Yet Another(TM) packaging system that is supposed to fix all the woes of the previous packaging system. Haven't we learned yet? In a complex system, packages are just as bad (actually worse) for users than DLL Hell.

      This is Just Plain Wrong (tm)

      This is a debian based (apt-get) packaging system. It was one of the first, and it "fixed" all the problems you complain about in your post. (More accurately, it didn't have to fix them, as from its very inception it was designed to handle these issues.) No dependency/.dll/.so/library hell. apt-get handles this quite nicely, thank you, without you having to know anything about the deps or libs in question...you tell it what you want, it gives you what you need. No problem.

      The fact that there are a few frontends to apt-get is not a problem, particularly in this case, where these guys are really trying to engineer a new desktop experience....they want this to look/feel different. But I'll bet you the same functionality is there; the problems you mention will not happen.

      So please, can the FUD.

      --
      Given a choice between free speech and free beer, most people will take the beer.
    69. Re:Beautiful by harlows_monkeys · · Score: 1
      Under OS X, installation consists of downloading the application, and optionally extracting it from an archive. That's it, nothing more

      Well, for maybe half the apps that is true. The other half require using an installer, because they need you to type your admin password to install them.

      This includes a good fraction of Apple's own apps.

    70. Re:Beautiful by amliebsch · · Score: 1

      While reading your comment, I just had one of those "Aha!" moments as to exactly what Microsoft's goal with .NET is. The whole ".NET Framework" seems to be exactly what you described, and using manifests allows upgrading the framework without breaking older apps or having to update the OS.

      --
      If you don't know where you are going, you will wind up somewhere else.
    71. Re:Beautiful by ssj_195 · · Score: 1
      This causes two problems: 1) Distros take longer to release (uhh, sarge?) as they're maintaning not just the OS but all the applications that go with it too
      Yes, as demonstrated by the glacial release cycle of Ubuntu, versus the incredibly rapid turnover of Windows and OS X. Or rather, not.
      you install something that isn't packaged with your distros packaging system you break the package management completely
      I've never actually seen this happen myself, but I'll take your word for it :). Anyone have any horror stories to share? Does it happen with actual packages, or only if you install from source?
    72. Re:Beautiful by Anonymous Coward · · Score: 0

      That's right. Sarge began life when Windows 2000 was new, and it was released a month before it was EOL'd.

      Thankfully, no one considers Debian to represent a typical release cycle. 6 months seems to be the gold standard. Of course, that's 6 months between very incremental releases, where nothing new ever dares to happen until Microsoft or Apple does it first.

    73. Re:Beautiful by jusdisgi · · Score: 2, Funny

      To call Debian's release cycle glacial is an insult to glaciers everywhere.

      Hey, when's the last time you saw a glacier upgrade its kernel from 2.2 to 2.4 n four years?

      --
      Given a choice between free speech and free beer, most people will take the beer.
    74. Re:Beautiful by hackstraw · · Score: 1

      The simple & dumb way as OS X handles packages is just that: it can not handle dependencies, or anything, it just puts some files on your computer.
      It works moderately well, if you only use it for applications and those are statically linked, but nothing else.
      Now, take Debian's package system: it handles dependencies, version conflicts, alternative packages that serve the same purpose, etc, etc, ec. And it is absolutely easy: an apt-get install xyz installs/updates package xyz and all the necessary shared libs, updates file associations, whatever (and it does not takes exactly rocket science to create some GUI for that single command line).


      I have never had any "dependancy" problems with any application for my Mac except those through fink, a debian package system ported for the Mac.

      Mac apps are actually directories that hold everything necessary to run the application. I have only heard of a couple of Mac apps that are frontends to commandline applications that may need those commandline applications to be installed on your system, but those are small freeware or shareware applications.

    75. Re:Beautiful by listen · · Score: 1

      I agree, I would much prefer it if things were more isolated and versioned. Take a look at Gobolinux, it seems to be halfway there. Zero install and the ROX desktop are also interesting. However there is a massive cost in transitioning to a system like this : it is very hard to make a real case that the switch is worthwhile.

      But... my real point was that OS X zealots often act as if everything that Apple do is perfect in concept and implementation, and that there is something holy and unique about Apple that means that a better solution is simply impossible. Because they are Designers (TM), or something.

      I've had a far far worse time with OS X installers leaving crap around than with the debian package system. But I don't then claim .debs are perfect.

    76. Re:Beautiful by pyros · · Score: 1
      AFAICT, there is no mention that this intel processor will be x86.

      Have you been sleeping? All the demos Jobs did at the keynote were done on a Pentium 4. The transition developer kit included a Pentium 4 machine. They Universal Binary Programming Guildlines even say no more OpenFirmware. All these factoids have been posted to various threads like 100 times.

    77. Re:Beautiful by lost_n_confused · · Score: 1

      The reason it says drag this to the hard drive is because is a mounted image that won't be there after the next reboot. I have found 99% of the programs will operate from the image file. The few that won't generally tell you that they won't in the readme. I generally test shareware by running it from the image file and if I don't like it I blow it away if I do like it I move it to my hard drive.

      --
      -- To mess up an OS X box, you need to work at it; to mess up your Windows box, you just need to work on it.--
    78. Re:Beautiful by strider44 · · Score: 1

      fucking hell.

      What's so hard about clicking the damned icon that says "install packages"?

      But if you want to install the bleeding edge version of gimp, why don't you just do it the windows way? By downloading it from the web site?

    79. Re:Beautiful by Kiryat+Malachi · · Score: 1

      All of which goes to show why I prefer a hammer that can be used to nail together any sort of structure over a fancy gadget with a single "build doghouse" button.

      Hammers are nice, but when all I really want is to build a doghouse, I like that "build doghouse" button.

      Similarly, when I'm writing brand new code, I like having the ability to do dynamic linking, change various little bits, and so on. When I just want a word processing application to install, I like having the "install application" button.

      Flexibility is overrated, sometimes.

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    80. Re:Beautiful by DrFrob · · Score: 1

      Copy an application from a DMG file to your dock. Eject the DMG and then launch the application. You'll notice that the DMG then mounts itself again.

    81. Re:Beautiful by ivano · · Score: 1
      of course he's referring to home directory installation. not to add insult but it was pretty obvious where the GP was coming fom.

      I think it was easier for you to just insult him than answer his question. Just like I'm doing to you :)

      Ciao

    82. Re:Beautiful by fyonn · · Score: 1

      You DO realize you just said computer security is stupid, don't you? What do you do for a living, write viruses?

      no, he didn't. he asked why he can't install an app as a user? thing is, in unix, even debain he can. not in the system directories, but in his own dir. why should apt not support that? maybe it does, I've never used debian, but I think this is his point.

      it's a good point though, security is a big concern, but so is useability. users want to install software, the system in general will let them, so why make them jump through hoops?

      dave

    83. Re:Beautiful by AKAImBatman · · Score: 1

      To be clear, I'm not saying that all distros should just up and adopt this scheme. There's always going to be a "different strokes for different folks" mentality in the Linux community. But there *are* a variety of distros, all with supposedly different goals. Today they are all pretty much clones of each other with slight strengths and weaknesses over one another. No one has yet taken a stand and decided to do a really different distro that does attempt to appeal to the home Desktop market. The closest thing to this is the Java Desktop System, but it's really intended to be a user interface to Java applications. (No comment on whether that has been achieved or not. That's a different discussion.)

      The issue I currently see with Linux is that the community is *not* exploiting its ability to be different in an open environment.

    84. Re:Beautiful by homerito · · Score: 1

      I am locked at the office with Red Hat Linux release 7.3 (Valhalla) and a 2.4.20-20.7smp kernel with a very old kde and old gnome. I am a simple user but i managed to install applications by compiling them and creating my own /usr and /local in my home directory. I have not been able to get gtk+ 2.6.7 to work and i am stuck with gtk+ 1.2 so no fancy kde or gnome for me :(. I ended up installig enlightenment with a new version of freetype and that works ok for now. Dependency is really hell installing applications like that. The administrators have not bother me so far.

    85. Re:Beautiful by jusdisgi · · Score: 1, Troll

      Both of the aboves gives you a pretty good summary of why Debians way of handling packages isn't really any good in the long run.

      No, both of those are asinine examples of stupid assumptions and bad behavior, and don't show any "problems" at all.

      First of you can't install a application as a user, now how stupid is that? If *I* want to install a bleeding edge version of Gimp, I neither want to bother the admin with it nor do I want to force it an all the others users, yet Debian requires me todo exactly that.

      You jackass. It's called some semblance of security. Allowing any user to install things is a Bad Thing, and even a properly locked-down Windows box won't allow this these days. You want to have some control over what can and can't be installed; if you want somebody to be able to install things, you grant them permission, either by letting them su or by giving sudo access. The latter you can do 1)requiring root's password, 2)requiring the user's password, or 3)requiring no password at all. Your choice. Quit your bitching.

      Secondly Debian packages work great, but only for stuff that is in Debian, which might be a lot, but is *far* from everything and its also often *way* outdated

      Debian is not a mainstream desktop OS. Go get Ubuntu, which has the same packaging system and basic system design, but much newer packages and a better desktop setup. And quit your bitching.

      And this bullshit about "Could not find package xyz"? So, you're complaining because to install something, you need to know what it's called? I mean, seriously......you don't think it's reasonable to ask the user to know the name of a program? Well, ok, fine....apt-cache, and all the apt-get frontends, allow you to search both names and descriptions. So quit your bitching.

      --
      Given a choice between free speech and free beer, most people will take the beer.
    86. Re:Beautiful by Shalda · · Score: 2, Interesting

      See, that's the issue. Programs should come as one single file that can be conveniantly added or removed. Drag and drop. Installing a program should never ever involve updating system files or altering any other applications files. There should be no "Package Managers". Microsoft doesn't get that. The Linux crowd doesn't get that. Apple, I think, wants to get that, but that's all a long ways off.

    87. Re:Beautiful by Znork · · Score: 1

      "I think that x86 Mac is attempting to threaten Linux. "

      Perhaps, but anyone who thinks they'll succeed hasn't understood why linux has been successful.

      It's not because it isnt Microsoft. It's because it gives you back control over your computing.

      Apple is even more controlling than Microsoft, deciding where you want to go today on both a software and hardware basis. That's fine for competing with Microsoft for end users, and if Apple can offer better prices or something with x86, all kudos to them, and hopefully they'll get a few more customers.

      But it wont put a dent in the Linux market, neither at the enterprise level or at the hobbyist level because where Linux offers a new compelling free and competetive approach, Apple only offers the same old proprietary hardware and software combination that countless of vendors have offered for decades.

    88. Re:Beautiful by Hast · · Score: 1

      I only works in the way that it installs programs on OSX. It doesn't solve the problems inherent for GNU/Linux.

      In order to make it work on GNU/Linux you'd need to have all standard libraries installed per default or just include everything as "dll's" in the application package.

      The reason it works for OSX is because OSX is an extremely controlled platform which allows them to make assumptions that are not valid on GNU/Linux. OSX doesn't even run on more than one plaform (at least not with end users who do the installing) or anything but special built hardware. Of course it works without a hitch, they'd had to be the worst designers in the world not to make it work!

    89. Re:Beautiful by Anonymous Coward · · Score: 0
      Why heck even Linus was using a PPC64...
      Scary huh?

      Linus adopts PowerPC Macs, Apple discontinues them.

      Linus adopts a SCM system. The owner of the company that makes it becomes the most reviled person in programming history.

      Linus works for Transmeta. Transmeta goes bust.

      Linus works for OSDL. OSDL has to restructure and do some serious damage limitation.

    90. Re:Beautiful by Tony+Hoyle · · Score: 1

      OSX has none of these problems because it has no package system to speak of. .dmg files are just raw disk images, and you drag/drop them into your home directory. .pkg files are closer, but IMO no packager is worthy of the name unless it supports *uninstall*. Currently the only way to uninstall apps on OSX is to reformat the drive... not exactly user friendly.

    91. Re:Beautiful by ArsonSmith · · Score: 1
      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    92. Re:Beautiful by snorklewacker · · Score: 1

      > Independant developers not associated with debian can't make packages and have them available to apt by default.

      You can add third-party repositories any time, and nothing prevents people from packaging up a .deb and offering it on their site. This is the same issue you get with redhat, and frankly even slackware. Gentoo makes third party portage subtrees *really* complicated.

      The contrast is the fact that the central repository simply doesn't even exist for Windows or MacOS, so everyone's had to use a different distribution method. God knows the packaging mechanism in Windows isn't much to emulate (actually MSI's are quite good, but add/remove programs still sucks immensely), but MacOS might be on t o something with .DMG.

      Given the state of GUI package management tools (synaptic is frankly quite clumsy), I don't think integration of packages with the desktop has been a high priority in many people's minds...

      --
      I am no longer wasting my time with slashdot
    93. Re:Beautiful by jusdisgi · · Score: 1

      Why yes, yes I am. But I can't have an application installed to my home directory because I need to install a package. And I can't install the package, because I don't have access to the package database.

      Uh, sorry man. That's just not right. You can still install things in your home directory. There is no requirement of using the package manager, it's just the easy way to install software system-wide. Please sit down.

      --
      Given a choice between free speech and free beer, most people will take the beer.
    94. Re:Beautiful by Coryoth · · Score: 2, Interesting

      The part that boggles my mind about this argument is that the Cathedral already exists. Distro maintainers that use central packaging systems have already agreed to be that Cathedral. If they could leverage that Cathedral slightly more (e.g. a standard API base), then there would be less work and fewer frustrations for everyone.

      I'm really not so sure that would work as well as you suggest. Many of the distros survive by letting you install as much or as little as you want, by letting use GNOME or KDE or XFCE or *box or play with dev versions of E17. The distros themselves work hard to remain flexible in what software they suck up and include in the distribution.

      I'm sure, if you wanted to you could mandate a firm API - just don't expect FOSS developers to necessarily agree and develop against the paritcular APIs you chose. Try telling the Firefox crew to abandon XUL and use pure GTK+ or QT. Who knows where the next must have app will come from - maybe someone will develop a truly revolutionary new "must have" application using Mono - are you using Mono for your mandated API?

      There is as much life and vitality in FOSS as there is because the developer can use whatever library, whatever API suits his or her needs. The distributions, in turn, keep an open and flexible system to make it easy to add new libraries or applications using new or different or otherwise obscure APIs.

      Linux, I think, does as well as it does because it can rally such a vast array of applications, and it does that by supporting applications using the console, pure GTK+, QT, GNOME, KDElibs, FLTK, Edje, XUL, Mono, or whatever takes your fancy. Apple does well because it has cornered a niche and has a pretty guaranteed market, so plenty of people are willing to develop for it - particularly in the commercial software for designers realm. Apple also gets support via Fink, but from what I gather that's back to the dependency management and lack of rigid APIs thatb you're complaining about. A new OS, or distro is not going to get much use if it can't get enough applications - if you can't promise a market like Apple can, and you can't promise freedom to develop however you like as Linux can, well... I suspect you end up like BeOS and NeXT, just hoping you can get bought out by someone bigger.

      Jedidiah.

    95. Re:Beautiful by Anonymous Coward · · Score: 0

      Sorry man, but you're just wrong.

      1) when upgrading an application, all you need to do is drag and drop into the Applications folder. You don't need to move or trash the old application. Just overwrite the old application. Done.

      2) Sounds like you're trying to run applications from the Dock. The Dock icon is associated with a folder, so when the folder is moved to the Trash, of course the Dock icon will still launch it. If you use the method outlined in point 1 of this post, that won't happen.

    96. Re:Beautiful by rpdillon · · Score: 1
      Well, that depends on your package architecture. In a package architecture that uses dependencies, you're necessarily going to have to touch system libraries and binaries during install - I wouldn't want someone hijacking a setuid root install process to bootstrap an attack on the system because some newbie user decided to click "OK" in a browser window, or better, an email.

      OTOH, if you're using static binaries, who cares? You're not going to be touching those system level files, and if the user wants to push some programs to ~, go ahead. That's when kernel-space vs. userspace checking comes in, as well as where the setuid and execute permissions take over.

      You really need protection at install and at runtime, particularly when install is a system-level task (as it is with practically ANY package management system).

      That said, I really do disagree with the original post; I think package management systems have gotten to be very sophisticated, and they implement the Right Way to handle installations. The easy way isn't always the Right Way, as both Windows and OS X have shown. Sure, OS X's method may be simplified for the end user, but to quote a manifesto I believe to be brilliant: "Usability simply does not equal low learning curve, and hiding system details from the user, as the Official Truth seems to be these days."

    97. Re:Beautiful by grumbel · · Score: 1

      ### You DO realize you just said computer security is stupid, don't you? What do you do for a living, write viruses?

      Its a usability problem, not a security one. If I want security, I mount the home dirs with noexec or have a policy that forbits them and run nightly cron checks or whatever. apt-get not support user install doesn't prevent a user at all to run untrusted binaries, actually worse it forces the users to search for binaries or source in potential insecure places instead of using the high quality debian packages.

    98. Re:Beautiful by ArsonSmith · · Score: 1

      Of course apple can threaten Linux on Intel.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    99. Re:Beautiful by turbidostato · · Score: 2, Insightful

      "First of you can't install a application as a user, now how stupid is that?"

      Yes, now you point it out is quite stupid.

      Now: why is it that my car has a single wheel drive? Only the driver can decide where to go with the car! isn't it plainly stupid?

      The things the computer will do are decided by its administrator, just the same the captain of a boat is the single one that decide where the boat will go.

      "If *I* want to install a bleeding edge version of Gimp"

      Tell it to the administrator, or become administrator yourself.

      "I neither want to bother the admin with it"

      I promise you will bother even more if you could just go installing software all around. And still, you will probably be able to just compile the Gimp and install within your home directory not needing aid from the sysadmin for that.

      "Secondly Debian packages work great, but only for stuff that is in Debian, which might be a lot, but is *far* from everything"

      Wrong again. Debian packages will work great for any stuff built "the Debian way" no matter if it comes from Debian repos or not. Well... quite exactly the same with your beloved MacOS/X: it doesn't work too good for binaries not developed for it, does it?

      "..and its also often *way* outdated, remember those three year release cycles..."

      Debian has not a "three year release cycle" while it is true that last Stable has been so for three years (and still, major versions of any propietary OS -including Apple's, doesn't seem to get the market with higher frecuencies, do they?).

      Again, nothing avoids you to produce and distribute your own packages FOR Debian. Heck! then you will prefer a long release cycle in order not to change too much your packages for a long, long time.

      And then again, even if you'd be force to change stuff at a fast pace, it is much better when the whole production process is publicly available so you don't have to either wait for The Company to release their new OS version and see then how it breaks your program or sign expensive deals with it in order to have a look to early betas.

      "Software packaging should be done by those that provide the software in the first place"

      That you will have to tell to software providers; nothing prevents them from doing so. Debian package format, for instance, is publicly available as well as tools to help at the make of it.

      "the distro might run a quality check on it"

      And it does for quite a large bunch of software. But this shouldn't refrain you from plubishing your own "non-blessed-by-the-distro" software if you want to. After all, I don't think neither Microsoft nor Apple runs quality checks on, say, Dreamweaver, and nobody expects it to be otherwise.

      "What good is it to release a software today and having to wait three or more years till it finds it way into Debian"

      Here you simply don't know what are you talking about.

      "There are of courses dozens of other problems, but those above are probally the main ones"

      Then we are quite lucky since noone of the "problems" you talk about are real problems at all, but in your imagination and due, so it seems, from poor knowledge.

    100. Re:Beautiful by mrchaotica · · Score: 1

      You're absolutely right: the cathedral isn't the most desirable structure. However, that's exactly what we have: the Debian repository is a cathedral, Gentoo's Portage is one, FreeBSD's Ports is one, and so on. Of course, the result of that is multiple, fragmented cathedrals, which isn't just not the best, but is actually the worst possible solution. A single cathedral (a la Mac or Windows) wouldn't be ideal, but it would still be an improvement.

      In the long run, I think the only real solution is standards, and more importantly, standards that everyone can agree on. LSB is making progess in this area, as is Freedesktop.org. However, it won't go anywhere if everyone keeps bickering about how LSB chose the wrong package manager and whatnot.

      I think the reason why this is such a difficult issue is that it's actually a human, rather than technological, one.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    101. Re:Beautiful by fishfinger · · Score: 1

      And as it has also been posted 100 times, Apple have stated that OSX will only run on an Apple x86 so it might as well be a non-x86 Intel processor.

      Besides, if it is a x86, this may well mean that a OSX compatibility layer can be incorporated in to Linux, much like FreeBSD's Linux compatibility!

    102. Re:Beautiful by Anonymous Coward · · Score: 0

      "Are users not allowed to install their own apps?"

      Of course they aren't!!!

    103. Re:Beautiful by Tony+Hoyle · · Score: 2, Interesting

      If developers DO require more functionality, they can put that extra code into libraries that are inside the application bundle

      OSX has /usr/local/lib just like every other Unix. It has library dependencies and LD_LIBRARY_PATH just like every other Unix as well.

      If you need libraries you're going to have to install them. OSX might want you to put everything into a single statically linked binary but it really doesn't work that way, except for very simple applications.. that's why you build .pkg scripts to install things into the right places on the hard drive.

      Unfortunately because there's no uninstall your hard drive gets clogged up with all the apps you've installed and you eventually have to reformat. I've had to do this twice since I got my Mini due to libraries and whole applications sticking themselves on the disk and unable to remove them.

    104. Re:Beautiful by mwood · · Score: 1

      I didn't say I thought it likely that I would actually find a compelling reason to use Apple's hardware. They'd have more value to me as a supplier of other *non*-x86 platforms. If I'm satisfied with x86 I'll probably just go on assembling my own.

    105. Re:Beautiful by MassacrE · · Score: 2, Insightful

      So you are saying that if an administrator wants to install software, they have a nice management tool to handle it and packages maintained as part of the distribution. If the user wants to install the same version of a piece of software already in the package database for their own use, they need to manually track down dependancies and build from source in their home folder?

      I think people are in denial that this is a problem.
      - The security model of (most) Linux systems still assumes the fact that a binary being on the hard disk means that it should be entitled to every single permission associated with the user when run.
      - Users need to understand a priviledge escalation model (sudo) and be given permission by a site-wide administrator in order to install anything, includng prepackaged documentation. This is good sometimes, but there is no way for an adminstrator to say that user installs are ok, without giving some form of limited root access.

      Current 'consumer' operating systems certainly aren't perfect on this account in terms of security, but those security issues are already acknowledged and being worked on.

    106. Re:Beautiful by turbidostato · · Score: 1

      "But for home users it's imperitive that they be able to install software and IMO they should not have to be root to do so"

      Well, IMO, and in opinion of those that have effectively develop unix-like systems, well, they have to be root.

      Now, it's free software man, you can start your "no-security" project whenever you like. But, hey, I will tell you the world is full of "no-security" Windows 9Xs and "I'm running Administrator" Windows 2000 and XPs, so I think you can have quite a good perspective about what happens when you go the "IMO they should not have to be root to do so" way.

    107. Re:Beautiful by Anonymous Coward · · Score: 0

      Hey look, another 15 year old Linux asshole who can't read and comprehend, posting on slashdot!

      Just because you can't install packages through the package manager without a root password (or sudo elevation) doesn't prevent the user from running other programs (that don't require the package manager, and don't need to be compiled if you don't allow user access to gcc) from his home directory. I was able to install RealPlayer on Solaris as a user, without elevated privileges or using a package manager or using a compiler. Not allowing packages because of 'security issues' but still being able to run programs from $HOME makes no sense. You really don't have a good grasp on system security, do you?

    108. Re:Beautiful by cahiha · · Score: 2, Interesting

      Ah, but you miss the point of OS X's simplicity.

      There is nothing "simple" about having a different package upgrade mechanism for every program.

      If developers DO require more functionality, they can put that extra code into libraries that are inside the application bundle. Since it's usually very application-specific code, it's not going to be something that other apps are going to need/want, so there's no issues with wasted space due to non-dynamic libraries.

      You're confusing cause and effect. It's not that Apple has magically figured out which packages make most real-worlddevelopers happy, it's that Apple's developer and user community has become reduced to a group of people that happen to be happy with very little. For a regular UNIX user, the Macintosh is painfully limiting.

    109. Re:Beautiful by AKAImBatman · · Score: 1

      You need to be careful about telling people that they're Just Plain Wrong(TM). You may be very wrong yourself.

      This is a debian based (apt-get) packaging system. It was one of the first, and it "fixed" all the problems you complain about in your post.

      If that was true, then why did the APT system break the first time I used Debian? I forget what the exact packages were (I think it was KDE), but the system just... broke. Classic dependency hell, on a system that wasn't supposed to be breakable.

      This guy just complained about the same thing. I've heard the same complaints from many others in the past. Not to mention that I'm a big fan of the BSD ports system (as close to unbreakable as you can get), and yet I've had that break on me many a time. Package systems are flawed for the same reason that programs have bugs: Humans are not perfect. The problem with a packaging system is that it's a precariously stacks structure that relies heavily on someone not screwing up. The slightest mistake and the whole thing comes tumbling down.

      I won't even begin to address the issue of commercial software and software that is not yet in the repository.

    110. Re:Beautiful by battjt · · Score: 1

      As long as I have run unix like environments, I've installed apps as a user.

      Installing most programs does not involve installing system files.
      tomcat
      java
      gimp
      openoffice
      xpdf
      emacs

      The only app I'm currently running that _requires_ installing system files is VMWare, which requires a kernel module.

      --
      Joe Batt Solid Design
    111. Re:Beautiful by Dcnjoe60 · · Score: 4, Insightful

      You are mixing apples and oranges. You are comparing packaging systems using the command line in Linux but using the gui interfaces of Apple or Windows. Shouldn't you be using Synaptic for a fair comparison? At least that way, you don't have the problem of not finding the package, because it's in the list you are picking from.

      Next, you complain that the debian packages are very often out of date, which is true, however, you confuse the issue of debian as distribution versus the way debian packages work. In otherwords, you are confusing one organizations implimentation instead of the actual methodology.

      Along those same lines, when you complain about packages being out of date, again, they are, in the Apple or Windows world, with commercial software, how often do new updates come out? I'm not aware of anyone running Office 2005, so you could say that Office is also out of date.

      Most of your complaints seem aimed specifically at debian itself. There are other debian based distros that have solved many of these.

      One final comment, I am assuming that you are the sole user of your computer and it is at home or a small business, because you complain about having to become an admin to install software. Well, in most businesses, that would be a plus, because you don't want joe-worker to be installing whatever he pleases. At home, too, it is a plus, I don't know how often the kids have downloaded and installed something that broke Windows. However whether OS X, BSD or Linux, you could always enable sudo for the users you trust not to screw up the system and thus mitigate the problem. I believe that is the approach that OS X took, along with several of the debian based distros.

    112. Re:Beautiful by Bob+Uhl · · Score: 1
      Allowing any user to install things is a Bad Thing, and even a properly locked-down Windows box won't allow this these days.

      You forget that (provided that /home isn't mounted noexec) a user could install an app in his home directory, perhaps in ~/bin, ~/etc, ~/lib, ~/share and so on. And that's what a package system should do when a user tries to install an app as himself--or at least provide an option.

    113. Re:Beautiful by jacksonj04 · · Score: 1

      It also depends how well the OS is designed with regards to userspace. On a mac, each user's 'individual' applications run within their own userspace (macheads correct me if I'm wrong). On Windows, a single application may install to every start menu, and run on every boot. It's possible to do this with a mac, buy you need to actually think "am I installing this for everybody?"

      --
      How many people can read hex if only you and dead people can read hex?
    114. Re:Beautiful by Anonymous Coward · · Score: 0

      So we should make it easy for admins (who should know what they're doing in the first place) to install applications across the system, but hard for the novice user to install an application for themselves in their home dir?

      I think you're missing the point.

    115. Re:Beautiful by mwood · · Score: 1

      As simplicity is overrated, sometimes.

      I'm trying to remember what year it was the last time I wanted to do word processing. (Not counting the times when I have to cope with people who send me a word processor's stomach contents instead of a finished document.)

      I just don't do the kind of work that Apple's customer base do. Everything they're proud of is something that makes me yawn. They would probably feel the same way about the things I'm proudest of. Which is my point: if you want a machine that builds doghouses then so be it, but I don't and I do not believe that the market will ever consist solely of people who do. Saying that "Linux" and Apple are competitors is about as sensible as saying that Centex Homes and Stanley Works are competitors. They make different kinds of products for different sets of customers.

    116. Re:Beautiful by mixmasta · · Score: 1

      you seem to have completely misunderstood the grandparent's post in your rush to condemn it.

      --
      #6495ED - cornflower blue
    117. Re:Beautiful by battjt · · Score: 1

      Another example of why apt-get is a PITA. Install your own X system, then try to install X app from debian. It requires their install of X. There is a way to fake it, but after hours of trying, I failed. Now I just install their version of X, then install my copy over theirs.

      Joe

      --
      Joe Batt Solid Design
    118. Re:Beautiful by SolusSD · · Score: 2, Interesting

      I believe Debian's apt is great for system-wdie upgrades, but if individual users want to install programs (ie, in their home directories) autopackage is the way to go. it'll allow you to install any autopackage in your home directory. What's even better is the package manager is contained in the package archive meaning there is no software to install to allow you to install autopackages. everyone should check this out. give it a shot by installing one of the autopackages available on the autopackage website. www.autopackage.org

    119. Re:Beautiful by Anonymous Coward · · Score: 0

      Also, have an application in your hd create a file (which has association to the application), trash the application and double click the created file, the application will launch from the trash

    120. Re:Beautiful by Urchlay · · Score: 1
      > Software packaging should be done by those that provide the software in the first place

      Eh? Suppose I write software that runs on Linux, but I don't run Debian. Do you really want to install a .deb package made by me? I haven't got the time nor (frankly) the desire to package up my software for every distribution under the sun, and even if I wanted to, it would be more than a full-time job to learn the nuances of every distribution... and if I'm a software developer, I'd rather spend my time developing software than packaging it.

      That's why there are package maintainers. Now it's possible for a package maintainer to do a good job, or a bad job... or to be too cautious, and cause long release cycles.

    121. Re:Beautiful by turbidostato · · Score: 1

      "Independant developers not associated with debian can't make packages and have them available to apt by default."

      Well, just exactly the same than... anyone else in the world and this part of the Galaxy.

      Or do you have access to Photoshop on your Windows or your Mac by the default? I bet no, you don't. You have to give some footsteps and then you get it.

      The same on Debian: you can edit /etc/apt/sources.list add the provided new source line and voila! to all effects that independent program management becomes tightly coupled with your usual Debian's tools.

    122. Re:Beautiful by LordNimon · · Score: 1
      So here's the solution. Applications should be installable only via a package manager. All packages should have the ability to install either for all users, or only for the current user. The former requires root access. If you don't want users to be able to install any apps, then you just prevent them from running the package manager (e.g. "chmod og-x /sbin/rpm").

      The problem is that I don't think there is a single Linux distro with this feature.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    123. Re:Beautiful by pmjordan · · Score: 5, Interesting

      I've thought about this occasionally. I'd agree that a monolithic repository system is not the way to go. It still doesn't solve the problem of being able to just download a piece of software and just being able to install it without problems. Debian fares no better than RPM-based distros in this respect, and installing core packages is no problem on either of the existing distros' architectures.

      A solution that seems to make the most sense to me, which nobody seems to have tried yet, is the following:

      Don't rely on one big repository (e.g. debian, gentoo, etc.) but also don't make the whole thing file-based like in OSX. Do keep repositories if you want, but in addition to having a bunch of basic repositories, (e.g. Ubuntu vs. Debian Unstable) you also put information not only on what other packages are required, but also how to get those other packages into each package.

      For example, this could be done by pointing to a bunch of mirrored URLs that point to some XML data describing the package at that mirror. The installer could pick the most recent version, choose the fastest mirror, whatever.

      Additionally, some sort of 'compound packages' would be useful. That way, you can ship rare libraries directly with the application. They may or may not be installed once downloaded, depending if you've already got the same or a newer version of them on your system. This could be especially helpful for systems that don't have internet connectivity. (gasp!)

      Sure, it's not perfect, but it beats RPMs (I use SUSE so I experience this myself) and the debian system any day, because you can just go and download packages off the internet and install them, without having to go and hunt for the dependencies yourself. Most likely whoever made the package actually had the necessary libraries installed (and the package system can remember where he got them from!) so all that is needed is to convey that information to the user's system.

      The case where it breaks down is of course when all the mirrors eventually die, for example if a package ends up becoming unmaintained. But if it's not been updated for that long, it and its dependencies could be added to the various monolithic repositories. I'm sure organisations would pop up that would keep 'dead' packages around for people to use. The way to combat this would be to have as much redundancy as possible, of course.

      I don't know. It might just work better than what we've got at the moment?

      ~phil

    124. Re:Beautiful by man_of_mr_e · · Score: 1

      As others have pointed out, we already have a cathedral system, but it's masquerading as a bazaar because there are so many of them.

      Rather than have a package management system, what really needs to happen is a package management framework. If the basic tools for a package management system were compatible with each other, then you could have RPM, DEB, portage, etc that all understood and could use each others formats.

      Unfortunately, this means defining a single COMPREHENSIVE standard, rather than the typical open source "just enough to get by and expand when we need it" approach.

      The bazaar is not always the best model. In reality, you can only achieve so much without a cathedral eventually coming into play. You can achieve a LOT with a bazaar, but ultimately there's a point of diminishing returns where conflict between the parties grinds productivity to a halt and crushes ingenuity.

    125. Re:Beautiful by sandbenders · · Score: 1

      I think that your answer is a classic example of what we in the usability business call the 'mirror persona'. You are answering this post thinking of your own capabilities, not the capabilities of the users we're hoping to attract. Packages are a great way to handle things for engineers, for linux enthusiasts, etc. Not Grandma.

      What we need to be thinking about, if we're trying to get linux on average peoples' desktops, is those average people, for whom the 'dumb' OSX system is perfect. It does just get the files ontot your machine, where thay immediately work correctly with no configuration. The effectiveness of this approach is why we have Plug-N-Play, why we have the term zero configuration, and why Microsoft's new slogan is 'It Just Works.'

      Assuming the goal is for linux to gain marketshare against Windows, we need to make it 'Just Work' too.

      --
      Eagles may fly, but weasels don't get sucked into jet engines.
    126. Re:Beautiful by AKAImBatman · · Score: 1

      I've had a far far worse time with OS X installers leaving crap around than with the debian package system. But I don't then claim .debs are perfect.

      Indeed. But as I suggested to Bruce, there's no reason why a package management system doesn't still make sense for core APIs. That would play on the strengths of the two systems and give you the best of both worlds instead of trying to force one world to cover everything.

    127. Re:Beautiful by Nugget · · Score: 1

      Please explain how apt-get's inability to function for non-root users is contributing in any way to system security. As others have pointed out, apt-get's shortcoming in this regard does absolutely nothing to prevent users from installing software without root privleges. It's nothing more than a shortcoming of apt-get that it doesn't support this activity.

      If you, as an administrator, want to enforce the concept of no nonroot software installs, you'll have to do more than simply cripple the package manager. Since users do not have to be root to install software, your premise is flawed.

    128. Re:Beautiful by grumbel · · Score: 2, Insightful

      ### Do you really want to install a .deb package made by me?

      No, I don't want a .deb from you. I want a autopackage or a lsb-rpm or something else that will work on any distro. And thats not to much to expect, such a thing should be as normal for a programmer than a tar.gz, however sadly the whole Linux environment makes it rather hard to get a distro independed package done in the first place, so I can understand why people don't bother to provide them.

      That said there would of course be still the problem with multiple different architectures, but that could be solved by having a standard source+metadata format, that can be easily automatically build.

    129. Re:Beautiful by Anonymous Coward · · Score: 0

      On systems that aren't for development here we have /home and /tmp mounted noexec, meaning you can't download Realplayer and istall it on you home dir. It won't exec.

    130. Re:Beautiful by MostlyHarmless · · Score: 4, Insightful

      What do you do with something like OpenOffice.Org, then, which requires about 10,000 dependencies? Should each GTK+ application come with its own statically linked copy of GTK to be carried in memory separately for each app?

      The natural response, of course, is to say: "no, that's an unnecessary reduction ad absurdum. We can just declare (by some means similar to the LSB) that all applications must use GTK+ 2.4."

      But then what do you do six months down the road when you start to see applications written for GTK+ 2.6? Now, either you have to convince every application developer to stick with 2.4 (unlikely); distribute those applications statically linked (ugly, see above); or explain to your users why they have to upgrade to the next version of your distribution to run what they want to run.

      Given that sort of choice, I'd think most users and developers would rather work on making packaging systems more friendly instead of abandoning them altogether.

      --
      Friends don't let friends misuse the subjunctive.
    131. Re:Beautiful by Anonymous Coward · · Score: 0
      Packages are a great way to handle things for engineers, for linux enthusiasts, etc. Not Grandma.

      Why does everyone assume that once your child has a child that you become stupid and incompetent?

    132. Re:Beautiful by jusdisgi · · Score: 1

      So what's this, you've found the one guy on the Internet that says apt-get fucked up on him, and you also claim the same thing happened to you once? Ok, whatever. I've had Macs just stop booting, an OSX install fail on allegedly supported hardware and had a list of Windows breakage that needs to come in ASCII format on DVD. You are still full of shit, and "the slightest mistake" does not bring things "tumbling down." Apt-get is more than capable, and robust as hell...those of us who actually use it instead of whining about how Linux isn't MacOS and how "that debian install one time screwed up" know this full well. I have used apt-get successfully with zero problems on several machines. For years.

      --
      Given a choice between free speech and free beer, most people will take the beer.
    133. Re:Beautiful by cahiha · · Score: 1

      Install your own X system, then try to install X app from debian. It requires their install of X.

      Debian X11 apps have dependencies on Debian X11 client libraries, as they should; that's what dependencies mean. If you want to ignore those dependencies during an install, just tell apt-get to ignore dependencies; it has flags for that.

      There is a way to fake it, but after hours of trying, I failed.

      I see no reason why that should be any easier than it is. What you want to do, ignore dependencies, will likely not do what you want, and that's not Debian's fault.

      The correct thing to do is to let Debian install its dependencies and install your copy of X11 separately in /usr/local. If you are foolish enough to want existing packages to use your new shared library, use LD_PATH.

    134. Re:Beautiful by grumbel · · Score: 1

      ### Shouldn't you be using Synaptic for a fair comparison?

      That wouldn't change anything, since the limitations I mentioned are in the underlying way how packages are handled, not in the UI.

      ### At least that way, you don't have the problem of not finding the package, because it's in the list you are picking from.

      The example should show that even Debian doesn't have all software in their repository, not that it is hard to find.

      ### Along those same lines, when you complain about packages being out of date, again, they are, in the Apple or Windows world, with commercial software, how often do new updates come out?

      You missed the point, the issue is that a perfectly stable software is released by its creator, but there is simply no easy way to install it for the normal user, since the distro will take month or years till it has it packaged into a stable distribution. If somebody releases a game for windows they don't have to wait for Microsoft to release a new version of Windows to ship it to the common users, on the Linux side however that the normal way, at least if you don't want to bypass the package system.

      ### Most of your complaints seem aimed specifically at debian itself.

      Nope, all distros have pretty much the same problem. They all expect software to be centrally packaged and distributed.

      ### However whether OS X, BSD or Linux, you could always enable sudo for the users you trust not to screw up the system

      The point is that I don't want to become root AT ALL to install a piece of software, its my home dir, so why can't I dump the software there? It would also be much more secure to being able to test a package first in a isolated account then being forced to install it system wide.

    135. Re:Beautiful by dodobh · · Score: 1

      And when a bug turns out in a library that the application is statically linked to, you need to reinstall/upgrade every application using that library. You are looking only at one end of the spectrum, how do you make it scale up across a few hundred applications?

      Some people are happy running very few tools, others just need more tools.

      --
      I can throw myself at the ground, and miss.
    136. Re:Beautiful by squiggleslash · · Score: 1
      I thought about this one for a while, and the phrase "sledgehammer to crack a nut" struck me as not quite appropriate for what I wanted to say. The gist though is that there are minor problems that aren't really problems, just inelegancies, and then there are "solutions" to those minor problems that are actually, totally, 100% awful. And when it comes down to it, I think the general direction of the packaging systems for *ix is a primary example.

      Back in the late eighties and early nineties, for the most part, "installation" meant exactly what we're talking about is current in OS X, with the one exception that you generally had to tell "the system", somehow, where you'd copied the app. That is, under AmigaOS, you'd edit s:startup-sequence and put in an assign, under DOS you'd probably edit autoexec.bat and put in an entry in your set PATH= line, etc.

      This latter bit of the process was, quite seriously, the only bad part of installations. Most packages came with instructions on how to do this last bit, usually in the form of running a quick program after you'd installed the app. The rest was easy. Apple solved this, at the time, even then, by including proper metadata in the operating system.

      Time has passed, and now someone, somewhere, has declared this entire system, with or without the "you have to tell the OS where the app's installed" bit, fatally flawed. Why? Because if an application has a shared component, it might be installed more than once!

      And is this important? Well, apparently so. You see, the additional library will take up more disk space, and more memory, and you know how short we are of both.

      Now, there's room here for a little rant on how applications seem to have grown over the years disproportionally compared to (useful) functionality, but even leaving that aside, clearly memory and disk space are no longer considered the most important factors in computing right now. If I have two applications that manipulate MPEGs, and they both have a generic, half meg (let's be generous, 'cos it will not be that big), library for encoding MPEGs statically linked to them, is this a serious problem on any modern computer system? Or even any ten year old computer system?

      The point is this isn't a problem. It's an inelegance. We can see, at a glance, that a fix for this issue would be a nice-to-have, but nothing more.

      So what about the alternatives? Well, we now have half a dozen popular package management systems, varying from Slackware's "no dependency checking, read the documentation" installpkg system to Gentoo's "We're not just going to solve that minor issue, but we'll also solve the problem that your application is running 3-5% slower than it could do because it was compiled for the 80486" kitchen sink approach. What do these have in common? Are they elegant, trouble-free, approaches that result in applications running the way the developers intended?

      Well, by and large, not really. We now have DLL hell, half the installation systems require we run around trying to find obscure packages that we didn't realise we needed from the start, the systems aren't integrated with the file system, which supposedly is the gateway to the computer, so adding complexity to the entire process of understanding what you have on your machine, and for the most part we've also limited the flexibility of users when organizing their own machines. We've also added complexity to the physical system of storing applications, creating another central set of registries etc that can break. It used to be the worst anyone could do to a PC, forcing a reinstall of everything, was overwrite the FAT. Now the disk filling up during an app install can potentially cause the same problem.

      This is a fix? Because it looks to me like it's introduced more problems than it's solved. In fact, it looks like it hasn't solved any problems, it's merely added an ounce of hardware efficiency in exchange for a high degree of complexity. It's so bad that, in my e

      --
      You are not alone. This is not normal. None of this is normal.
    137. Re:Beautiful by Kiryat+Malachi · · Score: 1

      Yep. I don't ever *want* to do word processing, but sometimes I *have* to do word processing. That said, although I mostly do technical/engineering work, almost everything I work with regularly can be run on OS X; I know for a fact that some of it will not run on Linux. Of course, it all runs on Windows. Except when Windows doesn't run.

      All that said, even if the market does not consist solely of people who need doghouses, if 90% of the market needs only doghouses, the doghouse machine will be successful and the hammer mostly won't (this would be, for the dumb people who read my comments, the home user desktop market). Likewise, if 90% of the market needs the ability to drive a stainless steel spike into a brick wall, as well as assemble a doghouse, treehouse, person house, or life size girl-shaped frame, the hammer is going to do quite well (server market).

      --

      ---
      Mod me down, you fucking twits. Go ahead. I dare you.
      (I read with sigs off.)
    138. Re:Beautiful by myov · · Score: 3, Informative

      Mac OS X has a package system (.pkg) with a gui installer. However, Apple encourages developers to build an app that can just be copied to /Applications, rather than building a package. It's easier for the end user, and easier to keep the related files together - avoiding the "what app installed /foo/bar?" question.

      --
      I use Macs to up my productivity, so up yours Microsoft!
    139. Re:Beautiful by Anonymous Coward · · Score: 0

      You can try that by statically linking all of your binaries. Then, when some common library has a critical security vulnerability, you can have fun dragging and dropping 50 newly compiled applications onto your system, because every one of them needs to be updated, rather than one system file.

      This can be seen even today. For instance, the vulnerability a few months ago in Windows GDI, which required a tool to scan your hard drive for all applications that used their own copy of the library. Or, for example, whenever XPDF has a vulnerability, I'm required to reinstall everything that depends on it, because it can only be linked to statically.

      Self-contained programs have their own set of problems. They aren't an automatic fix, unless, of course, you can explain some magic to eliminate the above problem.

    140. Re:Beautiful by ivano · · Score: 1

      and some nice pre-binding too

    141. Re:Beautiful by Anonymous Coward · · Score: 0

      And still, you will probably be able to just compile the Gimp and install within your home directory not needing aid from the sysadmin for that.
      Yeah... that's what most of his post was about. If he can go and do that himself, what's the big deal about having the package manager do it for him? Because people have horrible reading comprehension?

      Last sentence, even: "You can of course work around them by compiling yourself, but didn't we invented [the] packaging system to avoid exactly that.".

    142. Re:Beautiful by AKAImBatman · · Score: 1

      So in summary, you're fighting anecdotal evidence with even less anecdotal evidence? :-)

      Allow me to go for the gold and get a "win" in the anecdotal argument. (As much as a "win" means anything.)

      Google Groups: APT package database broken (4,890)

      Stating that APT is unbreakable is an undefensable position. Everything is breakable. It just so happens though, that packaging systems are seen as far more breakable than more traditional install methods, and lack many of the features of such installers. For example, there is no APT solution when I can't find VLC/XFCE/Bob's Cool Script Library/[insert your favorite package that is commonly missing] in the repository. And there's definitely no APT solution for software that CAN'T be in repository. (e.g. Oracle, Real Player, Java, etc.)

      So, are you going to keep swearing at me for attempting nothing more than an enlightened discussion, or are you going to acknowledge that some issues exist and then discuss how they might best be solved?

    143. Re:Beautiful by Anonymous Coward · · Score: 0

      For a regular UNIX user, the Macintosh is painfully limiting.

      What, specifically, is the mac missing?

    144. Re:Beautiful by lowmagnet · · Score: 1

      One thing you didn't mention about framework packages, and it's something I think is cool, is that Apple's framework packages generally contain every version of the framework including minor revisions. It may make libraries bigger, but each app can continue to run without dependancy issues like "You're running libC 10, and this program is libC 9"... At least in theory. I've never had an app come up and tell me a library is missing or broken in OS X, but it has occurred several times in the windows world at work.

      --
      Heute die Welt, morgen das Sonnensystem!
    145. Re:Beautiful by grumbel · · Score: 1

      ### But if you want to install the bleeding edge version of gimp, why don't you just do it the windows way? By downloading it from the web site?

      The webpage doesn't provide anything that the user can install easily, just source and links to the official Debian packages.

    146. Re:Beautiful by zootm · · Score: 1

      I want to download a .deb (or whatever package format you want) and double-click it, and I want that to be it installed. If there's dependencies, go fetch. Playing with sources.list is not an option.

    147. Re:Beautiful by javaxman · · Score: 4, Informative
      If you need libraries you're going to have to install them. OSX might want you to put everything into a single statically linked binary but it really doesn't work that way, except for very simple applications..

      1) 97% of all applications fall into the "very simple applications" category, if needing libraries not already installed with OS X is your metric. The point the parent was trying to make is that Apple errs on the side of providing everything by default- they've given up on trying to keep the OS footprint small. Unless it's code specific to your app, it's likely already provided. Please provide an example if you want to refute that point- maybe there's something they should be including that they don't.

      2) It doesn't actually have to be a single statically linked binary- that's just what most programmers do, because it's simple, and easier for the user to manage if you have everything self-contained in the application package. If you want, you can create your own application frameworks, and place them in standard locations ( not /usr/local, but rather /System/Library/Frameworks or ~/Library/Frameworks ). Frameworks have certain advantages ( versioning support being just one ) over standard dynamic libraries, and they're quite easy to use. Most OS X programmers don't do that because, well, they don't want to have to write an uninstaller.

      Just because OS X is 'like Unix' doesn't mean that's all it is. I don't even want to know what you're doing to your mini that you've felt the need to reformat and reinstall twice. That's just crazy. May I recommend Fink for your Unix-ported program needs? The /sw directory is an excellent idea...

      I've seen prepackaged binaries ( generally of ported Unix apps ) which write into /usr/local, and I have to say I personally dislike that practice. That said, if you choose to go that route and use /usr/local, managing it is no different than under any other OS- you have to do it yourself.

    148. Re:Beautiful by jusdisgi · · Score: 1

      Well, if I argued against letting everyone install things system wide, it was only because I did not even entertain the stupidity involved in complaining about not being able to install things in your home directory. BECAUSE YOU CAN. So, even worse than the point I thought he was trying to make, he was making a fictional point.

      So whatever. Maybe I misunderstood it. But it was only because I was giving him too much credit.

      --
      Given a choice between free speech and free beer, most people will take the beer.
    149. Re:Beautiful by resiak · · Score: 1

      Synaptic doesn't have a database of its own. It's just a frontend to apt, which uses the repositories you give it. You're referring to the out-of-date packages in Debian, aren't you? Erm, well, they're not bleeding edge, I'll give you, but the versions in testing (apart from right now, because of freezing things while Sarge releases) are usually up-to-date within days of new versions being released upstream. Oh, and don't pull out X.org here -- that's on its way, and again was held up by Sarge. "Complete"? I can't think of the last thing that wasn't in Debian that I wanted to install. Sorry, try again.

      (If you're feeling suicidal, use Ubuntu's unstable stuffs. They're up-to-date, but break more often than Sid. That's the choice you make.)

    150. Re:Beautiful by Afrosheen · · Score: 1

      OpenOffice is a super fat bastard anyway, what's the issue of shipping it with all of it's dependencies and having it run out of a specific location? Yeah, it's ugly, but it's effective, and size is already a bygone issue with it.

    151. Re:Beautiful by Todesmetall · · Score: 1
      you install something that isn't packaged with your distros packaging system you break the package management completely

      I've never actually seen this happen myself, but I'll take your word for it :). Anyone have any horror stories to share? Does it happen with actual packages, or only if you install from source?

      Try installing your software into /usr/local. When using a tool like stow, you can uninstall the software you have compiled from source. The package database remains completely unaffected.
    152. Re:Beautiful by WorLord · · Score: 1

      On my stock Ubuntu Hoary system, I open the program called (oddly enough) "package manager". I type in the name of the program I want in the "search" field, or browse for a program from a list, click the little box on the side of it, and push the "go" button.

      It does the rest.

      I don't even have to find and then go to a 3rd party website to download a file - I just launch software that is built in to my OS, and it does the finding, downloading, installation, and menu generation for me. If I know the name of the program I want, its as good as installed.

      From where I sit, not having to track down a .dmg or .exe is exactly one less thing I have to go through to install software (when compared to Mac or PC), which means I have most "mind-numbingly simple" time of it (out of the three options discussed here).

      I would talk about things I can't find in the repositories, but I honestly haven't had need of a program that wasn't in the repositories... so I've no experience with that.

      Now, if you're referring specifically to RPM based distribution, I'm not sure I can disagree with your synopsys. I do recall having some of these types of issues with RPM based distros before. (Source based distros are just out of the conversation, of course).

    153. Re:Beautiful by Daengbo · · Score: 1

      Well, since there are like a million and a half Linux ditros (approximately 1.3 for every user), I would suggest that the need is not that great.

      Really, if you are in a multi-user situation on your workstation, the admin likely won't allow you to install anything without approval, and if you are using your computer at home like a single user, then you can just type the root password (or your own for rootless distros) at the prompt.

      Bottom line is that I install programs to /home all the time on my own machine, but anything multi-user would get a noexec mount, anyway.

    154. Re:Beautiful by Anonymous Coward · · Score: 1, Insightful

      Try telling the Firefox crew to abandon XUL and use pure GTK+ or QT.

      Bad example. XUL is not a library that is loaded externally. It renders to GTK on linux. It renders to carbon or cocoa on mac.

      A correct example would be that you wuold have to choose either GTK or Qt for development of GUI's on linux, and to that I say: please do it, soon. There is nothing as irritating as having app Foo that you really really want using interface paradigm A, and app Bar that you really really want using interface paradigm B, which is the case on any real world Linux desktop used for real work right now, because there is always that one Qt app you want to use on your GTK desktop, or the other way around. There is simply not enough room for two base widget toolkits on a single desktop. Not if you want it to be usable and integrated. The conceptual differences between GTK and Qt should be layered on top of a base library which they both use, just like what happens on the mac and on windows.

      Linux, I think, does as well as it does because it can rally such a vast array of applications, and it does that by supporting applications using the console, pure GTK+, QT, GNOME, KDElibs, FLTK, Edje, XUL, Mono, or whatever takes your fancy.

      What universe do you live in? Linux on the desktop is a failure. Despite being free in all senses of the word, it has even less marketshare than OS X, an OS which only comes bundled with rather expensive niche hardware. The reason is quite simple: UI chaos because there is no cathedral. I abandoned linux (specifically debian) because I realized that FOSS programmers, despite understanding you need leadership to keep a clean codebase, do not understand you need leadership to keep a clean user interface.

      Desktop linux will remain an also-ran until the FOSS crowd groks this and works out some way to let knowledgeable people tinker while keeping the interface for users across the entire system integrated and standardized.

    155. Re:Beautiful by jusdisgi · · Score: 1

      Just because you can't install packages through the package manager without a root password (or sudo elevation) doesn't prevent the user from running other programs (that don't require the package manager, and don't need to be compiled if you don't allow user access to gcc) from his home directory.

      Ok.....then what the fuck is your point in the first place? You can install software in your home directory in Linux. If that's what you were talking about, then you weren't just advocating bad system policy, you were just plain fucking wrong. That's not what the package manager is for, and it doesn't keep you from doing it. The package manager is for system-wide software installation. Which explains why I assumed that's what you are talking about. Because you were bitching about not being able to use the package manager as a normal user. A normal user shouldn't have access to the package manager because they shouldn't be allowed to install software system-wide, and that's what the package manager is for. If you want to install software in your home directory, fine, go ahead.

      So it turns out you never had anything to bitch about in the first place, and were just making shit up. And as for the 15-yr old Linux asshole bit, let's examine 3 things:

      1)You're the one posting AC
      2)My user number should give you an idea of how many years I've been here, which should preclude such a young age
      3)Given that I'm the one here that seems to have some basic idea of what you can and can't do in Linux (and yes, even maybe why that is) you're coming off as the asshole.

      So please, shut the fuck up.

      --
      Given a choice between free speech and free beer, most people will take the beer.
    156. Re:Beautiful by RFC959 · · Score: 1
      Until application developers start packaging dependencies together with their app, linux will not take over the mainstream mom and pop user market.


      Here's my standard answer to that: who cares? Why do we want Linux to "take over the mainstream mom and pop user market"? Does Lamborghini argue that they should add an automatic transmission and an inline four-cylinder to the Murcielago so your mom can drive it to the post office? Different strokes for different folks, and the right tool for the job. Let Mom & Pop use the pointy-clicky stuff, and leave our low-level hacking alone, please. Besides which, if every application developer packages all the dependencies with their software, packages are going to get huge, and you're probably going to end up with multiple versions of a bunch of things on your system, because different packages dragged in different versions of the same dependency.
    157. Re:Beautiful by mmkkbb · · Score: 0, Flamebait

      I can't think of the last thing that wasn't in Debian that I wanted to install. Sorry, try again.

      You haven't tried to get Java running on Ubuntu, have you?

      --
      -mkb
    158. Re:Beautiful by lowmagnet · · Score: 1

      It's ok that GNUStep .apps are just folders; this is the way NeXTStep and Mac OS X do it as well. You could set your file browser to make .apps executable. It changes nothing at the command line, however.

      --
      Heute die Welt, morgen das Sonnensystem!
    159. Re:Beautiful by Anonymous Coward · · Score: 1, Insightful
      Well, if I argued against letting everyone install things system wide, it was only because I did not even entertain the stupidity involved in complaining about not being able to install things in your home directory. BECAUSE YOU CAN. So, even worse than the point I thought he was trying to make, he was making a fictional point.

      The point is that you CANNOT .. if you are using a package management system. What we need is a hierarchical package system. The base stuff provided by the admin to all users. When a user downloads a .deb or a .rpm and installs it locally, the package management _client_ should automagically do the right thing. The right thing is to use the stuff that's common to all users (maybe add a refcount) and follow dependencies to add other stuff locally. When you remove an app, then you remove the local shit (it doesn't affect anybody else) and drop the refcount to the global system level stuff by one. Of course you can have a malicious client that insists on not dropping the refcount .. but that doesn't sound like such a big deal. to reiterate - yes, users can install apps in their home dirs .. but for that they need to compile from source. It's gotta be made easier .. come on, this is 2005 - not 1996.

    160. Re:Beautiful by grumbel · · Score: 1

      ### You can install software in your home directory in Linux.

      Yes, you can. However the distros packagemanager and the distros package repository is completly useless for doing so and thats exactly the point of why apt-get isn't a very good solution for handling software. It works great for some uses, but completely fails at others.

    161. Re:Beautiful by Anonymous Coward · · Score: 0

      The entire philosophy behind X-Windows is that you can make it look and feel however you want. I personally don't like the look-and-feel of either Mac OS or Windows at all. But can I change it? NO! Because the interface for users across the entire system is integrated and standardized.

    162. Re:Beautiful by jusdisgi · · Score: 1

      Now we get to the heart of the issue. What you're saying is directly analogous to "Apache isn't a very good web browser."

      That's not what apt-get is supposed to do. Let it go.

      --
      Given a choice between free speech and free beer, most people will take the beer.
    163. Re:Beautiful by lowmagnet · · Score: 1

      Of course, NS apps are already compiled by the time you get there, so Rox is a little different. If there was a binary Rox equivalent, then that would be like a NS app.

      --
      Heute die Welt, morgen das Sonnensystem!
    164. Re:Beautiful by toddestan · · Score: 1

      If you need libraries you're going to have to install them. OSX might want you to put everything into a single statically linked binary but it really doesn't work that way, except for very simple applications.. that's why you build .pkg scripts to install things into the right places on the hard drive.

      Unfortunately because there's no uninstall your hard drive gets clogged up with all the apps you've installed and you eventually have to reformat. I've had to do this twice since I got my Mini due to libraries and whole applications sticking themselves on the disk and unable to remove them.


      Why am I suddenly reminded of Windows 3.1?

    165. Re:Beautiful by jav1231 · · Score: 1

      OSX doesn't allow this either. You might be able to run it out of a dmg, but installation almost always involves an admin pw.

    166. Re:Beautiful by bnenning · · Score: 1

      t's not that Apple has magically figured out which packages make most real-worlddevelopers happy, it's that Apple's developer and user community has become reduced to a group of people that happen to be happy with very little.

      Yeah, just those irrelevant toy applications like Office and Photoshop. Come on.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    167. Re:Beautiful by m50d · · Score: 1

      I was thinking more in terms of distributing them. It's hard to download a folder, and harder to email one.

      --
      I am trolling
    168. Re:Beautiful by jsebrech · · Score: 1

      But from a standpoint of supporting a diverse ecology of software producers and lots of competition, the cathedral isn't the most desirable structure.

      Systems design is nothing like nature. Evolution is incredibly messy and wasteful with resources. There is no reason to argue it is the most efficient system imaginable, even when it comes to protecting against outside threats. I think a good cathedral can get much more done with much fewer resources than a good bazaar.

      I see this mirrored in open source projects, where all the really successful ones have a core leadership that has strongly dictated direction for the project. Sometimes you even see this happen within a project, where they "break through" because they changed to a more cathedral-like system, like how mozilla became firefox and suddenly soared. Even the pet project of the bazaar crowd, debian, is strongly cathedral-like, with no tolerance for diverging from policy.

      It seems that when one pays a draconian cost (central control) to solve smaller problems (package dependencies, file locations), it might not be the best deal in the end. I'm still endeavoring to provide a better solution to this problem.

      You just fear government. I don't blame you. But there is not yet a form of organizing effort into productivity that does not require government. If you invent one, very well, but, for now, government is still the best model of organizing effort. Sometimes the perfect is the enemy of the good. For me avoiding cathedrals because they are not perfect does just that.

    169. Re:Beautiful by Anonymous Coward · · Score: 0

      But then what do you do six months down the road when you start to see applications written for GTK+ 2.6? Now, either you have to convince every application developer to stick with 2.4 (unlikely); distribute those applications statically linked (ugly, see above); or explain to your users why they have to upgrade to the next version of your distribution to run what they want to run.

      Or, you could just engineer your system so 2.6 always extends 2.4. Like how new versions of X11 extend the old versions, instead of modifying them. That does require a lot of forethought and elbow grease, but nobody ever said good things are easy to get.

    170. Re:Beautiful by SdnSeraphim · · Score: 1

      This issue cannot be solved with a specification by committee. The reason OSX and XP can do thing that seem better than package managers is that they control the operation of the OS. They don't rely on a group of 1000 people to try to figure out how 10000 other people can use an installer/package manager. They just put whatever hooks they need into the filesystem or the kernal. The problem with committee is that there is no personal accountability. For Apple, the people that develop the specs for software installation have personal accountability to complete their work and do it well. No non-company committee has this "fear."

      For open source, the task is near impossible. First if you want to put hooks in the kernal/FS/OS to be shared by all distros, requires the buy in from a great number of people, ie. a committee.

      What I think is the most interesting is that we are not looking outside of what we already have. We have package managers; we have x number of groups that think that their package manager is better than the others; we have x number of groups that want better package managers. Why are we not stepping back from the idea of a package manager, and start with requirements and and current limitations? Then come up with a set of things we need in order to accomplish all of the requirements, ignoring current limitations. These "things" might have a wide ranging effect on all parts of the GNU/Linux system. From filesystem, kernel, to executable changes.

      I don't think we will have any better software distribution and management until we can pull back from the immediate needs and look at blue-sky possibilities and change all parts of the OS to accomodate a better solution.

      I do not have hope that it will ever happen.

      --
      It is dangerous to be right on a subject on which the established authorities are wrong. - Voltaire
    171. Re:Beautiful by Anonymous Coward · · Score: 0

      This can be seen even today. For instance, the vulnerability a few months ago in Windows GDI, which required a tool to scan your hard drive for all applications that used their own copy of the library. Or, for example, whenever XPDF has a vulnerability, I'm required to reinstall everything that depends on it, because it can only be linked to statically.

      That's why libraries that are that common should be provided by the OS, not the individual developer.

    172. Re:Beautiful by grumbel · · Score: 1

      ### That's not what apt-get is supposed to do.

      Now thats a great argument. If that is really the case I would call that broken by design, but could you care to give some details why exactly it wasn't supposed to handle such a situation? After the only difference between installing as root and installing as user is the $PREFIX, something reasonably easy to fix if one tries to. There are of course packages that have to be installed as root (kernel and such), but they are by far the minority.

    173. Re:Beautiful by dr.badass · · Score: 1

      The simple & dumb way as OS X handles packages is just that: it can not handle dependencies, or anything

      Yeah, but with the advantage that you don't *need* to handle dependences the overwhelming majority of the time, because there's really only one version number the app should care about. Apps don't need to be statically linked, they just need to be linked to things that are part of the default install. Instead of worrying about foo 2.1.4b, bar 0.7.1, and baz 1.0, you can just say "This app requires Mac OS X 10.4 or later."

      The open source way is more flexible, granted, but so far it's been total crap for a mainstream desktop. I think that desktop distributions need to step up and say "We're only going to support these packages for now, so don't use anything else if you want to run on our distro." Otherwise, they're never going to have a stable foundation for people to build upon.

      --
      Don't become a regular here -- you will become retarded.
    174. Re:Beautiful by Shalda · · Score: 1

      Single file programs really don't preclude common dynamic libraries. There shouldn't be any reason you can't drag and drop Java or GTK+ on to your system and have other programs be able to call them. This I think would be preferable to programs installing select pieces of different libraries and runtimes. From a programming perspective this shouldn't be any different than the way one works with a Java or .NET namespace or creating a COM object.

      Really, though, I'm more talking about the user experiance. The typical user should never know that a program is more than just one file. And from the system manager perspective, it should also be just that easy.

    175. Re:Beautiful by JabberWokky · · Score: 1
      It looks like it was designed with the same kindergartners-on-crack design philosophy that makes KDE so colorful and cluttered.

      Part of that is likely because it is using nuvola, a KDE icon set.

      --
      Evan

      --
      "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
    176. Re:Beautiful by rbanffy · · Score: 1

      I think decent package managers are way better than DLL Hell. I think dependency hell is way better too.

      If you want to avoid it, reduce the complexity. If you think you can do a better job, create a Debian-derived distro and simplify it. Support only one version of GTK, gcc, Python, Perl. Support only a handful Gnome or KDE apps, have PostgreSQL as your only RDBMS and Apache as your only http server.

      Keep automated tests for all packages.

      You could also create "superpackages" that install other packages and all their dependencies in a single consistent and verified process.

      I can't se the point of this discussion.

      And yes, Symphony looks great.

    177. Re:Beautiful by DLWormwood · · Score: 1
      And OS 9 junkies hated the fact that this mecanism is based on the file extension...

      As a former OS 9 junkie, I personally liked the mechanism, but when the concept was introduced with OS 8.6 with CarbonLib soon after The Steve's return, they used a "bundle bit" to make the system more Mac-like. The ".app" extension found on OS X bundles was originally intended to be optional if a bundle bit and PkgInfo file were found, but some of the NeXT veterans tried to mandate file extensions with a very infamous technote that Apple had to quickly pull...

      Bundles/packages really are a good compromise between flat file systems and resource forks. While I still think the Resource Manager was a brilliant concept, several shortsighted design decisions made during the early '80's rendered it unscalable (confusion between 16-bit, 24-bit and 32-bit offsets) and insecure (read: virus prone), hence the migration to bundles even on HFS volumes under OS X.

      --
      Those who complain about affect & effect on /. should be disemvoweled
    178. Re:Beautiful by mpe · · Score: 1

      First of you can't install a application as a user, now how stupid is that?

      A very sensible one. In the vast majority of cases users are there to use a computer, not play at being sysadmins.

      If *I* want to install a bleeding edge version of Gimp, I neither want to bother the admin with it nor do I want to force it an all the others users, yet Debian requires me todo exactly that.

      This is only an issue if you are trying to install the software on someone else's machine. If it is actually part of your job to evaluate "bleeding edge" software then you will either have access to a computer specifically for that purpose or know how to install the software somewhere you have write acess to. If you are trying to install software on your employer's computer(s) without authorisation then they are perfectly entitled to fire you. Since this is also against criminal law in many parts of the world you could face a difficult time getting another job too.

    179. Re:Beautiful by HuguesT · · Score: 1
      So far EM64T hasn't proved to be the performer one would expect. Whereas AMD64 extentions improve performance on AMD chips, they don't seem to on Intel hardware according to various benchmarks.


      Redhat mentioned this in their realease statement:
      "Software IOTLB -- Intel EM64T does not support an IOMMU in hardware while AMD64 processors do. This means that physical addresses above 4GB (32 bits) cannot reliably be the source or destination of DMA operations. Therefore, the Red Hat Enterprise Linux 3 Update 2 kernel "bounces" all DMA operations to or from physical addresses above 4GB to buffers that the kernel pre-allocated below 4GB at boot time. This is likely to result in lower performance for IO-intensive workloads for Intel EM64T as compared to AMD64 processors."



      Moreover the preview cross-platform developer toolkit released at the time of the JobsTalk is 32-bit only.

      All in all I'm not sure we are moving forward here.
    180. Re:Beautiful by TERdON · · Score: 1
      it might be installed more than once!

      Actually, that's not really the problem, it would actually be wanted sometimes (eg a web developer having both FF1.0 and FF1.1 installed for compability checks).

      The problem is, when you have none of them installed, stuff won't work anymore. And there are cases where packing absolutely everything together in one executable is just silly (gallery, phpmyadmin, content management systems, which all have dependancies to mysql, apache, mod_php, lots of other stuff).

      Actually, lots of the reason Windows and Mac OS X get away without using package management is that both of them have a culture with a lot more of monolithic executables, with lot less updates to them. Basically, there haven't been any big need.

      --
      I have a really elegant proof for Fermat's last theorem. If this sig was only a bit longer...
    181. Re:Beautiful by crawling_chaos · · Score: 1

      And Sarge will probably still be the "stable" release when XP is EOLed. That is my point -- the "better" way ain't better if it takes years longer than its rivals to reach the exact same level of frustration. As the parent poster noted, apt-get is no panacea to package management woes.

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    182. Re:Beautiful by jbohumil · · Score: 1

      Ultimately perhaps applications will be deployed as entire virtual machines each containing exactly what is need to run that application perfectly. Tag onto that virtrualization a SOAPish interface that the meta-machine can query and dynamically adapt an interfaces to the available functions.

    183. Re:Beautiful by moof1138 · · Score: 1

      >For a regular UNIX user, the Macintosh is painfully limiting.

      For a regular UNIX user there are Fink and DarwinPorts, if a regular UNIX user is suffering it is because they don't know what is available to them, not out of a limit of what is available.

      --

      Hyperbole is the worst thing ever.
    184. Re:Beautiful by Anonymous Coward · · Score: 0

      How does a distro not supporting the right version of some software fix dependency hell?

      I download a wiki program from sourceforge, try to install it, install fails because version blarg.0+ of MySQL is required and your distro only supports PostgrSQL

      How does that help anything?

      Never being able to successfully install anything that wasn't included with the distro was my #2 reason for abandoning linux.

    185. Re:Beautiful by Coryoth · · Score: 1

      The security model of (most) Linux systems still assumes the fact that a binary being on the hard disk means that it should be entitled to every single permission associated with the user when run.

      I think it is important to note that this is the security model that is on the way out. LSM and whatever hooks to it (be it SELinux or something else) veers notably away from this model. We shouldn't be making any assumptions or else we'll end up in a morass similar to that Windows is in where every application assumes that it is perfectly reasonable to ask for full Administrator priviliges all the time.

      Perhaps it is time Linux installs started looking into SELinux and seeing how they can take advantage of that to make user installs easier, yet still able to be suitably and elegantly locked down.

      Jedidiah.

    186. Re:Beautiful by squiggleslash · · Score: 1
      Actually, that's not really the problem, it would actually be wanted sometimes (eg a web developer having both FF1.0 and FF1.1 installed for compability checks)
      This appears to be a reply to a, presumably unintended, quote out of context. I was talking about two apps with a shared component, where the shared component would end up being installed more than once if you go the monolithic, avoid-external-dependencies, route. Not two of the same app. ie in the example I give, both apps would have (statically linked) copies of the MPEG library. The intention behind package management systems was to get away from this, have the MPEG library a separate dependency, and have the two apps share the same copy, hence increasing efficiency.
      --
      You are not alone. This is not normal. None of this is normal.
    187. Re:Beautiful by BasilBrush · · Score: 1

      OS X only requires an admin password if it's an installer and needs to write to a system directory that you as a normal user don't have access to. So the apps that you can run from a DMG are not the same ones that require a password. If you can run it from the DMG, you can drag'n'drop it to the applications directory to install it with no fear of a password being asked for.

      Most non-Apple apps are installable by a user into their user applications directory without a password.

    188. Re:Beautiful by cahiha · · Score: 1

      Yeah, just those irrelevant toy applications like Office and Photoshop. Come on.

      Bad dependency management on a platform doesn't lead to "toy" applications, it leads to bloatware, as every vendor packs everything into every application. Photoshop and Office are actually good examples of that--that's why those systems come with their own toolkits, libraries, development environments, and scripting languages.

    189. Re:Beautiful by mpe · · Score: 1

      You missed the point, the issue is that a perfectly stable software is released by its creator, but there is simply no easy way to install it for the normal user

      Why do you think that it's a sensible idea for users to be installing software in the first place? Do you refuse to buy electrical appliances which have a "No user servicable parts" sticker on them...

      Nope, all distros have pretty much the same problem. They all expect software to be centrally packaged and distributed.

      The great thing about open source is that if you don't like they way something is done you can change it. Unlike proprietary software, where it's a case of "like it or lump it".

      The point is that I don't want to become root AT ALL to install a piece of software, its my home dir, so why can't I dump the software there?

      In which case you can simply build the software to work in that environment.

    190. Re:Beautiful by metamatic · · Score: 1

      Frankly, I'm not going to take any lessons in package management from anyone responsible for the abortion called AutoPackage.

      There is absolutely no way anyone competent would design a package format that consisted of an executable shell script containing more executable shell scripts, with no way to unpack other than to execute unknown code. It's just screaming out for trojanizing.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    191. Re:Beautiful by Ilan+Volow · · Score: 2, Insightful

      I've found that geeks (especially OSS ones) are often unable to understand the concept of an engineering tradeoff that makes a sacrifice in program's technical elegance and efficiency to gain a better and more robust experience for end users. That's what the app bundle system basically is, an engineering tradeoff that Apple made to benefit users that placed a higher priority on usability robustness and consistency than efficiency and elegance of design.

      I liken witnessing OSS developers attack the app bundle system to watching people who design economy cars for a living yell and scream about how a tank has really lousy fuel efficiency because of all of the bloat of that uneeded heavy armor.

      --
      Ergonomica Auctorita Illico!
    192. Re:Beautiful by BasilBrush · · Score: 1

      It's not a problem, three different levels of user. Admin, can install programs for everyone. Power user, can install programs just for himself, that don't need to make any system changes. Untrusted user can not install programs, and might be limited in which of the already installed programs they are allowed to use. OS X provides all three. The later is an option on a user account called "Simple Finder".

    193. Re:Beautiful by TERdON · · Score: 1
      The same situation of course applies to shared components too, not just web browsers.

      I also gave some typical examples for "monolithic" packages that just don't work. Would you want three installations of apache+mysql+php just because you installed Gallery, phpmyadmin and a content management system? I guess not, and there are lots of other examples with more "traditional" examples. Basically, the Unix philosophy doesn't work that way...

      --
      I have a really elegant proof for Fermat's last theorem. If this sig was only a bit longer...
    194. Re:Beautiful by mpe · · Score: 1

      If I were an IT admin (I'm not - I'm a developer), I'd want to not allow users to install software for that very reason. They install crap like real player or yahoo toolbar or whatever that bog down their machines, then the whine when their machines bog down.

      If they can do this then they can also install actual malware capable of deleteing/corrupting data, sending sensitive data anywhere on the planet, etc.

      But for home users it's imperitive that they be able to install software and IMO they should not have to be root to do so.

      Even then there is little reason for installing software to happen often. Why should a computer not need to be put into a a different mode in order to change its workings? People can accept this with domestic appliances, so why should computers be different...

    195. Re:Beautiful by squiggleslash · · Score: 1
      Good comment!

      A lot of this can be resolved by making intelligent decisions about what you're going to incorporate into the operating system and how you're going to structure it.

      In the above case, you'd probably want to structure Apache as having a plug-in architecture, so the dependency on Apache is relatively obvious. I, personally, would also include it as part of the OS (as I said in my original comment, I think you should try to incorporate as much into the OS as possible within reason to remove the need for third party shared components.) PHP would be reasonable as part of the overall "Linux Web Services" package this'd be a part of.

      MySQL I'd try to remove the dependency altogether, I'd rather the OS have a crude/generic DB (which could be MySQL) and ODBC-type framework built in for connecting to it or alternatives to it, and applications attempt to use it. I don't think I'm exaggerating much when I say the whole "Apps that need databases" thing is due for a serious rethink in general too.

      Good example though, and one that anyone making a decision about how to put together a GNU/modified-Linux distro that integrates application management with object management should consider.

      --
      You are not alone. This is not normal. None of this is normal.
    196. Re:Beautiful by the+phantom · · Score: 1

      The contrast is the fact that the central repository simply doesn't even exist for Windows or MacOS...

      I think that you are kind of missing the point. There is no central repository for MacOS because it is not needed. There are no real packages, because they are not needed. An application is the package. Everything that is needed is in the .app bundle. For most users, and for mot programs, this is a great way to handle things. Dependencies are either in the system by default (which includes the kitchen sink), or they are built into the package, or they are included in ~/Frameworks (or /Library/Frameworks). Developers are left to maintain their own programs, and they don't (generally speaking) have to worry about package management. Users don't have to futz with package management, because it is dealt with transparently. I am sure that we in the Mac world are missing out on something, but I haven't yet seen what.

    197. Re:Beautiful by Daytona955i · · Score: 2, Insightful

      Wow, what a Troll. I normally don't feed trolls but what the hell...

      First of you can't install a application as a user, now how stupid is that? If *I* want to install a bleeding edge version of Gimp, I neither want to bother the admin with it nor do I want to force it an all the others users, yet Debian requires me todo exactly that.

      It's not stupid at all and is in fact what OS X does and what windows is slowly moving towards. Fact is, if you aren't a trusted users, you shouldn't be installing anything. On a multi-user system, the admin can give you sudo access to be able to install things. Allowing anyone to install anything is just plain stupid. If you want a cutting edge version of gimp, download and compile it in your home directory. You definately should not be able to install it system-wide no matter what package management system you have.

      Secondly Debian packages work great, but only for stuff that is in Debian, which might be a lot, but is *far* from everything and its also often *way* outdated, remember those three year release cycles.

      Spoken by someone who must not actually use debian. Sure debian stable is a little behind but remember, it's *stable* meaning that buggy cutting edge program won't be there. However there is also testing and unstable which contain much more recent versions of things.

      Software packaging should be done by those that provide the software in the first place, the distro might run a quality check on it, but thats it.

      Sure that would be great and it happens to some extent but I don't expect the author of a program to package their program up for each distro. The only way that this would happen is if there was only one package management system. But there's not and probably never will be. Different flavors of Linux put things in different spots... If they didn't, there would really be only one distro of Linux.

      There are very few programs that I have not beed able to find a .deb for. Usually because it's a relatively unknown program or carries a restrictive license not allowing it to be redistrubuted. (Such as Java)

      So maybe you should shut your mouth unless you know what you are talking about.

    198. Re:Beautiful by BasilBrush · · Score: 1
      Yes, OS X has /usr/local/lib for compatibility with any simple *nix ports. Most are entirely empty. Mine is empty. It's not how Mac apps are supposed to work. The grandparent had the right idea.

      I've had my Mac years longer than you've had your Mini, and no it never needs a reformat. Nor have I heard of any other Mac user needing to. You appear to be blaming Mac OS for the faults of the *nix applications you are using.

    199. Re:Beautiful by Anonymous Coward · · Score: 0

      You must be new here. 1. People posting AC are no less likely or unlikely to make valid points than people with UIDs. 2. Your 6xx,xxx user number is ridiculously recent-looking to some of us (my own UID, when I bother to log in, is in the high 1xx,xxx range). It seems to me that you could very well be 15 and have the user number you do. In fact, I've seen some pretty advanced postings on technical boards from people who are in their early teens, so I don't that age is necessarily an advantage or disadvantage in these discussions. 3. I am not the AC you were arguing with and I think this whole debate about package managers is stupid.

      In the future, please simply ignore ad hominem attacks like that. It's a sure fire sign that the other person is either a) an idiot, or b) trying to rile you up.

    200. Re:Beautiful by Anonymous Coward · · Score: 0

      You've put your finger on the available options.

      The problem is not the technologies available.
      I think the problem is that most package creators are lazy and they opt for what is easiest for themselves, which, to use your example, would be to just build a package for GTK+2.6 and ignore their GTK+2.4 user base.

      How hard is it to build a package against GTK+2.6 and another against GTK+2.4? Maybe that's where improvements should be made. Make it easier for package creators to spit out appropriate builds for their actual user base.

      If a package creator has updated every other package on his development system, great for him, but he really ought to be targeting at least the top few environments that are actually being used in the real world, right? Try to keep oddball stuff to a minimum, or just statically link the oddball stuff, and offer multiple builds for the dynamic stuff like GTK+2.4/6.

    201. Re:Beautiful by Anonymous Coward · · Score: 0

      Yeah, just those irrelevant toy applications like Office and Photoshop. Come on.

      If OS X is so easy to port software to, and so nice for developers, then how come it is the ONLY DESKTOP UNIX SYSTEM that does not have a native-looking port of OpenOffice.org 2.0, let alone a native one?

      If Linux and Windows are blown away by the Mac's functionality and ease of use, why do they both have native OpenOffice.org ports, and Mac users have to use NeoOffice/J which is slow, relies on Java, and is an entire major version behind?

      Could it just be that the Mac is a bitch to port software to without basically rewriting it from scratch specially for it (like Office and Photoshop were)? Why, I do believe it could!

      That's what the Mac is: absolutely wonderful for users, very nice for developers who only want to write Mac software - and a royal pain in the butt for anyone who's trying to produce portable software.

      Sorry, but it's true.

    202. Re:Beautiful by mpe · · Score: 1

      No, I don't want a .deb from you. I want a autopackage or a lsb-rpm or something else that will work on any distro.

      Including being able to handle a distro which postdates the program in question.

      And thats not to much to expect, such a thing should be as normal for a programmer than a tar.gz,

      In which case you need to either write one or pay someone to write one...

    203. Re:Beautiful by Anonymous Coward · · Score: 1, Insightful

      Just because OS X is 'like Unix' doesn't mean that's all it is.

      Right. So when Mac zealots want to make OS X sound good, they tell us it's Unix, no really it is, it's got BSD code in it and everything, it's UNIX!!!!!1111. And when it turns out that using OS X as though it were Unix is a quick and easy way to break it, they say no, stupid, of course you can't do that, it's not Unix, you need to port all that Unix software and make it play nicely with the Mac.

      Make your mind up, okay, people? Either OS X is Unix (in which case we can criticise its failings as a Unix), or it isn't (in which case YOU can't say it is when you're trying to evangelise it).

      One or the other. Which will it be?

    204. Re:Beautiful by Urchlay · · Score: 1
      > No, I don't want a .deb from you. I want a autopackage or a lsb-rpm or something else that will work on any distro.

      You aren't likely to get such a thing unless you want all the binaries to be statically linked. *Shrug*, maybe that's exactly what you want, but there are good reasons for using dynamically linked libraries.

      Even then, do you want your auto-super-RPM package format to include binaries for all architectures Linux has ever been ported to? Lots of people run Linux on powerPC (both 32- and 64-bit), or native AMD64, or ARM, or even Sparc (32- and 64-). How are we supposed to have the time/energy/desire to build binaries for all these arches, much less hardware to test them on?

      Even if there were such a thing as an uber-package that would Just Work on all Linux distros (ignoring the x86 vs. powerPC vs. ARM, etc. issue), I as a developer wouldn't be releasing them. Why? Because I wouldn't be targetting Linux only: I'd release platform-independent source code which would compile on (at a bare minimum) Linux, Free/Net/OpenBSD, MacOS X, Solaris, Win32 (if possible and applicable), and hopefully BeOS. My earlier statement about not having the time/interest to support all the Linux distros applies even more so when multiplied by all the variants & versions of all these OSes, and again by all the achitectures they run on.

      What I'm talking about wouldn't apply to people working on commercial or otherwise binary-only software, of course. But you hardly ever see a closed-source package that works on multiple platforms anyway (e.g. Nero, DvdShrink, WinRAR are for Windows only, and damn near all binary-only Linux software is for x86 only).

      I realize this is a much bigger can of worms than you wanted to open, but it's a partial answer to your implied question of "Why can't there just be One True Package Format that I can install and have it Just Work?"

      Believe me, I'd love to have the same thing, but there are good technical reasons why it can't be as simple as we'd like.

      Actually there are social/political reasons, too: since Linux isn't a single OS controlled by a single vendor, we'd have to make every Linux distributor agree on How Things Should Be Done. That's pretty unlikely, don't you think?

    205. Re:Beautiful by mpe · · Score: 1

      Which is a huge flaw. Software installation should be automatic.

      Automatic software installation equates to a "malware" problem. Software installation really should be an uncommon task, especially for end users.

    206. Re:Beautiful by blane.bramble · · Score: 1

      They are assuming that if you are in the (generally) 50+ age group then you didn't grow up with computers and have therefore spent your life learning how to do more important and interesting things than deal with dynamic and static libraries.

    207. Re:Beautiful by grumbel · · Score: 1

      ### Why do you think that it's a sensible idea for users to be installing software in the first place?

      Do you think its a better idea to run as root for every little piece of software you want to try out? What makes you think that its actually not a sensible idea to install software as user? Its a perfectly fine thing todo and its the way Windows and MacOS work for decades. You won't stop viruses from spreading by forcing users to either 'sudo' or use untrusted sources instead of official Debian repositories.

      ### In which case you can simply build the software to work in that environment.

      But weren't package managers invented to avoid that in the first place?

    208. Re:Beautiful by rbanffy · · Score: 1

      Simple. When you install stuff yourself, you are on your own. No package manager can ever protect you from yourself.

      Nor should it try.

      I use Debian mainly because of APT, but I manage my Zope and its products myself. I also keep an eye on PostgreSQL, as every upgrade disrupts things a little.

      If, however, you download a package from sf.net that has dependencies _inside_ the package-set of your specific distro, there should be no problem.

    209. Re:Beautiful by g0_p · · Score: 1

      Doesn't yum do this? I am not certain, but I think dependencies for a package can be satisfied from packages hosted on another repository using yum. Isn't this what you are alluding to? Though I dont think there is a strict format around identifying packages other than the naming scheme and the rpm headers.

      I havent gone dependency hunting in a long time ever since I have been using yum. I do occassionally add more repositories to my yum.repos.d if I find something interesting but thats it.

      More information about yum http://linux.duke.edu/projects/yum/howitworks.ptml

    210. Re:Beautiful by Burz · · Score: 1
      What do you do with something like OpenOffice.Org, then, which requires about 10,000 dependencies? Should each GTK+ application come with its own statically linked copy of GTK to be carried in memory separately for each app?

      What do you do? Find an "OS" that actually is an OS, with a clearly-definied set of available APIs that serve more needs than just kernel functions like "open an IO port, run this program".

      When I install the OS X port of OOo called NeoOffice, does it check thousands of dependencies?

      No. It checks that I have Mac OS X 10.2 or higher, and maybe the version of Java and thats it. Yes a handful of otherwise sharable libraries are included with the program. So what? Some free libraries are better copied between projects than they are acting as an invisible system-wide reource; That's one of the reasons Apps on OS X supply user-selectable Services.

      GNU/Linux will not get better in this regard until LSB creates a desktop-branch of their specification. That would address one of the two great Linux bugaboos: 1) app dependencies, 2) drivers that consumers can't install.

      Beyond that... fix the cut-and-paste inconsistencies that still exist, support power management better, and you have the perfect desktop OS.

    211. Re:Beautiful by grumbel · · Score: 1

      ### You definately should not be able to install it system-wide no matter what package management system you have.

      Of course you should not, unless you are root, thats now something bloody obvious that I didn't assume that it would be needed to mentioned specially. What I was talking about is installing stuff in the users home directory.

      ### If you want a cutting edge version of gimp, download and compile it in your home directory.

      Why should the user be forced to compile and track dependency manually when the Debian repository provides a perfectly working version of it? Why can't apt-get allow him to install it into his home? Weren't package managers invented to avoid compiling from source in the first place?

      ### Sure debian stable is a little behind but remember, it's *stable* meaning that buggy cutting edge program won't be there.

      You don't seem to have used Debian for too long, 'stable' refers to the package dependencies *not* to the software. There is plenty of software in stable that is far more 'bleeding edge' than unstable, simply because 'stable' was frozen at a time where the software just has jumped to a new major version and never got any of the bug fixes that the software in unstable got. After all only security fixes get down to stable, rest stays in testing and unstable. Anyway, thats a different issue.

      ### but I don't expect the author of a program to package their program up for each distro.

      Neither do I, what I want is a way to package programms independly of the distro. Which either means source tar.gz + some computer readable metadata (as oposed to human readable INSTALL files like its handled at the moment) or autopackage/lsb-rpm style binaries.

    212. Re:Beautiful by Brandybuck · · Score: 1

      It works moderately well, if you only use it for applications and those are statically linked, but nothing else.

      Not true. You can put everything an application needs in the .app, including dynamic libraries. There are of course drawbacks, as you've pointed out, such as redundancies and huge application downloads. But everything that would be installed under /usr/local in Unix can be put into a .app directory instead. Imagine a Visual Basic application that actually came WITH the runtime...

      --
      Don't blame me, I didn't vote for either of them!
    213. Re:Beautiful by grumbel · · Score: 1

      ### How are we supposed to have the time/energy/desire to build binaries for all these arches, much less hardware to test them on?

      For the beginning standard source format would already help a lot, ie. one with computer readable metainformation on how to build, not just human readable INSTALL files. The rest could then be simply autobuilded.

      ### but there are good technical reasons why it can't be as simple as we'd like.

      I wouldn't call it 'good technical reasons', most of it is simply historic and lack of standardization. Nothing would really stop a standard package format to work out on a large scale if people simply tried a little bit harder.

    214. Re:Beautiful by imroy · · Score: 1
      First of you can't install a application as a user, now how stupid is that?

      Right. Lets try some substitution shall we...

      First of you can't install a VIRUS as a user, now how stupid is that?

      See how stupid your complaint is? If you let users install system software then we go back to the days of rampant viruses and worms... which Windows still hasn't escaped.

      You still want to install software? Well it's your machine isn't it? Login to root and install it, FFS! Otherwise ask the admin.

      Secondly Debian packages work great, but only for stuff that is in Debian...

      Bzzt, wrong! If you knew anything about Debian (which you clearly don't) then you'd know about adding APT respositories to your sources.list file. Do a google search, there's lots of third-party repositories out there for Debian packages. Fedora even uses a variant called APT-RPM that uses the same mechanism. It's very simple, all you really need is some web or FTP space for some files.

      What good is it to release a software today and having to wait three or more years till it finds it way into Debian?

      *sigh* the whole three-year thing... Look, I've been running the unstable "sid" branch for many years now. My systems are always up to date and only occasionally have problems, although the switch to GlibC 2.1 still sticks in my mind. Most packages are updated within a week, although it can take much longer for packages that upset a lot of other packages. Debian takes very seriously the stability of the system, even the unstable branch. For people who want new0ish software but don't like the idea of running something "unstable" there's the testing branch. Packages are delayed from unstable until they haven't had a bug report for (IIRC) two weeks.

      Understand this: the "stable" branch of Debian really is stable. It's for people who are serious about having a reliable system that runs like clockwork.

    215. Re:Beautiful by Knuckles · · Score: 1

      You don't want automatic updates for security issues? Nice for you, I however do, and the fact that I don't get them on Mac or Win (except for system stuff) already prevents me from using these systems

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    216. Re:Beautiful by Dcnjoe60 · · Score: 1

      Regarding Synaptic, I suggested it because I thought that part of your complaint was that a user shouldn't have to drop to the CLI to install it, and then you got those error messages.

      In regards to Debian not having all software in their repository, that is true, there are only something like 15,000 packages in it. However, it is also true that Windows and OS X don't have it either, you have to get it from a vendor, most likely.

      As for stable software being released by its creator but not available. I agree there is usually a lag, but even debian repositories usually have it in the testing or unstable branches in short order (assuming it is something that is even remotely popular). This is no different, and actually better than Windows and OS X. Steve Jobs said they've been running OS X on x86 for five years. It will be another before it's available to the public. Even debian itself releases quicker than that!

      I do agree that when a new game is released on Windows you don't normally need to upgrade your OS, on the otherhand, you usually do need to upgrade your video card and ram, but that is a different story. The real problem is that most people wouldn't mind having to upgrade their linux distro if only the games were released for it!

      Regarding centrally packaged software, well, yes, it is true that the distros expect the software to be centrally packaged and distributed, but then Apple expect it to be their way and Microsoft their way (for their respective OSs). However, is this really a distro problem or a programmer issue. There is nothing stopping me from installing firefox or thunderbird in my home directory. It doesn't need to be packaged in a .deb or .rpm. But, most programmers don't package their software to be able to install it that way. Part of the problem may be that linux by default is meant to be multi-user. And regardless that drive capacities have increased by leaps and bounds, I wouldn't want to install Office four times, so my wife and kids could use it, too. At least in linux I can choose to install from source, bzip, rpm or deb (an no, I don't use gentoo), so that if something is available in only one format, I can still install it.

      Finally, as for the sudo issue, I really answered that above, it's not a distro problem that won't let you install something to your home directory. Firefox and thunderbird are examples of that. You don't need any special access to install them in home and they work fine. It's really up to the developer to determine how they want it installed. This again is no different than OS X and Windows, it's just that the developer's choices are more limited with those OSs.

      I do agree that it is better to be able to test a package first in an isolated account then installing it system wide. However, if you are getting the package from an official repository, then that testing is supposed to already have occurred. If, on the other hand, you are compiling it yourself, then you can tell it to install wherever you want.

      The fact, though, that you are talking about installing and testing and compiling, etc. Shows that you are using your computer somewhat differently than the target market for OS X and Windows (now the beauty of OS X, is that you really can have the best of both worlds, by doing it Apple's way and dropping into BSD and doing it *Nix way).

      Finally, along that same comment about installing in your home directory. Surely, you would want somekind of verification of what you are installing, otherwise a malicious web page could install something there, too. So, if you are going to need somekind of "Are you sure" message, is that really any different than having to use sudo?

      Anyway, I'm not arguing that the debian way (or anyother Linux way) is the best way or even better than the OS X way(you noticed, though I left Windows out of that disclaimer). I think they have different approaches because they try to cater to different users. The biggest difference, I think is that OS X from the start was a desktop operating system. Linux really focussed more on the server. It's packaging systems reflect that, although as desktop use has improved so has the package installation process.

    217. Re:Beautiful by andrew71 · · Score: 1


      In other words, I'd say we need dynamic linking code to really be dynamic!

      The OS component responsible for dynamic linking may also act a little bit as a package manager, managing different multi-versioned libraries, maybe across networks, securely (please remember, we walked into the 21st century a while ago).

      Programmers may distribute "fat binary" versions, with all the needed libraries, or "light binary" versions, only when they are sure the libraries are already on the target systems, a lot like you do with runtimes since the early days...

      The system should know exactly what libraries an application needs (along with version ranges). Then you would have a tool to "strip" an installed app, stripping binary libraries from the local copy and merging the missing libraries (if any) into the main system repository. Maybe the same tool would also work the way back, copying (all? most?) required libraries locally (for distribution purposes, to allow running from removable media, whatever).

      A little bit too far fetched?

      --
      13-4=54/6
    218. Re:Beautiful by zootm · · Score: 1

      Why couldn't the package format include update information?

      And most Mac/Windows software susceptible to security problems automatically updates itself via the web. It's not a single, unified system, but they do do it.

    219. Re:Beautiful by Burz · · Score: 1

      I disagree.

      Debian plays its role as a conservative force among Linux distributions. OK this last cycle was 12 months too long, but its influence is still of great value.

      On the other end of the scale, we have Fedora and Gentoo. As someone who had supported "Red Hat compatible" 3rd-party apps let me say that RH/Fedora present the desktop user with plenty of adventure in keeping their apps running; whereas the same apps will keep running on both Debian stable and testing over the years.

      I haven't met a single app/version which ended up breaking on a RH upgrade, that didn't keep running years longer on even the more bleeding-edge Debian derrivatives like Xandros, Linspire and Knoppix. This includes Rational Rose 7 and VMware 3.2.

    220. Re:Beautiful by antiMStroll · · Score: 1
      The topic at hand is the Linux desktop's readiness to compete with OSX. I presumed that your post (often a mistake on Slashdot for sure), being the first moderated one, was on topic. You focused criticism on package management, incorrectly ascribing to all of them a fault commonly leveled at one: RPM, and associations (to which I can't disagree), followed by suggestions for a system in which programs keep all the files necessary for them to run in individual directories save for a single, common library provided by the OS. I responded that by this standard Windows XP isn't ready either. It seems to do quite well against OSX, BTW. (Is DLL Hell even a valid criticism of Windows anymore? The only time I see it is updating ported GTK apps.)

      "Thirdly, *what* Windows XP package manager? "

      Note my quotes around 'package management'. In the context of Linux desktop readiness, any reasonable person should have taken that to mean the OS's mechanism for installing and removing software, the purpose of package managers. The abysmal state of Slashdot moderation notwithstanding.

    221. Re:Beautiful by pmjordan · · Score: 1

      Too far fetched? Probably. There are a few slightly different ways of loading libraries. You have languages that don't compile to native code. Either way, for automatic detection, you'd really have to wait until runtime, unless the binary format had a detailed list of dependencies. Why bloat up the binaries if you can let the packaging system take care of this stuff?

      I'm not really sure what you're trying to say with your post. Are you trying to imply that that's what I'm trying to say? Either way, it's not. I'm only suggesting going a step further than specifying what dependencies a package has, and also specify where to find those dependencies, be it in a big repository, or on a random website.

      ~phil

    222. Re:Beautiful by Rick+the+Red · · Score: 1
      * This is an article about Linux. Your argument
      about packages being out-dated is almost
      completely limited to Debian.
      No, this is an article about Symphony OS, which is based on Debian.
      --
      If all this should have a reason, we would be the last to know.
    223. Re:Beautiful by grumbel · · Score: 1

      ### If you let users install system software then we go back to the days of rampant viruses and worms...

      Users already can install and run viruses and worms as much as they like on Linux. Lack of install support for users in apt-get isn't a security feature, since there are numerous other ways to install software. I would go even as far as saying that lack of user install in apt-get is a huge security risk in the long run, since it forces user to look for random other sources for binaries instead of using the trusted Debian repository.

      ### you'd know about adding APT respositories to your sources.list file

      If you would have acutally used Debian with unofficial debs you would now that Debians dependency tree is pretty fragile, if install not-so-well-build unofficial debs you can have lots of fun cleanup up later on. Yes, it sometimes works well, but often does not.

      ### My systems are always up to date and only occasionally have problems

      If you think running without security updates is a good thing than that is your problem.

      ### For people who want new0ish software but don't like the idea of running something "unstable" there's the testing branch.

      People want *some* new software (say a new Gimp or KDE or whatever they need most for they daily work), they don't want to have a completly bleeding edge that doesn't even provide security updates.

    224. Re:Beautiful by lowmagnet · · Score: 1

      That is true... I can only speak for Apple's plaform in this, but they use Disk Images to transport files. The browser usually mounts them for you, so it seems transparent to the user. The only real install step left to do is moving the pkg to the applications folder. I made an automator action to do so. :)

      --
      Heute die Welt, morgen das Sonnensystem!
    225. Re:Beautiful by Urchlay · · Score: 1
      > For the beginning standard source format would already help a lot, ie. one with computer readable metainformation on how to build, not just human readable INSTALL files.

      Well, there's GNU autoconf (./configure && make && make install), but not everything uses it, and not every autoconf-using package uses the same options..

      And you just *can't* force all developers to use the same build system. Some of us like autoconf (some hate it), some like a plain old Makefile, some like multiple Makefiles, some people (odd as it may seem) even like xmkmf and IMakefiles. This is a matter of personal preference, particularly for those of us writing free software because we enjoy it (in a corporate environment, if you're the boss, you can enforce such standards, of course).

      Also, there can be build problems that couldn't possibly be foreseen: I developed my program on (say) Linux with glibc 2.3.3 and gcc 3.3.2. You try to compile it on MacOS 10.3 with gcc 3.4.0. It turns out that the semantics of some function call I used are slightly different on MacOS's glibc, or maybe they require a different header file to be #include'd, or maybe I used a C construct that's no longer legal in the new version of gcc (granted, I make a serious effort not to do this, but nobody's perfect).

      How the heck am I supposed to know my program won't work on MacOS if I can't afford (or don't want) a nice Mac to test it on?

      ...And don't try to advocate giving up C and C++ in favor of (Java|Python|Perl|Ruby|whatever). Not everything can be written in a scripting (or VM-based) language, and not everyone knows or wants to learn a new language every couple of years. Not to mention, it's perfectly possible to write unportable code in any of the above languages. Even people who prefer such higher-level languages don't agree on which one is best.

      > I wouldn't call it 'good technical reasons', most of it is simply historic and lack of standardization.

      Any time anyone tries to propose a "one size fits all" solution, I just have to shake my head. Not everyone agrees on what's the best way to do something. Not everybody *should*, otherwise no progress is made.

      If you want a UNIX-like OS that has a formal set of standards and does a good job adhering to them, you might look outside the Linux world. MacOS X and Solaris are both pretty good in the "it just works" department, if that's your goal. The Linux community, for good or ill, has gotten as fragmented as the original UNIX community back in the 80s (before my time, but I read a lot).

      Sorry, that turned out to be more of a rant than I intended. Please don't take it personally (I don't even know you).

    226. Re:Beautiful by Blakey+Rat · · Score: 1

      Good post, man. I agree with you 100% entirely. The best way to solve problems is to step back from them and take a look at the big picture.

    227. Re:Beautiful by poopdeville · · Score: 1

      I suggest you re-read the GP's post. Hell, just the part you quoted is sufficient:

      "Just because OS X is 'like Unix' doesn't mean that's all it is." (Emphasis mine)

      See, GP is telling you that OS X is a unix-alike with a whole lot more. If you're installing software that hooks into the extensions, installation goes very smoothly. In particular, one can install software into one's home directory. If one is installing software that doesn't hook into the extensions, one would best be served by using a package manager, like Fink (which is a goddamned port of the apt suite and an OS X specific apt repository). Note that this is the solution to installing software in other Unix-alikes as well.

      Now, I suggest you practice reading some more, as your reading comprehension is scoring very low marks today.

      --
      After all, I am strangely colored.
    228. Re:Beautiful by AKAImBatman · · Score: 1

      The topic at hand is the Linux desktop's readiness to compete with OSX.

      Actually, the topic at hand is SymphonyOS and its plans for making Linux the ultimate Desktop OS. Part of those plans are Yet Another Package Manager(TM).

      I presumed that your post (often a mistake on Slashdot for sure), being the first moderated one, was on topic.

      It is.

      You focused criticism on package management, incorrectly ascribing to all of them a fault commonly leveled at one: RPM, and associations (to which I can't disagree)

      RPM is definitely bad, but even the best ones (e.g. FreeBSD Ports) are just not userfriendly and are quite breakable.

      I responded that by this standard Windows XP isn't ready either.

      Here's where you fall flat. I never suggested that anything was "ready" or "not ready". You inferred that, and thus placed words in my mouth. My original intent was to ask why such a seemingly nice system targetted at desktop users is intent on using Yet Another(TM) packaging system when it has already been proven that such beasts are not friendly to end users.

      And yes, XP's installer management techniques are quite poor in comparison to OS X. However, it does work reasonably well for Windows and tends to create fewer problems than many packaging systems.

      The abysmal state of Slashdot moderation notwithstanding.

      Just a thought, but if you wanted to not get moderated as a troll, it might help if you didn't have "troll" in your name. Walks like a duck and all...

    229. Re:Beautiful by Blakey+Rat · · Score: 1

      I know a couple people have already posted on this, but I have no clue whatsoever what he did to a Mac Mini (a computer that couldn't possibly be more than, what, 6 months old?) to require reformatting *twice*! I can't imagine what he did to it to require reformatting once, for that matter... OS X is very hard to screw up.

    230. Re:Beautiful by antiMStroll · · Score: 1
      "Just a thought, but if you wanted to not get moderated as a troll, it might help if you didn't have "troll" in your name. Walks like a duck and all..."

      But you'ld expect it to work in my favour when I compliment MS product! ;)

    231. Re:Beautiful by Blakey+Rat · · Score: 1

      Well, if nobody else in the Linux world, Linspire seems to be pretty dedicated to get Linux out to average Joe users.

    232. Re:Beautiful by resiak · · Score: 1

      You haven't tried to get Java running on Ubuntu, have you?

      No, mainly because I use Debian.

      I have, however, got Java running _perfectly_ on Debian, and am currently playing Puzzle Pirates. I do feel unclean for using it, though.

      21:36 <resiak> install java
      21:36 <dpkg> First, read <java licensing>. Still here? If you're in sarge or sid, ask me about <java-package>. If you're in woody, grab java-package manually from http://packages.debian.org/java-package and then ask me about <java-package> for instructions on how to use it. Also, ask me about <java-package howto>
      21:36 <resiak> java-package 21:36 <dpkg> somebody said java-package was the new name for mpkg-j2se... err, I mean j2se-package... DAMN IT, CAN'T THEY PICK A NAME?! Anyway, it lets you build a .deb file from Sun's non-free upstream Java distributions. See "man make-jpkg". Cf. "make-kpkg" (from kernel-package).only in sarge and sid currently, but it's a -all package, so it's safe to use it in woody. This packages lives in 'contrib', so make sure you have that in your sources.list.
      21:38 <resiak> java-package howto
      21:38 <dpkg> http://www.debian-administration.org/?article=142

      Go speak to dpkg on freenode. You'll need to /j #debian.

    233. Re:Beautiful by grumbel · · Score: 1

      ### And you just *can't* force all developers to use the same build system.

      Certainly true, but if something like freedesktop.org would publish a recommendation I sure at least quite a few would follow. At the moment I couldn't follow any standard way even if I want to, because there simply isn't any.

      ### And you just *can't* force all developers to use the same build system.

      Of course you can't force them to use a different build system, thats why I said 'metainformation', by that I mean a common way to document things like how to install a package, how to compile it, how to install it into a different prefix, destdir, which libraries it requires, etc. things you can do with basically every build system somehow, they are just named often quite different.

      The source packages that you find for Debian or Redhat do basically exactly that, they wrap the underlying build system into something that is usable for an automatic build of the binary package. It would be nice if that part would be somehow become standard across distros so that I could just say 'build --prefix=/foo/', instead have manuallly trying to figure out if its 'make -f Makefile.linux PREFIX=/foo' or './configure --prefix=foo' or something completly different.

      ### Any time anyone tries to propose a "one size fits all" solution, I just have to shake my head. Not everyone agrees on what's the best way to do something. Not everybody *should*, otherwise no progress is made.

      Certainly true, but the different build systems aren't really that different in *what* they do, they are only different in *how* they do it. And since the 'what' part (install, build, cleanup) is basically offered by all of them, some 'metainformation' could be used to allow to automate this process.

      Starting from such 'metainformation'-enhanched source tarballs it would then be possible to automatically build binary packages for lots of architectures and such.

    234. Re:Beautiful by sneakers563 · · Score: 1
      And don't even get me started about trying to make xine play a dvd...

      1) Yeah, insert the DVD and click the "DVD" button on the control panel; that's real freaking hard.

      2) Who says we should all be using OS's designed for imbeciles? I suppose it'd be nice for my parents if the computer would just start running the movie, but why should I have to be subjected to that kind of babysitting? I don't want my computer to make assumptions for me, and I'll bet that most of the people using Linux don't either. I'm glad OSX is out there for people like your parents, but that doesn't mean it's what everyone wants/needs.

    235. Re:Beautiful by Blakey+Rat · · Score: 1

      ... or simply make GTK 2.6 a superset of 2.4.

    236. Re:Beautiful by steve_l · · Score: 1

      First, I want to observe that 'configuration management' is still an academic research. nobody gets it right. But you are making some valid points.

      IMO one mistake that linux distros do is have a single central place for all binaries, all installed by root. Whereas having a per-app configuration makes more sense. If my app wants version 4.3 of a library, it can live in my user space while another app has version 4.2. This works. right up until a security alert forces upgrades to 4.2.1 and 4.3.1 and you have to locate every single instance of a library and pacth. Across 500 machines on a site.

      The Maven2 stuff from Apache is leading the way for Java JAR versioning and retrieval; other apps are using it too. There each user has their own local cache of JARs, all stored in different dirs for project/artifact/version. Each artifact is md5 signed and includes a descriptor of what other files it depends on.

      I am working with this, and it is, well, interesting. There are some quirks, especially with transitive dependency inference. Whenever a library declares the files it depends on, those have to be treated as hints, hints you can override.

      The other thing that interests me is vmware, who are now hosting prebuilt system images. Want a copy of suse linux with mysql configured. Download it. Want a debian distro with kde3.4? download it. Each OS is a self contained thing you pull down.

      there are some interesting security issues there, I am sure..

    237. Re:Beautiful by mmkkbb · · Score: 1

      Yup, sounds about as exciting.

      This is intuitive how, exactly?

      --
      -mkb
    238. Re:Beautiful by kollivier · · Score: 1
      But from a standpoint of supporting a diverse ecology of software producers and lots of competition, the cathedral isn't the most desirable structure. It seems that when one pays a draconian cost (central control) to solve smaller problems (package dependencies, file locations), it might not be the best deal in the end. I'm still endeavoring to provide a better solution to this problem.

      Why not a two-pronged approach? Some people and businesses want to take control of their OS, some don't, or, more accurately, they can't afford to. After all, when you talk about the better deal, is there really one 'better deal' for everyone?

      It seems to me that the better deal for the Enterprise is control and customizability. Linux has, IMHO, got this covered pretty well. People can build their own distro off of Debian, LFS, or other distros, quite easily and take control over what is installed and what the users can do with it. This is good also for kiosks, PDAs/embedded devices, and other devices that provide a controlled experience to the end user. Not to mention hobbyists. :-)

      But I don't feel this is the better deal for the home user, or the small to medium-sized business. The better deal for them is something that minimizes complexity and maintenance, and maximizes productivity. They want things to work "out of the box" and would even do things like upgrade their machine rather than hire a consultant to tweak the distro to their needs. Workers in many of these environments take some degree of responsibility over the maintenance of their computer, so it has to be very simple to understand and maintain for non-tech users. I don't think there's any Linux that actively targets these users yet. It's obvious lots of people want Linux to target this market though.

      Well, those are just my thoughts on the matter, but there's lots of organizations out there like this; in fact, there are probably tons. (I work for one.) Get Linux into this market and IMHO it'll really take off, but so far I haven't seen people doing to Linux what needs to be done in order for us (and organizations like us) to adopt it. ;-/

    239. Re:Beautiful by StormReaver · · Score: 1

      I have been developing an application distribution system, which I call Linstall, that addresses all issues except where to place files (which is deferred to the underlying packaging system itself). My implementation assumes RPM, but distribution makers can easily modify it to use whatever packaging system they desire (deb, tar, etc).

      The way it works is basically this:

      1) The developer tells the packaging component which program is to be packaged.

      2) The packaging component queries the application for all its dynamic dependencies, and walks the packager through the process of locating all the packages that were used in the development of the program.

      3) The packaging component creates an ISO image just large enough to contain the application and its dependencies, places everything the program needs into the ISO image, then compresses it.

      4) The compressed ISO image is then appended to an extractor stub program, and the resulting file is ready for the user to download.

      5) The end-user downloads the file, makes it executable, and runs it.

      6) The program extracts the ISO image, decompresses it, mounts it, then passes the correct command line to the packaging system to install the application.

      7) The installer unmounts the ISO image, and exits.

      Since all dependencies that are not part of the operating system are present in the distributed file, there should be no dependency problems. Since package managers are smart enough to not reinstall packages that are already present, there should be no Windows-like DLL hell.

      Your natural first reaction might be that this could dramatically increase the size of the file the end user has to download, and in some cases that is true. In most cases, however, this will not be the case since the user would have to download at least that much during the process of tracking down all the dependencies anyway.

      Given the option of downloading a larger package, but knowing that the application will install reliably, versus downloading a smaller file initially but having to spend time tracking down dependencies, most users would choose the former.

    240. Re:Beautiful by iwan-nl · · Score: 1

      The SymphonyOS site is back up, so I've been able to check it out. SymphonyOS uses synaptic. I'm definitly going to try it.

      --
      I'm trying to improve my English. Please correct me on any spelling/grammar errors in this post.
    241. Re:Beautiful by jbolden · · Score: 1

      Which both BTW have Linux like package management systems (fink uses debian's apt-get and DarwinPorts is a first cousin of Gentoo's portage). In other words as soon as you have package problems as complex as Linux's you end up with a packagement management solution like Linux's.

    242. Re:Beautiful by ThisIsFred · · Score: 1
      Ok, for one, that's just putting words in my mouth. I never said that any package systems "were not ready for the desktop". I said that package systems create a dependency hell in complex systems that's just as bad as DLL Hell.
      Well, I'm certainly not going to put words into your mouth, but I will argue against this point. I've never had a situation similar to DLL Hell on my Linux systems. To me, DLL Hell is when two applications that have the ability to restore libraries stored in the system areas of a Windows system continually restore their prefered version. The result is that the user has little control over the situation, other than to not run one of the programs. One or both of the programs get broken.

      The closest I've got to that level of frustration in the GNU/Linux world is when either a) the developer fails to mention all the dependencies or doesn't include the rare ones (like I can track down some library out of CVS from a host that was used by only 3 other developers and was shut down 6 months prior). Or, b) the application uses a deprecated function, and I need to get an updated version of the program. I don't know what you'd define as a complex system, but I very rarely have these problems on my desktops or servers.
      --
      Fred

      "A fool and his freedom are soon parted"
      -RMS
    243. Re:Beautiful by iCEBaLM · · Score: 1

      Yes, as demonstrated by the glacial release cycle of Ubuntu, versus the incredibly rapid turnover of Windows and OS X. Or rather, not.

      As of my last check, Ubuntu still has a 3 release out of date ATI driver, arguably the second most popular video card used, a driver that has significant performance problems. Installing your own from ATIs RPM breaks a couple packages in ubuntu which require the use of dpkg --force* commands, which nobody should have to use. They are not doing a very good job of keeping all of their packages up to date. This is part of the problem, the distro devs don't have enough time to keep all the packages up to date because they're packaging everything including the kitchen sink so either packages get left behind, the releases become slow, or both.

      I've never actually seen this happen myself, but I'll take your word for it :). Anyone have any horror stories to share? Does it happen with actual packages, or only if you install from source?

      Say you want to install a different (read: newer, different compile time options, etc) version of a library on your system. Sure, you can spend days figuring out how to package it for your distribs package format or you can install it from source in minutes. Since you installed it from source the package system doesn't know about it, you try to install something from a package that depends on this source compiled library and what happens? The system says "that library isn't installed, hey, I'll install it for you" and then proceeds to overwrite the one you just installed.

      Not a very good system.

    244. Re:Beautiful by WatertonMan · · Score: 1

      They both use Linux package management because they are ports of Linux software for those who need them. (BTW - many packages also come with Mac installers outside of Fink or Darwinports)

      The point is though that most Mac software doesn't. And people complaining about bloatware in a day when we regularly download multimegabyte film trailers are living in an other world. I know many Linux users are using 10 year old technology, never pay for software, and likely live in their parent's basement. But many run newer software and recognize that for $100 they can get a 160 - 200 GB hard drive.

    245. Re:Beautiful by Anonymous Coward · · Score: 0

      Solaris has a good solution for this:

      1) The normal case is the new version is upward compatible, in which case you ship a single copy of the library that everyone points to (e.g. libc.so.1).

      2) If there's an incompatible change then you ship both versions, and apps link against the one they need (automatically), e.g.: libresolv.so.1 and libresolv.so.2.

      Note that you don't rev the version number for every single compatible change though, so the actual cases of multiple libraries are very rare.

    246. Re:Beautiful by WatertonMan · · Score: 1

      The flaw in OSX' approach is when applications do put files in /Library or ~/Library and don't provide a simple way to remove them. Many don't offer good uninstallers and even most uninstallers leave ~/Library/Preferences alone. This can cause trouble. There was a big thread about it over on Ars last week before the Intel announcement spread fear and excitement everywhere.

    247. Re:Beautiful by NMerriam · · Score: 1

      That's not what apt-get is supposed to do.

      apt-get isn't supposed to be used to install software? That's news to me.

      The entire reason all these package managers are being discussed is because they were being touted as so incredibly powerful and much more useful than the pitiful toy .app or .pkg installation methods used on the Mac. For the sysadmin, that may be true, but for the desktop user (which is what the whole freaking Mac OS on x86 thread is about!) it's a joke that nobody on the Linux side of things even seems capable of seeing.

      --
      Recursive: Adj. See Recursive.
    248. Re:Beautiful by Terrasque · · Score: 1

      Sounds a bit like zero install, actually. It's basically a caching distributed filesystem thingy.

      So for example if you wanted to run foo.com's program foo2000, you just start the executable file (dont remember paths exactly, so take this with a grain of salt) /0install/foo.com/foo2000/current/foo2k - and 0install connects to foo.com, and downloads that file. That file loads other data files, and they get downloaded too, and cached locally.

      Now, lets say foo2000 depends on bar.org's libbar library to function. It just loads /0install/bar.org/libbar/2.3/libbar.so - and that gets downloaded and cached. (notice the link goes to a specific version of the library, so even if bar.org releases a new, api-breaking version, foo2000 will still use the old, working one..

      Next time you start foo2000 it starts up just as fast as a normal program would, since all is on your harddrive, and nothing needs to be downloaded.

      --
      It's The Golden Rule: "He who has the gold makes the rules."
    249. Re:Beautiful by Khazunga · · Score: 1
      What do you do with something like OpenOffice.Org, then, which requires about 10,000 dependencies?
      List them...
      Should each GTK+ application come with its own statically linked copy of GTK to be carried in memory separately for each app?
      Why should they?
      The natural response, of course, is to say: "no, that's an unnecessary reduction ad absurdum. We can just declare (by some means similar to the LSB) that all applications must use GTK+ 2.4."
      Why not install GTK+ 2.4 AND GTK+ 2.6?
      But then what do you do six months down the road when you start to see applications written for GTK+ 2.6? Now, either you have to convince every application developer to stick with 2.4 (unlikely); distribute those applications statically linked (ugly, see above); or explain to your users why they have to upgrade to the next version of your distribution to run what they want to run.
      Install both gtk+ 2.4 and gtk+ 2.6. Have applications load libgtk+2.4.so or libgtk+2.6.so, not libgtk+.so. Most already do so.
      --
      If at first you don't succeed, skydiving is not for you
    250. Re:Beautiful by iCEBaLM · · Score: 1

      Why do you think that it's a sensible idea for users to be installing software in the first place? Do you refuse to buy electrical appliances which have a "No user servicable parts" sticker on them...

      No, I'd much rather have to pay someone else to administer my home PC for me. What a dumb statement you made.

      The great thing about open source is that if you don't like they way something is done you can change it. Unlike proprietary software, where it's a case of "like it or lump it".

      I can see it right now: "Here you go grandma, here's some information on how to build your own linux distribution from scratch, have fun!"

      In which case you can simply build the software to work in that environment.

      Again, you seem to be missing the point of the thread, were you born stupid or do you have to work at it? We're talking about *ease* of installation, not how to make it actually harder.

    251. Re:Beautiful by iCEBaLM · · Score: 1

      You can add third-party repositories any time

      By default, my friend. By default. Adding repositories is not something the general computer using person is going to be able to do.

      and nothing prevents people from packaging up a .deb and offering it on their site.

      Except that there's so many damn package formats for linux nobody does it, they distribute in source or redhat rpm.

      The contrast is the fact that the central repository simply doesn't even exist for Windows or MacOS, so everyone's had to use a different distribution method.

      No, the distribution method is the same, you go to the vendors website, download the app (usually in a .dmg disk image) and drag it into the applications folder.

    252. Re:Beautiful by javaxman · · Score: 1
      And when it turns out that using OS X as though it were Unix is a quick and easy way to break it, they say no, stupid, of course you can't do that, it's not Unix, you need to port all that Unix software and make it play nicely with the Mac.

      I wasn't saying that at all. If you're going to use OS X as if it were a Unix, go ahead... but remember you're doing so. Meaning, if you're going to install a bunch of crap in /usr/local/lib, some day you might find that you'll have to manage those libraries. You won't be just dragging applications in the trash to uninstall them- you'll be doing the same admin work you'd need to do on any *nix system.

      I was pointing out that it's possible to take apps that would otherwise write libraries into /usr/local/lib/ and convert those libs to frameworks, and have framework versioning take care of some issues you run up against with shared libraries, but you'll still have to provide an uninstaller for a clean 'Mac' experience, so it's not often done. Usually code ends up statically linked because disk space is cheap and users like being able to grab an application and move it and have that be that.

      As has been pointed out, it's entirely possible for OS X to be *nix and another layer of stuff. The GP was complaining that they'd had /usr/local -related problems which resulted in instability. I frankly have a hard time swallowing that, but regardless, that'd be a problem with just about any poorly admin'd OS.

      And please don't paint me as a Mac zealot. I used CP/M, DOS, VMS, SunOS, NeXTStep, Solaris, Windows and then Linux, in that order, for years before ending up under OS X. Even then, I ended up here because my employer chose the system, not because of a choice I made. Before the switch to OS X, I'd completely written off Apple as a company. I hardly qualify as a Mac zealot. I'm just a guy who's day job includes hacking Objective-C.

      Stupid AC anyway. Get an account. What the hell's wrong with you... posting AC is just lame, why even bother? God I hate that I respond to ACs, it's not like they can check their accounts to see who's replied to them...

    253. Re:Beautiful by atezun · · Score: 1

      There is nothing "simple" about having a different package upgrade mechanism for every program.

      and there's nothing simple about going to System->Administration->Synaptic Package Manger
      then having to login to root
      then click mark all upgrades
      then click apply
      then in apply the following changes click apply again
      then the user watches packages with obscure names download to the computer
      then the user gets to watch a terminal window pop-up that the user have no idea what it's doing(I'm sure that's comforting to a new user)God help if there's a Yes No prompt during these installs.

      how is this any easier than most mmdern standalone applications that check for an update notify you take you exactly to the site where there's a big button that says download and all you have to do is click download it, extract it and drag it into your applications folder or if you want you can even leave it on the desktop.

      Further more if something goes wrong with this package manager that breaks the system how is the user going to know what the hell happened? At least this way they have a vague idea of what exactly they installed and since most apps on OS X don't require you to install them as root, very few of these can permanently damage the system. whereas if you're running synaptic and you experience a power-failure there can be some not so pretty results.

      And lastly when the user is tired of a program and no longer wants it on their computer all they have to do is drag it into their trash and all that's left is their preference files in case they want to reinstall the program at a later date.

      Package managers are great for seasoned admins, but they are dangerous in the hands of an unexperienced user.

    254. Re:Beautiful by RealAlaskan · · Score: 1
      Bruce, could the dependency problem be handled by distributing ``fat binaries'' which included all dependencies, but weren't yet linked? That is, distribute all the object code, but let the installer link it.

      That way, the installer could query the OS about each dependency, and provide it from it's own package if the OS didn't have it on tap. I suppose that you should also give the installer the option to tell the OS what it provides, so that the OS could offer it to other programs. Obviously, if your libraries are proprietary, your installer wouldn't make that offer!

      This system could work for proprietary packagers, too: they could write their own installers, load them with stupid safeguards and copy protections and generally make them as close to unusable as they wished. Libre programs would offer all the libraries on which they depended.

      Libre or proprietary, this system would give everyone the portability of static compilation and the RAM footprint of dynamic. To keep from cluttering your hard disk with multiple copies of far too many libraries (maybe the distribution core should require everything and provide nothing?), let the installer remove anything which the OS demonstrates it can provide. That is, if you get link errors using what the OS provides, use your own version. If you don't get link errors, remove your own version from the disk. When you're done installing, perhaps remove the linker and installation logic, and so on.

      I'd think that a system which wanted to use this wouldn't have to give the installer much. It would have to provide a clearly defined, specified-with-upwards-compatibility-in-mind way to query and inform about what it requires and provides. The installer would have to include a linker (For Libre software, it could simply include the necessary parts of GCC) and a bit of logic to run it. Maybe the OS should be able to recognise such an installer and initiate the queries? That might allow some sort of auto-installation.

    255. Re:Beautiful by eggnet · · Score: 1

      Photoshop and Office are actually good examples of that--that's why those systems come with their own toolkits, libraries, development environments, and scripting languages.

      They do this becuase they're cross-platform: win32 / osx

    256. Re:Beautiful by AKAImBatman · · Score: 1

      Well, I'm certainly not going to put words into your mouth, but I will argue against this point. I've never had a situation similar to DLL Hell on my Linux systems.

      That's probably because I'm not arguing DLL Hell, but package dependency hell. i.e. Linux packaging systems often break, refuse to install something, have a missing package, etc., etc., etc. I can't count how many times I wanted to install a piece of software on Linux and simply can't find all the packages. And trying to install via source is no end of pain. Go to compile one tarball and it asks for another tarball. So you go get that, which then asks for another tarball. Which then asks for a new version of a library that's unavailable in the package repository, and won't compile on your system, and ARRRRGGHHHH! JUST SOMEBODY FRIKIN' SHOOT ME NOW!!!

      Ahem. You get the idea.

    257. Re:Beautiful by jbolden · · Score: 1

      The package management systems are added after the fact. That is the fink project or the darwinports project have added the package management aspect. The pure porting guys don't need it. Best examples are darwinports stuff gets translated to fink they add fink specific package management.

      Its not a question of bloat its a question of complexity of dependency. Think about zope:
      zope -> apache, php, python -> mysql, php libraries, perl ...
      That's a pain without package management unless you want the app to need to run its own version of these servers (which is what mac databases often have to do).

    258. Re:Beautiful by _undan · · Score: 1

      This is why you EMPTY the trash when you want to get rid of an application, dummy.

    259. Re:Beautiful by AKAImBatman · · Score: 1

      I wish people would stop bringing this up. Windows programs don't delete their settings files (and often leave their registry entries and a few program files around too!), Linux programs don't delete their settings files, in fact you'd be hard pressed to find ANY system that does this. It's a non-argument to the extreme. Sure, Apple could add a hook that deletes these files on program deletion, but that's not desirable behavior in MANY circumstances.

    260. Re:Beautiful by MassacrE · · Score: 1

      The way that Microsoft is hoping to fix this in longhorn is that even an Administrator can only run user apps with 'normal' permissions unless they have configured policy for the app.

      One could imagine a 'sandbox' like java has for binaries - the process only has r/w access to stdin, stdout and stderr by default, with an additional "privilege manager" used to negotiate more. The privilege manager would have user-facing UI, such as "do you wish to allow this user to do x/y/z". Thus UI tasks such as choosing a file may pipe their requests through this manager interface as well.

    261. Re:Beautiful by OsirisX11 · · Score: 1

      To NYSE (Score:3, Informative)
      by mcguyver (589810) Alter Relationship on Tuesday June 07, @05:59PM (#12752759)
      1. If anything can go wrong, it will. (see Murphy's law)
      2. Systems in general work poorly or not at all.
      3. Complicated systems seldom exceed five percent efficiency.
      4. In complex systems, malfunction and even total non-function may not be detectable for long periods (if ever).
      5. A system can fail in an infinite number of ways.
      6. Systems tend to grow, and as they grow, they encroach.
      7. As systems grow in complexity, they tend to oppose their stated function.
      8. As systems grow in size, they tend to lose basic functions.
      9. The larger the system, the less the variety in the product.
      10. The larger the system, the narrower and more specialized the interfaces between individual elements.
      11. Control of a system is exercised by the element with the greatest variety of behavioral responses.
      12. Loose systems last longer and work better.
      13. Complex systems exhibit complex and unexpected behaviors.
      14. Colossal systems foster colossal errors.
      -KISS

    262. Re:Beautiful by scosol · · Score: 1

      Have you actually read about the "packaging system"?

      It's not "Yet Another" either... it's the appdir system that ROX invented-
      Hell it's not even a system-

      In fact, it functions almost exactly like you have described OSX!
      Copy a folder and you've installed the app!
      Delte the app? Delete the folder!
      Copy to a friend? Make a copy of the folder and give it to him!

      --
      I browse at +5 Flamebait- moderation for all or moderation for none.
    263. Re:Beautiful by AKAImBatman · · Score: 1

      Sorry to bust your bubble (actually I'm not, but more on that in a moment), but you've just described Internet enabled OS X DMG files. The primary difference is that you're thinking of using a read-only file system (ISO) whereas Macs have HFS+ or FFS in addition to ISO formats for their DMG files.

      Before you drop the project, though, listen carefully: I think this is a GREAT idea for a project. Linux currently has nothing like this despite having all the necessary components. I think you should pursue the idea to frutition. Perhaps even get a grant from LinuxFund if you need it. Good luck! :-)

    264. Re:Beautiful by Anonymous Coward · · Score: 0

      Ok, but what about 2.6.0 vs 2.6.1, 2.6.2, etc. Exactly the same package, completely compatible, except that subsequent versions are fixing defects in the earlier versions.

      How many people need to release updated packages to ensure all applications are using the fixed version of a library they should all be sharing?

    265. Re:Beautiful by AKAImBatman · · Score: 1

      If that's true, then.... ROCK! :-D

      However, they need to immediately stop calling it a packaging system (it's not) and start calling it "application bundles". The term "packaging system" is already heavily overloaded.

      I wonder why none of the Symphony developers came to correct us?

    266. Re:Beautiful by Anonymous Coward · · Score: 0

      *cough* double-click on recipt in /Library/Recipts *cough*

    267. Re:Beautiful by scosol · · Score: 1

      Here ya go:

      Package Management Custom Program using AppDirs
      File Manager Rox-Filer


      http://www.symphonyos.com/desktop.html

      --
      I browse at +5 Flamebait- moderation for all or moderation for none.
    268. Re:Beautiful by AKAImBatman · · Score: 1
      Umm... maybe I'm missing something, but the use of ROX Filer doesn't guarantee that they'll be distributing apps as bundles instead of Application Folders. The FAQ states the following:

      Q. Will it be possible to install applications that have to be compiled from source, or otherwise don't easily fit into a user-friendly packaging system?

      A. There will be several ways to install apps. 1. using the symphony package (the easiest way) 2. Installing via apt or directly from a deb file 3. Compiling form source (the graphical installer will attempt to do an ./configure make make install if it is asked to, otherwise it can be done from the console and the program can be added to application launchers and desktop menus manually.)


      They don't state anywhere that *.sym packages will be application folders. In any case, I'm downloading the Alpha so I'll know for certain very soon. :-)
    269. Re:Beautiful by scosol · · Score: 1

      I understand that- the key part is:

      "Package Management- Custom Program using AppDirs"

      Meaning- a nice interface to the AppDir paradigm, which works exactly as I said-
      You're installing it, you'll see :)

      More info on AppDir is here:
      http://rox.sourceforge.net/phpwiki/index.php/AppDi r

      --
      I browse at +5 Flamebait- moderation for all or moderation for none.
    270. Re:Beautiful by Knuckles · · Score: 1

      The first is a fair point I guess. So what you argue for is just a better UI to apt (or rather, less UI and more automagic stuff)?

      The second one, dunno. I think it's better to have the functionality tied into the system and taken care of automatically. Yeah, it would be nice if I could click a deb, it gets installed, and inserts its source in /etc/apt/sources.list.
      I'd rather not rely on having to hope that each app implements its own update system, without centralized, easily accessable info

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    271. Re:Beautiful by terjeber · · Score: 1

      because apps on the Mac OSX will run under Linux too (or even with minor modification).

      Mac apps will "never" run on Linux. Not unless someone ports the entire Mac framework to Linux, Cocoa all the other stuff. Since that is Apple proprietary, never to be opensourced, stuff, it is highly unlikely that it will ever happen.

      I'd love to see it though, threads on Linux are so much more efficient than on OSX.

    272. Re:Beautiful by terjeber · · Score: 1

      First of you can't install a application as a user, now how stupid is that?
      A very sensible one. In the vast majority of cases users are there to use a computer, not play at being sysadmins.

      That's an absurd statement and true for only company-owned computers. A huge number of people actually have PCs at home, and they just want to run their favorite software on that computer. The image editor, the video editor, the browser etc. Not allowing a user to install applications is absurd. Luckily the Debian package system has no such limitation.

    273. Re:Beautiful by terjeber · · Score: 1

      If you want a cutting edge version of gimp, download and compile it in your home directory

      Have all Linux users gone insane? Apparently. OK, slowly - the first part of your advice is good, if a user wants the latest version of an image editor, he should download it. The second part of the advice is absurd, you can't expect any users outside of a tiny fraction of one percent of all computer users to know what compiling is, let alone actually perform it.

      So maybe you should shut your mouth unless you know what you are talking about.

      He has some very valid points, and until those points are addressed, Linux will be a marginal or non-existant player in the desktop market. Hell, even now, Linux growth in the server market is slowing considerably. Unless usability issues with Linux are fixed, there is no reason Linux will survive as anything but an enthusiasts toy in the long run.

    274. Re:Beautiful by brettper · · Score: 1

      Sounds a lot like CoreData

    275. Re:Beautiful by DenDave · · Score: 1
      if you are getting rid of you G5s
      I am seriously considering sending the boxes to infinite loop with a "shove it Stevo" sticker... Have ditched my Apple stock, heck with what I made on that I can go surfing for a few months! I am sorry, PPC is the superior architecture and anyone who is blazed by the mghz should go look at something shiny
      --
      -if at first you don't succeed, stay the heck away from paragliding.
    276. Re:Beautiful by zootm · · Score: 1
      I'd rather not rely on having to hope that each app implements its own update system, without centralized, easily accessable info

      On one hand that's a good point, but on the other hand a centralised repository has a lot of problems, even with things like ethics (free/non-free software in particular). The automatic insertion into sources.list is basically all I'd like to see from a Linux package manager, actually -- just a package format that could insert itself quickly (and remove itself likewise, including references to update repositories) from a shell extension, for the file in question. This is basically what autopackage is trying to achieve, I believe, and it seems like it has (at least basically) the right idea in this regard.

      Another problem is something that just isn't an issue on Mac or Windows. If you want something to, for instance, be tied to a shell extension in a desktop environment, you have to do Gnome, KDE, etc., etc. We need more standardisation, even if it's only in a source "installer" format and some automated system to interpret the command relevant to the installed environment or environments.

      In a lot of ways, though, Linux/OSS isntallers have the potential to be better than what exist now. It's just a matter of looking critically at where we are, and deciding where to move.

    277. Re:Beautiful by einhverfr · · Score: 1

      This issue cannot be solved with a specification by committee.

      Right. This is not the job of a specification committee anyway. Look at the SQL standards, for example. But such a committee can go a long way to defining internals which can then be used to create a more friendly system.

      The reason OSX and XP can do thing that seem better than package managers is that they control the operation of the OS. They don't rely on a group of 1000 people to try to figure out how 10000 other people can use an installer/package manager. They just put whatever hooks they need into the filesystem or the kernal.

      Hmmm.... What filesystem hooks are present in XP? Mac maybe, but not XP.... That is what the registry is for ;-)...

      The problem with committee is that there is no personal accountability. For Apple, the people that develop the specs for software installation have personal accountability to complete their work and do it well. No non-company committee has this "fear."

      No company or committee has this fear. It only exists for individuals. These individuals may be paid by a company, pursuing advanced degrees in computer science, or simply releasing tools that they use in their small businesses. Yes, there is personal accountability, and most of the effective committees are formed by people who have strong incentives to get this to work.

      What I think is the most interesting is that we are not looking outside of what we already have. We have package managers; we have x number of groups that think that their package manager is better than the others; we have x number of groups that want better package managers. Why are we not stepping back from the idea of a package manager, and start with requirements and and current limitations? Then come up with a set of things we need in order to accomplish all of the requirements, ignoring current limitations. These "things" might have a wide ranging effect on all parts of the GNU/Linux system. From filesystem, kernel, to executable changes.

      THe current issue is that all suggestions here in the forum create as many problems as they solve. And I guarantee that if you run MacOS X as a server, you will be forced to deal with the fact that MacOS X does not so easily handle extremely modular applications such as Apache very well without a package manager. Same thing with other business systems. Of course many of us build such apps from source and rely on automake for help, but sometimes this can be frustrating too....

      --

      LedgerSMB: Open source Accounting/ERP
    278. Re:Beautiful by StormReaver · · Score: 1

      Thanks, Batman. I want to make it clear that I wasn't proposing the idea as an advancement in the state of the art of software distribution, but rather as a way of improving Linux application software distribution.

      As you said, Linux has, and has had for years, all the necessary components in place to make this happen. Unfortunately, no one else has taken the initiative to put them together.

    279. Re:Beautiful by Anonymous Coward · · Score: 0

      If a user is intelligent enough to install their own software in their home dir they can. Otherwise it's the admins descision. Sounds good to me.

    280. Re:Beautiful by ThisIsFred · · Score: 1

      I think that depends largely on how popular the depedencies are. For example, chances are that qt and gtk+ aren't going to be difficult to resolve. It's why I prefer "dumb" packaging systems. Just install the program, I'll find the dependencies. If the author doesn't document the dependencies, it doesn't really matter, because as sure as he'll forget to list them in INSTALL.txt, he'll forget to include the dependencies when he creates the RPM.

      --
      Fred

      "A fool and his freedom are soon parted"
      -RMS
    281. Re:Beautiful by benjamindees · · Score: 1

      The second part of the advice is absurd, you can't expect any users outside of a tiny fraction of one percent of all computer users to know what compiling is, let alone actually perform it.

      Then shut up and ask your admin to do it. Any admin worth his salt would rather do it for you than have you go bitching to *developers* about how they should better support you and your stupid ideas of what you should be able to do. You're not paying Linux devs for that level of support, remember?

      The Open Source development model is vastly superior because it cuts idiots out of doing things they shouldn't be doing, and doesn't waste time supporting them when they try. Unfortunately, for most users, installing software is one of the things they can't handle.

      Notice how efficient and secure system administration under a distro like, say, Debian can be? Do you think this is because they give endusers the ability to use bleeding edge software when they don't even have the skills to compile it themselves?

      Correct software development mostly separates users into two groups: developers/admins and idiot users. That's because idiot users won't take the time to debug a program when it crashes and submit a useful bug report, or a patch. They mostly just knee-jerk and upgrade to the "latest version" hoping it's been fixed. This gets software development nowhere (witness the world of Windows) because it takes more effort to support endusers' constant "self-administration" than it does to just fix the problem, and upgrading to fix a bug usually causes more bugs than it fixes.

      You can bet that Linux will move more towards the direction of development and support that I'm talking about. And, what's more, your boss will buy it, because this model will be able to provide the "100 desktops per admin" that he fantasizes about.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    282. Re:Beautiful by terjeber · · Score: 1

      you can't expect any users outside of a tiny fraction of one percent of all computer users to know what compiling is, let alone actually perform it
      Then shut up and ask your admin to do it

      Is it really that effing hard to get this? If you expect the average user of a computer system to have access to a sysadmin, know a sysadmin or be able to afford one for their system, you live in the world of IBM ala 1968.

      Slowly: The majority of computer systems are not managed by a system administrator. They are in homes and in quite small businesses. They don't need a sysadmin, they shouldn't need a sysadmin.

      Any computer system that requires expert help to install the latest video editing software from Sony or image editing software from Adobe will be relegated to marginal status forever, as is the case with Linux right now. Don't get me wrong, I run Linux on all of my home systems, but I am also an expert. My wife, my brother, my father, none of them are experts, and all of them would benefit from Linux-like security on their systems, but none of them would be able to run it without hours and hours of my help, so they don't. My dad will be switched to Apple next time he needs a new computer, so should the others.

      The Open Source development model is vastly superior because it cuts idiots out of doing things they shouldn't be doing

      You just said that the vast majority of computer owners should chuck their computers. That is absurd.

      Unfortunately, for most users, installing software is one of the things they can't handle.

      Weird, they seem to have been doing reasonably OK for years on their PCs and Macs. Are you starting a new company that will go around to every Dick, Joe and Harriet and install software on their computers when they want a new version of their virus software?

      That's because idiot users won't take the time to debug a program when it crashes and submit a useful bug report, or a patch. They mostly just knee-jerk and upgrade to the "latest version" hoping it's been fixed. This gets software development nowhere

      Elitist idiocy. People want to use their tools, not effing debug them. My wife works in graphics design, why the eff should she know anything about how to debug Frame Maker?

      Quite frankly, unless Linux develops a model where ordinary users can install their own applications Linux will forever be relegated to specialty applications in large corporations. If Linux wants to make inroads into small business where computers are used as tools only or the home market, it will have to have something like Apple. It doesn't have to have all the downsides of the Apple solution, but there must be a solution.

      This gets software development nowhere (witness the world of Windows)

      Are you dillusional? Windows have many orders of magnitude more well-functioning end-user applications than Linux. Most people use their computers for image editing, video editing, browsing, email, word-processing and a few other tasks. There is nothing on Linux that comes close to Windows or Apple for most of these tasks (browsing and e-mail being exceptions). Not the same ball-park, not even the same sport. To think that Open Office, the Gimp or the video editing software available for end-users on Linux matches anything available on Windows or Apple is dillusional, and belive me, I have tried almost all of it.

      A computer is a tool. If it has the applications that I need and they work well, it is a good tool. That makes Windows and OSX good tool for a very, very large market, and Linux useless for the same. On the other hand, considering the fact that I am a software developer, it makes Linux the perfect tool for me, but I'm not a typical computer user.

    283. Re:Beautiful by albanac · · Score: 1

      Nuke and re-install in this case would have involved formatting the hard drive. Yes, it's my fault that my partition structure wasn't more sensible. That's totally true. I stuck with Debian for about another six months on all my other machines, but the FreeBSD system eventually just appealed to me so much more. ~cHris

    284. Re:Beautiful by benjamindees · · Score: 1

      If you expect the average user of a computer system to have access to a sysadmin, know a sysadmin or be able to afford one for their system, you live in the world of IBM ala 1968.

      I live in the world of IBM a la 2005. Sounds like you live in the world of Microsoft a la 1995. If you expect to be able to bypass the admin of a Linux system to install some crapware, you can keep your infested Windows box.

      The Open Source development model is vastly superior because it cuts idiots out of doing things they shouldn't be doing

      You just said that the vast majority of computer owners should chuck their computers. That is absurd.


      No, I said users should stick with using applications, not installing spyware.

      If *I* want to install a bleeding edge version of Gimp, I neither want to bother the admin with it nor do I want to force it an all the others users, yet Debian requires me todo exactly that.

      This is what I was responding to. This is what you want:

      People want to use their tools, not effing debug them.

      Can't have it both ways. If you want to use bleeding edge OSS software, you'd better be prepared to contribute, or at least support your own damn self. Oh and by the way, everything you've asked for is technically possible, you just have to know how to do it. No one's going to make it easy because it's a lot of work for absolutely no benefit.

      unless Linux develops a model where ordinary users can install their own applications Linux will forever be relegated to specialty applications in large corporations.

      First of all, that's complete horseshit. Anyone can su to root and install programs on their own machine. What it sounds like you're asking for is the ability to install programs on someone else's machine where you just happen to have a user account. That will never happen, because, like I've said, it just causes more work for everyone involved.

      If Linux wants to make inroads into small business where computers are used as tools only or the home market, it will have to have something like Apple.

      Well, as someone who actually supports Linux in small businesses, I'll just have to disagree. And there are people who will support home users in the same way as Windows, but without limiting the ability of users to screw up their own machines with random malware, I wouldn't expect any better results.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    285. Re:Beautiful by terjeber · · Score: 1

      If you expect to be able to bypass the admin of a Linux system to install some crapware, you can keep your infested Windows box

      Attititudes like that, and the complete lack of understanding of the world that is the reason for those attitutes, will, if the Linux community was driven by it, forever relegate Linux to niche-player status. Thankfully a large part of the Linux community doesn't belive that computers belong in strictly controlled environments only. Most Linux users understand that home-users and small companies also could benefit from using Linux.

      If you want to use bleeding edge OSS software, you'd better be prepared to contribute, or at least support your own damn self

      Here the ignorance shows through to such a degree it is pathetically funny. There are two statements in the rubbish above that are ludicrus. The first is that Linux is bleeding edge. Bleeding edge implies leading edge. If you think Linux is leading edge, you haven't a clue what Linux is. Linux is a copy, a bad such if you look at design and implementation, of a 30 year old operating system. It has tons of improvements, sure, but leading or bleeding edge it is not, and has never been. The second statement in the rubbish is that users of Linux should contribute or shut up. Again, attitudes like that will make Linux a niche player forever, which is silly again.

      Anyone can su to root and install programs on their own machine

      Again, it shouldn't be nesessary to be root to install software on the computer. If my family shares a desktop, and it runs Linux, I am the only one with the root password. That doesn't mean that my wife should have to bug me every time she needs an upgrade to sofware only she uses. That's just dumb. She should be able to install any user software she wants, why not?

      without limiting the ability of users to screw up their own machines with random malware

      You don't have to put people into a Gulag of state-controlled dictatorship just to avoid having them mess up the entire computer. If Linux was, as you apparently think it is, a leading edge system, it would have mechanisms in place for preventing such problems. Sadly Linux is a (good) redesign of a 1970's operating system, very, very far from leading or bleeding edge.

      Please realize that I am not dizzing Linux here, as I mentioned, I use Linux for almost all of my work, but it needs a serious amount of improvement before it can be used by the general population for anything but specialty applications.

    286. Re:Beautiful by 00lmz · · Score: 1

      If they load libgtk+2.6.so you can just
      ln -s libgtk+2.6.2.so libgtk+2.6.so
      Ahh... symlinks...

    287. Re:Beautiful by Anonymous Coward · · Score: 0

      [I'm the AC you are repliying to]

      > While I still think the Resource Manager was a brilliant concept, several shortsighted design decisions made during the early '80's rendered it unscalable

      Ah, yes, the infamous tst instead of tst.l in res manager code that limited it to 32K...

      That beeing said, I used to think that res fork were great, until I realized they duplicate something the filesystem should already be able to do... Of course I was already a NeXTstep developer then...

    288. Re:Beautiful by sandbenders · · Score: 1

      Well put. My Grandma is a nurse- she's competent, capable, and I love her dearly. But she is not ready to deal with dependency issues- well, maybe with patients, but certainly not with her computer. For that matter, my friends in nursing aren't either; they're more comfortable with computers than Grandma, but they spend their time studying how to make people well, not how to compile a kernel. They just need to know email, IM, and the web, and that's all they're interested in (generally).

      --
      Eagles may fly, but weasels don't get sucked into jet engines.
    289. Re:Beautiful by Anonymous Coward · · Score: 0

      OSX has you set up as an admin account, just not root. They disable root by default, and the applications you install still require a password if they manipulate anything in the /System/Library or /Library Directories.

      You can create other accounts that are not admin, and they cannot install apps unless its in thier home directory. And the apps must use ~/Library.

      You can also create accounts with restrictions as well.

      And if you need root (UNIX stuff mostly) either use sudo or enable logging in as root through netinfo.

  2. Symphony looks like the Apple Lisa? by Craig+Maloney · · Score: 3, Interesting

    Is it just me, or does the Symphony look a great deal like the Apple Lisa and other early attempts at GUIs? I'm not saying there isn't anything to see here, but it reminded me of screenshots of the Lisa interface.

    1. Re:Symphony looks like the Apple Lisa? by dutky · · Score: 1
      It's just you. The Lisa interface was, essentially, indistinguishable from the early Macintosh interface. If anything, Symphony OS looks more like a cross between Windows XP and that new widget environment in OS X 10.4 (Dashboard?).

      The Lisa interface would be immediately familiar to anyone accustomed to modern GUIs. It had all the expected behaviors:

      • icons representing disks, applications and files
      • double clicking to open files or launch applications
      • a trash can into which items could be dragged to be deleted
      • overlapping, movable, resizable windows
      • pull-down menus in the same arrangment we see today (File, Edit, ...)
      • a clipboard supporting multiple data types
      • and applications that were, essentially, indistinguisable from their modern equivalents
      It lacked some of the modern fluff (animated icons and menus, drag-and-drop editing, "lickable" themes, etc.) but all the basics were there.
  3. Agree by thijs_w · · Score: 1

    I totally agree with this statement, why not make one graphics layer for all applications like Mac OS X, instead of GTK, GTK2, QT, etc, etc.

    1. Re:Agree by Anonymous Coward · · Score: 2, Insightful

      ...

      Each of those you listed is an ATTEMPT to make "one graphics layer for all applications".

      It's just no one can agree on which one to use.

      (Social problem, not technological).

    2. Re:Agree by lphuberdeau · · Score: 1

      QT and GTK are complete libraries. Creating a new one would simply add to the list: GTK, GTK2, QT, YOUR_NEW_LIBRARY_HERE. There is no way a single library will ever take over in the free software universe and it's perfect that way. It's called freedom. As long as KDE can run GTK apps and Gnome can run QT apps, there is no reason to change anything.

      --
      Qui ne va pas à la chasse n'a pas de gibier
      PHP Queb
    3. Re:Agree by ludey · · Score: 2, Insightful

      Apparently you have not heard of "Quartz" and "Cocoa"

      --
      --------------
      David O.
    4. Re:Agree by ludey · · Score: 1

      well bite my tongue, i meant carbon and cocoa...

      --
      --------------
      David O.
    5. Re:Agree by Perl-Pusher · · Score: 1
      why not make one graphics layer for all applications like Mac OS X

      There are two graphics sets quartz & carbon. It also has X11, for anyone who uses gimp or fink or needs to do an ssh into a unix box and run a gui app. Then there are a large number of java apps for the mac. Java uses it's own graphics layer. That's why it can be damn slow! Just because the themes are all the same doesn't mean that they are the same. I run a fedora box with both kde & gnome similairly themed. Event open office is using kde themed widgets and it looks every bit as coherent as windows or my mac. It's not hard to do.

    6. Re:Agree by TrekCycling · · Score: 1

      Mod parent up. This is obvious what has taken place in the Linux community. And it's questionable, actually, whether it's a "problem" or just the situation as it stands.

    7. Re:Agree by m50d · · Score: 1
      Because there are so many poor benighted infidels that don't realise that they should port all their applications to qt. Some of them even start new applications in non-qt toolkits, the fools.

      Idiot moderators: I'm not being serious. I'm being sarcastic or ironic or some such to make the serious point that the reason linux has so many toolkits is that different people prefer different toolkits, and there's no way you can persuade them to switch to one.

      Non-idiot moderators: where were you last time I said this?

      --
      I am trolling
    8. Re:Agree by TheRaven64 · · Score: 1

      Presumably you mean Carbon and Cocoa, as both of these use Quartz for display. However, comparing Carbon and Cocoa to Qt and GTK is silly. Carbon is a set of C bindings and Cocoa a set of Objective-C bindings to the same UI widgets. Sure, they have different programming models (callbacks Vs event loop), but under the hood they are toll-free bridged (i.e. Carbon's opaque data types are, in fact, Objective-C classes, and the Carbon and Cocoa calls do the same thing). More importantly, from a UI perspective, they both create widgets which look and act in exactly the same way.

      --
      I am TheRaven on Soylent News
    9. Re:Agree by cronot · · Score: 1

      It's called freedom. As long as KDE can run GTK apps and Gnome can run QT apps, there is no reason to change anything.

      Yeah, I've heard this mantra for long now. The problem is that this kind of thinking values more a line of ideology than users, the ones that actually have to struggle with the system.

      I've already given up on the hope that Linux might have only one toolkit, or even better, that it would be embeeded on the X Server (you know, you'd have one less application layer to go through to do stuff on the screen). Now, I'd be happy if at least we could have a standardized themeing for all tookits, as in you could use one theme for all toolkits. What most bother users on having N toolkits is that they don't have a consistent look between them. You may argue that this does happen on Windows too, but it certainly happens at a far lesser degree. And it mostly don't happen with MacOSX.

    10. Re:Agree by Anonymous Coward · · Score: 0

      These days, GTK2 is pretty much the standard. KDE is the only thing that still sticks by Qt.

    11. Re:Agree by Anonymous Coward · · Score: 0

      Mac OS X has the same problem. Multiple APIs from Apple itself. Not to mention other third party libraries like Qt (yes, the same Qt you mentioned).

    12. Re:Agree by ssj_195 · · Score: 2, Informative

      I personally don't even notice it any more (probably because the only GTK app I use is gaim, and very occasioanlly, GIMP :)), but I guess it's confusing for most new users. Has anyone tried out gtk-qt? Does it work at all well? Obviously it can't handle entirely different UI conventions, but I guess it could possibly make things at least look the same.

    13. Re:Agree by mwood · · Score: 1

      And I don't use KDE *or* Gnome, but as long as I have the toolkit libraries I can run all the GTK and QT app.s I want. And Motif app.s, and FLTK app.s, and....

      One Toolkit To Rule Them All is for me not a solution but a problem to be avoided.

    14. Re:Agree by Canberra+Bob · · Score: 0, Offtopic

      "Non-idiot moderators: where were you last time I said this?"

      Non-idiot moderators? Likely having lunch with the Tooth Fairy and Easter Bunny

  4. A parrot? by saintp · · Score: 0

    It's not a dupe, but close. Call it a parrot?

  5. A Mystery Wrapped in an Enigma... by Adrilla · · Score: 4, Insightful

    Interesting. An advertisment, disguised as an Apple article, disguised as a Linux topic. Interesting.

    --

    "Plans are for fools! Oglethorpe, the plutonian (Aqua Teen Hunger Force)
    1. Re:A Mystery Wrapped in an Enigma... by tomhudson · · Score: 4, Interesting
      Interesting. An advertisment, disguised as an Apple article, disguised as a Linux topic. Interesting.
      ... and a dupe on top of that.

      We discussed this earlier this week when Dvorak trie d to piss on everyone's parade with the same opinion.

      It was BS then. Its BS now. All Apple on x86 does is give street cred to the idea of switching away from the Bitch from Redmond. Eveeryone else benefits at that point.

      In other news - the sun shines, the earth rotetes, life goes on.

    2. Re:A Mystery Wrapped in an Enigma... by Cromac · · Score: 1
      We discussed this earlier this week when Dvorak trie d to piss on everyone's parade with the same opinion.

      From all the way back to yesterday, not even 24 hours between dupes now.

    3. Re:A Mystery Wrapped in an Enigma... by tomhudson · · Score: 1

      Hopefully the Mad Crapflooder will repost a bunch of interesting comments from other stories in this thread, and it won't be a complete loss of electrons.

    4. Re:A Mystery Wrapped in an Enigma... by Kjella · · Score: 1

      From all the way back to yesterday, not even 24 hours between dupes now.

      Well, at least they're not both on the front page (been here, seen that). On that note, time to quit "working" and go home.

      --
      Live today, because you never know what tomorrow brings
    5. Re:A Mystery Wrapped in an Enigma... by antiMStroll · · Score: 1

      No kidding. If this, what looks like bits of the Rox desktop combined with Karumba and some icons locked into corners, represents Linux's only hope the OS is well and truly screwed. Or, as you say, it's an ad.

    6. Re:A Mystery Wrapped in an Enigma... by anaesthetica · · Score: 1

      This may be why CmdrTaco sent this story over from the "not-bloody-likely dept."

    7. Re:A Mystery Wrapped in an Enigma... by Kirby-meister · · Score: 1
      It seems most of /.'s article headlines these days have been either flamebait, shock-value, or on the lines of "fear-inducing."

      Which isn't far from how most US news media outlets act. Over here in Northern VA good old Fox in DC was airing commercials about "a deadly bacteria spreading around the DC area that could kill you!"

    8. Re:A Mystery Wrapped in an Enigma... by Anonymous Coward · · Score: 0

      Sorry to post as AC but cannot currently remember my password. This is not an advertisement at all, at least not a solicited one. I am the maintainer of the symphony os project and I had dreaded a mention on slashdot since we are self-hosted.. we do not have hosting via sourceforge or any other provider. I have had to set a bandwidth limit and disable the server to prevent other sites from going down. The site can still be viewed on our backup http://isptec.net/~symphonyos.com/

    9. Re:A Mystery Wrapped in an Enigma... by Anonymous Coward · · Score: 0

      If I may introduce yet another Slashdot meme... ...I smell ad!

    10. Re:A Mystery Wrapped in an Enigma... by Anonymous Coward · · Score: 0

      Welcome to Slashdot. Dupes for Nerds. Stuff that Matters.

    11. Re:A Mystery Wrapped in an Enigma... by KillerDeathRobot · · Score: 1

      ... and a dupe on top of that.

      Except it's not really a dupe. It has pretty much the same title, but it's about Symphony OS and has (next to) nothing to do with the article that was posted yesterday.

      I'm not sure I understand what's going on though. Is posting a fake dupe some kind of reverse psychology or what?

      --
      Thinkin' Lincoln - a web comic of presidential proportions
    12. Re:A Mystery Wrapped in an Enigma... by Pollardito · · Score: 1

      an advertisement for an Alpha product no less

    13. Re:A Mystery Wrapped in an Enigma... by tomhudson · · Score: 1
      Seeing as nobody can actually get to the site hosting symphony (bandwidth limit exceeded, poor sod), and how symphony has squat to do with the headline (whether OSX86 is a threat to linux), I really don't know just WHAT to make of the story. The headline's a dupe, sure enough.

      THe content of the article could charitably be rated "off-topic" ...

      Maybe the editors have today mixed up with Troll Tuesday.

      What I want to know is:

      1. How did Apple keep this (the parallel builds) a secret for 5 years?
      2. Since they DID keep it a secret for so long, why release it NOW?
      3. Since Apple IS capable of keeping secrets, were all the other product leaks "managed", and if so, are they going to retract their lawsuits against prior leakers?
      I think THESE are the real "story points" here.
    14. Re:A Mystery Wrapped in an Enigma... by conteXXt · · Score: 1

      I browse at +2 so I may have missed it but:

      Why isn't anyone mentioning better win32 emulators as a benefit?

      --
      The truth about Led Zep should never be told on /. (Karma suicide ensues)
    15. Re:A Mystery Wrapped in an Enigma... by Anonymous Coward · · Score: 0

      Except that it's NOT actually a dupe. It's a different article.

  6. Wow.... by Rod76 · · Score: 2, Insightful

    Its a really sad day when Mac OS X becomes a potential threat to one of its close relatives.

    --
    Die First, Then Quit
    1. Re:Wow.... by AKAImBatman · · Score: 1, Insightful

      Its a really sad day when Mac OS X becomes a potential threat to one of its close relatives.

      Considering that Linux is a ground up copy of Minux, which is a ground up rewrite of a simplistic System V system, which traces its roots all the way back to K&R, with a very brief stopover at BSD for a bunch of tech, whereas OS X is a direct derivitive of Mach/FreeBSD 5.x, I fail to see how they're close relatives. Unless, that is, you are referring to the large amount of BSD technology used at various points in Linux's life?

      Truthfully, I don't think anyone is threatening anyone else. Mac OS X has always been attractive to Unix lovers because of its excellent ability as a desktop/laptop/workstation operating system. This is an area that Linux is really unable to compete, despite its best efforts. Similarly, OS X doesn't really compete in the server arena despite its best efforts. This will probably change in the future, but Apple moving to Intel will have no effect on the status of relations between Linux and OS X.

    2. Re:Wow.... by AKAImBatman · · Score: 1

      Darn. s/Minux/Minix/g

    3. Re:Wow.... by TrekCycling · · Score: 1

      Right. Unless I can load OS X on my personal home-built PC, I don't see the threat. There may be a threat in terms of Red Hat or SuSE, but Linux will survive just fine. It was around before it was being bankrolled by those companies and it will be around afterwords, because there will always be people who want a free alternative to either Windows or OS X.

    4. Re:Wow.... by Anonymous Coward · · Score: 0

      Unix-like (or POSIXish) systems can be considered close relatives, even if not in terms of actual shared code, they are in design philosophy, source compatibility etc. Consider that despite OS X and FreeBSD sharing code, FreeBSD is far more similar to Linux in its characteristics than it is to OS X.

      Agreed that Mac/x86 vs. Mac/ppc will have no noticable effect on Linux...unless some day, OS X runs on commodity PCs.

      It'll be interesting to see how Apple prevents this; Darwin does run on PCs, and MacOS X on Mac/ppc can (or at least could in the past, I don't know about recent versions) work even if you recompile the kernel from freely available Darwin sources...

    5. Re:Wow.... by mrchaotica · · Score: 1

      OS X and Linux are close relatives in the same way that Amiga, BeOS and Windows aren't.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  7. Linux vs. Mac OS X by nphinit · · Score: 1, Flamebait

    For many of us, Linux will likely never be able to compete against OS X for one simple reason:

    Most anything worthwhile that you can do in Linux, you can also do in OS X, and often much more easily. The reverse isn't *close* to being true.

    OS X is what Linux dreams of one day being. Why not use what Linux *may* have in 10 years, today?

    1. Re:Linux vs. Mac OS X by xtracto · · Score: 1

      Because:

      Free as in Freedom.
      Free as in Beer.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    2. Re:Linux vs. Mac OS X by CoolMoDee · · Score: 2

      Because OS X won't run on most every machine out there like Linux will.

      --
      Jisho - A Japanese English German Russian French Dictionary for the rest of us.
    3. Re:Linux vs. Mac OS X by rokzy · · Score: 1

      Free as in Happy.

    4. Re:Linux vs. Mac OS X by mary_will_grow · · Score: 1

      "Most anything worthwhile that you can do in Linux, you can do in OS X."

      That is simply not true. And linux CERTAINLY does not dream of becoming proprietary software. I think you've missed the WHOLE POINT OF THE F/OSS COMMUNITY, if some proprietary software with a better user interface can come along and make you dump linux.

      If I want to try out some fancy new process scheduling idea I had, guess what, I can do that in linux. If I had some new filesystem I wanted to implement, I can do that in linux. I dont need to reinvent a whole new OS to try out a few small ideas. Another approach to trying these ideas would be to get a job at an OS vendor. Seems like a lot more commitment then simply downloading the kernel and reading a few wikis.

      Linux is a platform for creative geeks to try things out, and the innovations that have come from it are free for all of us to use, even proprietary software vendors.

      Also, programming for the linux platform means you'll be able to compile your stuff on a zillion different hardware platforms. Not just the ones in sexy magnesium cases. Or just the ones w/ powerpcs and pentiums.

      I dont think linux dreams of being OS-X at all. I think *you* dream of linux being OS-X. And thats awesome, maybe with your support the GUI will get better. I dream of it having feature X. Maybe I'll put it in. Wheee!!! get it yet?

      --
      Why stick up for big business?
    5. Re:Linux vs. Mac OS X by Anonymous Coward · · Score: 0
      You have a very narrow view of the computer world. The desktop may be the end-all of computing to you, but it is only a very small part of the computer universe.

      For many who deal in such things, I think the majority would pick Linux over OS X for servers, embedded products, and clustered computing. Very many computer-saavy people would consider these areas to be "worthwhile" as well. I'm sure ease-of-printing and playing iPod music can be deemed "worthwhile" too (though I will say that CUPS has never given me the problems that people bitch about), I rank them pretty far down the scale in a relative sense as compared to the three I mentioned.

    6. Re:Linux vs. Mac OS X by FauxPasIII · · Score: 1

      > Most anything worthwhile that you can do in Linux, you can also do in OS X, and often much more easily.

      Okay, then boot Tiger on my Sparc 5.

      --
      25% Funny, 25% Insightful, 25% Informative, 25% Troll
    7. Re:Linux vs. Mac OS X by m50d · · Score: 1

      Freedom. That's what it's all about, that's what it has always been about, right from when RMS started it in what, 1984?

      --
      I am trolling
    8. Re:Linux vs. Mac OS X by Anonymous Coward · · Score: 0

      yeah, we need the secure version of the C language first! Hello ATT Labs!

    9. Re:Linux vs. Mac OS X by Anonymous Coward · · Score: 0

      OS X already has feature X. That's kind of the point, idoit.

    10. Re:Linux vs. Mac OS X by Codename_V · · Score: 1

      From what I understand, even after the switch to x86 cpus, OSX will still only run Apple branded hardware. That being the case, I think soon it will be OSX that has a hard time competing with Linux.

      Also I've used OSX. Sure it has a wonderful gui tacked on making it easy to use for your everyday Joe. But I really don't think a properly set up Linux machine, with Gnome or KDE tacked on, is all that much different for an end user.

      However from an admin point of view I found OSX to be quite clumsy. For example on my Linux systems, if I want to set up NFS automounting, it's a fairly straightforward process that I can pretty much automate either during an install or after the fact. But on OSX I need to use a gui application that rather reminds me of Windows regedit. And I believe controlling services was similarly painful. If I had to deal with all my Linux machines in this way I'd go nuts.

      Or perhaps it's just my ignorance of OSX that's showing above. But after searching and searching for documentation and even contacting Apple tech support, that was the best I could come up with. Or perhaps things are different on the server version of OSX. I dunno. If I'm merely ignorant, then forgive my ignorance. At any rate, since it meets my needs quite adequately as both a server and a workstation operating system, and since you can't beat the cost, I'll stick with Linux.

      --
      Free will is just an illusion
    11. Re:Linux vs. Mac OS X by Jugalator · · Score: 1

      Hm.. Now this is kind of off-topic but that gave me an idea that Apple hardware may become much more popular than ever before. Sure, OS X won't run everywhere since Apple is locking it down, but during the keynote, Apple said they'd fully expect people to install and run Windows on their computers and didn't intend to do anything about it. And if Windows is compatible enough out of the box with their hardware, I guess Linux will be as well, or at least not too hard to make it so.

      This has to be a major reason to why Apple switched architecture -- to make their hardware far more attractive part thanks to OS X, and to build a great multi-OS system. I feel stupid for not having connected the dots before, now. :-)

      If Apple computers can dual-boot between OS X and Linux, guess which hardware anti-Microsoft people will come in droves for. Heck, even Windows users should find them interesting.

      --
      Beware: In C++, your friends can see your privates!
    12. Re:Linux vs. Mac OS X by pebs · · Score: 2, Insightful

      OS X is what Linux dreams of one day being.

      Total bullshit. Nevermind the fact that Linux doesn't have a single entity behind it and can't "want" to be anything. I use both Linux and OS X and find that they are oriented towards different areas. OS X still has long ways to go before being a server-oriented power-user UNIX system (although it tries), although it has the desktop thing down. Linux has ways to go before being a desktop-oriented non-techie-user system although it has the server thing down. And not everyone likes the choice of GUI that Apple rams down your throat. Personally I like a little choice in my user interface, and OS X is very deficient in that area.

      If Apple screws up something in their UI (which we saw with Tiger), you are pretty much stuck with it unless they fix it. This is not so much a problem in Linux distros where everything is open source..

      --
      #!/
    13. Re:Linux vs. Mac OS X by LnxAddct · · Score: 1

      Err okay then please give me fine grained access control over my system like that which is provided to me with SELinux running on my Fedora Core 3 box. Or please go open up a gui tool, or command line, and choose any one of thousands of applications to install at your will for free at the click of a mouse. Try upgrading your OS without paying a penny. How about running a whole network of thin clients that boot off the network over PXE? Also, go grab one of those old PCs you have lying around and breathe new life into it by installing OSX on it, oh wait... you can't. All of this is only a few clicks away when using linux. OS X also doesn't have 1/10 of the hardware support that linux does. Linux does many many more things that OS X just can't compare with. The only reason OS X works as well as it appears is because Apple controls every aspect of your computing experience from the hardware up. If that sits fine with you just so you can have some arguably good eye candy, then good for you but I recommend grabbing linux and doing some real work with an OS designed to be used and not just looked at. OS X will never be able to compete with linux, especially as long as its closed source. Can you list any examples of things that OS X does notably better then linux? Have you even used linux to know? Other then multimedia stuff, OS X is pretty lacking.
      Regards,
      Steve

    14. Re:Linux vs. Mac OS X by Anonymous Coward · · Score: 0

      Or my ipod!

    15. Re:Linux vs. Mac OS X by Princeofcups · · Score: 1

      > Because OS X won't run on most every machine out there like Linux will.

      OSX out of the box, no. But the Mac community has been able to get OSX running on unsupported Macs without too much difficulty. Darwin runs on anything. It won't take too long for someone to crack whatever meager copy protection that Apple will cook up. Jobs probably wants the hacker community to get all excited it. By the end of next year, folks all over corporate America will be showing off their Dells running OSX, just like they used to show off their WinXP betas.

      jfs

      --
      The only thing worse than a Democrat is a Republican.
    16. Re:Linux vs. Mac OS X by Mr.+Spontaneous · · Score: 1

      mod parent up... I just used my last mod points on the previous article.

      --
      Its all fun and games until someone loses an eye... then its just fun.
    17. Re:Linux vs. Mac OS X by Anonymous Coward · · Score: 0

      Is the desktop really a "very small part"? Considering how many people have a desktop at home and a desktop at work and how few servers there really are in an actual business compared to the number of desktops, that may not be the case.

    18. Re:Linux vs. Mac OS X by antxxxx · · Score: 1

      I have never wanted to implement a fancy new process scheduling idea.
      And as for filesystems, I want one that saves my files and allows me to retrieve them again. I have never even considered implemnting a new filesystem that may not do these 2 things 100% of the time.

      I guess this means that OS X on x86 will be better for me than linux. How many other people do you think there are that feel the same way as me?

    19. Re:Linux vs. Mac OS X by rpozz · · Score: 1

      I would say it's more the other way round. For my purposes, and I assume many others, OS X really doesn't have any functionality that Linux doesn't apart from eye candy and ease of use. This may, however not be the case for people who require specific graphics software.

      Linux will also run on just about any computer you can find, is completely free, and is improving at an impressive rate. Look at a Linux distro from 5 years ago, and look at one now. OS X isn't cheap and only runs on expensive hardware.

    20. Re:Linux vs. Mac OS X by Anonymous Coward · · Score: 0

      Happy as in Gay.
      Gay as in Homosexual.

    21. Re:Linux vs. Mac OS X by mwood · · Score: 1

      There's an important point in here. Electron microscopes will never become popular enough that you'll find them stacked on the shelves at Wal*Mart. But there is a profitable market for electron microscopes nonetheless. There are people who quite reasonably want to do things that I not only do not want to do but may be unequipped even to imagine. Assuming that everything must either serve the needs I can imagine, or inevitably die, is a great way to set myself up for astonished disappointment.

    22. Re:Linux vs. Mac OS X by jedidiah · · Score: 1

      Except that spiffiness still requires you to dump your current system and buy into something highly proprietary controlled by a single source vendor. While a negligible part of the market might consider that, most users simply aren't buying into the idea.

      Until THAT changes, none of the other x86 operating systems have anything to fear.

      Infact, Solaris x86 still remains more relevant.

      The prospect of MacOS "killing" Linux on the desktop remains unchanged.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    23. Re:Linux vs. Mac OS X by Anonymous Coward · · Score: 0

      Come on then, what is feature X? What is so good about your horendously over-priced OS?

    24. Re:Linux vs. Mac OS X by shmlco · · Score: 1
      Free as in Freedom.
      Free as in Beer.

      There's no such thing as a free lunch.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    25. Re:Linux vs. Mac OS X by MightyMartian · · Score: 1
      If x86 OSX is going to do any harm, it's going to be against Microsoft, and that's only if it can bring down the costs of its proprietary hardware. I think Apple may have something here, but they've got to reduce costs and get developers to start porting over x86 Windows software to the x86 Mac. As far as Linux is concerned, about the only people I can think of who may be distressed is Yellow Dog users.

      We all know what's going to happen within a week or so of the first x86 Mac Mini being released, and that's that someone is going to port Linux to it.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    26. Re:Linux vs. Mac OS X by mary_will_grow · · Score: 1

      No.
      Lucky for you other people wanted to try new filesystems and new process schedulers, and thats why Linux got so good so fast. And will continue to stay good. Its a good idea magnet. Thats good for you, too! wheee!!!!

      --
      Why stick up for big business?
  8. Choice of processor threatened Linux? by Anonymous Coward · · Score: 0

    How? If Apple's desktop threatens Linux, it shouldn't matter what processor it is running on. Loser article, but I guess the editors are just considering page views and number of comments, not being particularly insightful or enlightening.

  9. Obivous article + ad = frontpage story by rdwald · · Score: 1

    Summary of article: Linux needs better hardware drivers if it's going to compete with Mac on the same processor. No, we thought that Linus had more influence with hardware manufactures than Apple, a hardware company, does. Summary of SynphonyOS: Ooh look! Another distro! With a unique package management system! I'm sure that'll take off.

  10. Never happen by Anonymous Coward · · Score: 0

    Never in a million years. Linux is unstoppable since it has no central one owner. Anyone who thinks otherwise is logged into reality as root.

  11. Plug much? by addaon · · Score: 1

    This is more than linux with a very very slightly different desktop environment (dock? check. hot corners? check. active desktop? check. ugly chrome... it'll get uglier in time.) how?

    --

    I've had this sig for three days.
  12. DUPE by a_greer2005 · · Score: 1, Insightful

    this is a big dupe, and let me answer the question: NO it isnt a threat, If aple ties it to hardware amd people break that and make it work on anything, that is a DMCA violation and thus only a relative few qould do it, most that want apple will buy apples anyway because theoor hardware is nicer than the PC equicelant for not too much more $$.

    1. Re:DUPE by Anonymous Coward · · Score: 0

      http://cyber.law.harvard.edu/openlaw/DVD/1201.html

      Reverse engineering software for the purpose of interoperability is specifically allowed under tthe DMCA

    2. Re:DUPE by Anonymous Coward · · Score: 0

      My condolences on your condition, someday we may have the ability to regrow arms and you won't have to type with your tongue anymore.

  13. Only if by Kilz · · Score: 4, Insightful

    Apple wants to commit suicide and alow the Mac os to be run on generic pc's. So far what Iv read says that the Mac os will still only run on Mac's. Apple has no plans on releasing the os as software to run on any pc.

    --
    I trust Microsoft as far as I could comfortably spit a dead rat
    1. Re:Only if by Paul+Rose · · Score: 1

      Bingo
      I might agree that Linux enthusiasts ... must rethink the concept of Desktop has we know it today
      Mac OSX might be a threat, but no more so on Intel than it was on PPC. No way does Apple want to become an OS vendor. They'll do all they can to prevent OS X from running on non-Apple PCs using both legal and technical approaches.
      Some hackers might figure out out to get it working 90%, most of the time, if you sacrifice the correct rooster on a full moon, but OS/X on PCs will not become mainstream.

    2. Re:Only if by Ubeor · · Score: 1

      My question is not whether MacOS x86 will run on generic PCs, but whether Windows will run on the x86 Macs. It could be a selling point for Apple -- buy it with MacOS, and, if you don't like it, you can switch to WinXP on the same hardware!

    3. Re:Only if by dioscaido · · Score: 1

      That's one comment I never understand. Why would it be suicide for Apple to allow OSX to boot on any PC? Wouldn't they make far more money selling millions of copies of OSX than selling millions of desktops?

      I think moving OSX to the general PC platform would be a genius move, assuming they can handle all the hardware configurations gracefully. This is the only way, IMHO, that OSX could really make a dent in Windows' market share. Right now, to switch they have to get rid of their current hardware AND software, and those are some pretty big steps. It seems like OSX x86 has the possibility of running Windows apps through something like WINE. Take out the custom hardware and now it's not that huge of a deal for someone to switch to OSX.

    4. Re:Only if by John+Bokma · · Score: 1

      If Apple is stupid enough to not sell the OS separate I don't wish them luck. It will be on BitTorrent by the end of this year, and running on millions of PCs in a few months.

    5. Re:Only if by chipset · · Score: 1

      I can't find the link, but yes, the Apple system will allow booting of Windows XP. An Apple Exec said it.

    6. Re:Only if by Steven+W00ston · · Score: 1, Insightful

      Yes, and I'm sure OSX will ship with drivers for all of the hardware on those millions of PCs.

      --
      Steven Wooston, Lead Programmer, J-J-J-Julius Games
      Author of a CONSIDERABLE number of best-selling games
    7. Re:Only if by moderators_are_w*nke · · Score: 1

      I breaks the niceness. MacOS X and the Apple platform are solid, reliable and expensive. At the moment every mac you buy is a balance of hardware and software that makes it reliable, fast and great to use. If you run MacOS X on a cheap PC which crashes all the time, it will lose that.

      Also, its just chav. I paid a lot of money for my Mac, it looks great and runs great. I don't want everyone on the planet running MacOS X because then its exclusivity, and if any version of MacOS X that runs on any old PC (even the dev previews) gets out, every no-name korean brick will be running it before you can say bittorrent.

      --
      "XML is like violence. If it doesn't solve your problem, use more." - Anonymous Coward
  14. x86 != PC by FidelCatsro · · Score: 4, Insightful

    Apple are moving to X86 yes , but it wont be standard PC equipment .
    This is no threat to linux , Apple are going to keep with their custom hardware and linux for A-x86 will spring up and take over in a few years from linux for PPC (well not totally )

    --
    The only things certain in war are Propaganda and Death. You can never be sure which is which though
    1. Re:x86 != PC by nick-less · · Score: 1

      Apple are moving to X86 yes , but it wont be standard PC equipment .

      I bet a Mac On Linux x86 Edition is available 6 month after 10.5 for Intel Macs...

    2. Re:x86 != PC by FidelCatsro · · Score: 1

      That would be great , I am going to hold off buying a new Mac now till the switch is completed .
      Wine and "Mac on linux" would make for a great working environment

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    3. Re:x86 != PC by WhiteDeath · · Score: 1

      actually, I imagine it will more likely be linux-ppc compiled for x86 (more or less)

      Apart from some chipset specific stuff, it should be similar inside to a ppc, but will need to be compiled for an x86 instruction set.

    4. Re:x86 != PC by jojo1835 · · Score: 1

      That's the real question. Will it use Industry Standard Hardware, or will I have to purchase a "Macintosh Intel Workstation" to get my OSX on a P-whatever? Has anyone got an idea?

      TT

      --
      See... and you thought your sig was boring - TT
    5. Re:x86 != PC by FidelCatsro · · Score: 1

      I agree it most likely will be similar to open-firmware and the hardware set-up apple use already , however binary/source compatibility will hopefully be allot better for Linux Ax86 as opposed to PPC(obviously just the Source part in that comparison)

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    6. Re:x86 != PC by FidelCatsro · · Score: 1

      There is 0 chance apple will release x86 for standard equipment , after-all they are a hardware company and make hardly any money off of OS sales in comparison .
      So the real question is will someone find a hack to make OS x run on standard equipment , Im sure apple will do their up-most to see that never happens. Besides its unlikely considering they will probably use a rather different set-up most likely similar to Apple PPC.

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    7. Re:x86 != PC by jfengel · · Score: 1

      Even before switching to x86, Mac has started using a lot of commodity hardware (memory, IDE hard disks, USB for mice and keyboards). IIRC they still have an idiosyncratic video connector but I gather that they still use at least partly commodity video boards.

      Do they still encode part of the OS in ROM on the motherboard? They used to, but I thought they'd dumped that years ago.

      What's left besides the motherboard? Are they going to roll their own chipset?

    8. Re:x86 != PC by Anonymous Coward · · Score: 0

      The equipment will be 100% Intel Standard, just like a Dell. Apple will simply use Intel-standard "trusted computing" hardware features to ensure that the OS only boots on Apple-branded boxes.

    9. Re:x86 != PC by Anonymous Coward · · Score: 0

      not likely , that would make hacking the OS far too easy . Remember Darwin is an open kernel and base system

    10. Re:x86 != PC by FidelCatsro · · Score: 1

      'They have been using Open-Firmware for their PPC hardware so I don't see why they would switch from Open-Firmware now . they will most likely use all standard equipment bar the motherboard and the BIOS.
      So i imagine it will be significantly diffrent

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    11. Re:x86 != PC by Anonymous Coward · · Score: 0

      The distributed version of OS X != Darwin. Apple had closed-source hardware drivers. Or just put the Trusted Computing checks in the GUI layer.

    12. Re:x86 != PC by TheRaven64 · · Score: 1
      Apple abandoned their own display connector (ADC) in favour of DVI about a year back[1]. Their video cards were different because they required Open Firmware compatible ROMs, not BIOS compatible ones. They were, however, the same as those sold by Sun for a couple of times the price. I suspect that they will go with a standard PC BIOS, which is a shame, since Open Firmware is a whole load nicer.

      [1] A shame really. ADC carried digital video, USB, and power in a single cable. My Apple Cinema Display without ADC requires 4 cables (FireWire, USB, Power and DVI).

      --
      I am TheRaven on Soylent News
    13. Re:x86 != PC by EggyToast · · Score: 1
      Actually, they dropped the video connector with the last batch of monitors. They used to use ADC, which was simply DVI with a few extra plugs for USB support. As only their monitors used ADC, most everyone was forced to buy adapters for dual-monitor stuff.

      So they gave up on it.

      But yeah, the guts really aren't that different from a standard x86 computer's interior at this point. The video cards have a different chipset, most likely due to PPC and the mainboard, and the mainboards are customized.

      As long as they're making those custom mainboards, they don't have much to worry about. That's what most of the most important drivers in the OS deal with anyway, and routing data around. So it's still enough to make them "customized machines" and "uniquely mac," but yeah, all that's really left after the Intel switch is the Mainboard.

    14. Re:x86 != PC by germanStefan · · Score: 1
      i agree with this. The types of people who buy macs will continue to buy macs, no matter what processor. And those using Linux are using it on x86/PPC because they like the idea of open source and having the ability to hack through source code. Those people wont be switching to Mac OS X on x86 just because they can.

      THe biggest threat that this Mac OS X on x86 is to windows. Especially with college bound students. Many already have ipods and love them. Knowing that they can try out Mac OSX and if they dont like it, bail for windows. And usually the things we learn in college stick with us...right?

    15. Re:x86 != PC by Anonymous Coward · · Score: 0

      Apple has stated NO Open Firmware. Expect EFI instead, which is functionally equivilant.

    16. Re:x86 != PC by ak3ldama · · Score: 1

      "I suspect"... That's all that any of this is, guessing. The fact of the matter is that Darwin boots on BIOS, and current hardware uses OpenFirmware. x86 people want BIOS so they can give OS X a whirl without buying Apples hardware, because they have the belief that Apple doesn't magically produce better hardware like everyone else thinks. And Apple fans want OpenFirmware because it's a more elegant solution (and what they're used to), and they would rather be able to keep their elitist status of being the only ones that are able to run OS X.

      --
      "but money is the God of Algiers & Mahomet their prophet." - Rich. O'Bryen June 8th 1786
    17. Re:x86 != PC by magarity · · Score: 1

      No, no, the real question is whether or not Microsoft is going to release Windows for the PowerPC to take up the slack in that market.

    18. Re:x86 != PC by blueZhift · · Score: 1

      Indeed, unless Apple decides to release MacOS X on Intel as a separate product that runs on standard PC hardware, Apple on Intel is no more of a threat to Linux than it has been in the past. And since Apple makes a nice bit of change selling Macs as they are now, why should they want to kill that off? I suspect that creating the "Apple Experience" would be a lot harder without control of both the OS and the hardware. Apple isn't likely to give up that control anytime soon, they'd be crazy to do that since so much of their reputation is built on design and ease of use!.

    19. Re:x86 != PC by hkb · · Score: 1

      Actually from all current indications, hints and hunches from folks inside Apple is that they will be standard PC's with standard motherboards and perhaps slight customizations. Although this is all hearsay because apparently, Apple STILL isn't exactly sure which way they'll go.

      But you can betcher ass they'll do something to this effect. Who's to say it that hacked versions of 10.5 that run on white box PC's won't show up on the net within two weeks.

      --
      /* Moderating all non-anonymous trolls up since 2004 */
    20. Re:x86 != PC by jaycontonio · · Score: 1

      Yeah, ATA, SATA, AGP, DDR RAM, firewire, usb 2, and a Pentium 4 are never found in the same box like Apple's boxes. Apple boxes will be a standard PC. Just better quality.

    21. Re:x86 != PC by FidelCatsro · · Score: 1

      Its more to do with the motherboard and Open-firmware , Perhaps linux for x86 may work on Apple-x86 with a few minor tweaks to the kernel and a new boot loader (here's hoping that's all it takes )but OS X wont work on standard PCs so the fears are groundless .

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    22. Re:x86 != PC by jaycontonio · · Score: 1

      Yeah you're right on that one...the only difference though between an actual mac and a pc will be a custom motherboard. The parent seems to think every bit of Apple's hardware is custom, which is a lie.

    23. Re:x86 != PC by tholomyes · · Score: 1

      True. Interesting quote from this article:

      After the keynote, Apple's Phil Schiller stated that there are no plans to sell or support Windows on an Intel-based Mac. "That doesn't preclude someone from running it on a Mac. They probably will," he said. "We won't do anything to preclude that."
      --
      When did the future switch from being a promise to a threat? -C. Palahniuk
    24. Re:x86 != PC by FidelCatsro · · Score: 1

      Hate to point this out to you ,:P but i am the parent . You just misread my sentiment ;) .

      --
      The only things certain in war are Propaganda and Death. You can never be sure which is which though
    25. Re:x86 != PC by Anonymous Coward · · Score: 0

      The dev kit is a standard PC with a custom BIOS. The developer docs confirm that the final product will be a PC with a BIOS. So yeah, it is standard PC equipment.

    26. Re:x86 != PC by terjeber · · Score: 1

      I bet a Mac On Linux x86 Edition is available 6 month after 10.5 for Intel Macs

      I'll take that bet, in fact, I'll give you more time, I'll give you two years. And I'll bet you $20,000, you can put in $2000 only, whoever is right takes the pot. Unless Apple gives their blessings, it won't happen. OSX on x86 will rely on Apple specific hardware, and I don't see the Linux crowd going into the hardware business yet.

  15. Enlightenment by redog · · Score: 1

    Quit yappin and checkout e17 from cvs and help innovate.

    Or help the rox desktop project.
    Or help fix X11 some.
    Sheesh, OSX is nice and all but I don't think that apple moving to a different processor is going to change FOSS very much.

    I bought my powerbook for the hardware. Put linux on it, and use it for my day to day development on cheap x86's. Apple is not going to have cheap x86's. They will have sexy hardware that comes with their latest OS installed. Whoever is heavily involved in linux and FOSS development either wants cheap comodity hardware to put in a closet or their software can more than likly be ported to build on OSx86 with out much headache.

  16. osX is more Unix than linux by Anonymous Coward · · Score: 0

    I can use OSX to compile gnu stuff, run X and photoshop, bash, with cool eyecandy and rocksolid stability!

    If I can do it on an intel box, I may not need linux. honest. I am not that religious

    1. Re:osX is more Unix than linux by Anonymous Coward · · Score: 0
      I can use OSX to compile gnu stuff, run X and photoshop, bash, with cool eyecandy and rocksolid stability!

      If I can do it on an intel box, I may not need linux. honest. I am not that religious

      Stop sucking dick and listen up: OS x86 will only run on Apple Macintosh brand computers. So you'd need to buy a new (Macintosh) computer. Since you didn't buy a PPC macintosh, you won't be buying a x86 macintosh either. Thank you and go fuck yourself.

  17. Could Apple's Intel Desktop Threaten Linux? by Anonymous Coward · · Score: 0
    Answer: Yes...especially *if* lower cost Macs are introduced which perform well.

    Also, don't forget that there will be Intel servers, too...Apple is going to Intel across it's entire product line.

  18. Linux Desktop by ActionAL · · Score: 1, Insightful

    If linux had a mac os x like desktop it would offer mainstream users a better experience. Not all users are system admin types. But if you want to you still have that freedom to do your thing. Or you can play around in the awesome desktop environment that mac os x is, which i do 90% of the time.

    1. Re:Linux Desktop by Anonymous Coward · · Score: 0

      The fact that your comment get's a "+1 insightful" rather than a "-1 no shit" is why linux will never offer mainstream users a better experience.

  19. How will I karma whore now? by yotto · · Score: 1

    They put a link to Wikipedia right in the article! How will I karma whore now?

  20. Evil Empires. by Savage-Rabbit · · Score: 1

    Could Apple's Intel Desktop Threaten Linux?

    Does this mean that OS.X will now take over from Windows as the 'Root of all Evil'?

    --
    Only to idiots, are orders laws.
    -- Henning von Tresckow
    1. Re:Evil Empires. by maxwell+demon · · Score: 3, Funny

      Well, Windows has no root, so they at best could take over the "Administrator of all Evil".

      --
      The Tao of math: The numbers you can count are not the real numbers.
    2. Re:Evil Empires. by safari-surfer · · Score: 1

      ... they at best could take over the "Administrator of all Evil". Actually that won't quite work since OS.X is a dialect of UNIX and it's super user is actually called 'root', not 'administrator'.

  21. Next... by null+etc. · · Score: 2, Insightful
    If Linux enthousiasts don't want Mac OSX on Intel to become a threat for the future of Linux Desktop, they must rethink the concept of Desktop has we know it today.

    Oh yeah? Why is that? Why does it matter if Mac OSX uses Intel or PowerPC or Transmeta for that matter? Apple will still lock their platform, still charge too much for accessories (such as RAM), still take 20 years to develop a 2-button mouse.

    Tell me, fearmonger, why should I start running down the streets in panic?

    1. Re:Next... by Lysol · · Score: 1

      You're right, there is not much to worry about in Linuxland. Apple poses little threat.

      However, I have issue with a few things.

      1. Lock their hardware platform how? If you mean you won't be able to buy a mobo from vendor A and install OS X on it, then yah, sure. But so what? Part of the problem with Windows is that it tries to support everything under the sun, which I think is a bad idea. Lower-end hardware dilutes the value of the OS.

      2. Too much for accessories. True, but you don't have to buy RAM from Apple. Nor do you have to buy a mouse, keyboard, or even display from them. So besides the replacable parts that come with a Mac, most of the other stuff can be bought at the same price as Windows/Linux stuff. And again, lower end junk might not be supported for that reason - it's junk!

      3. 2 button mouse. Ho hum...

    2. Re:Next... by Anonymous Coward · · Score: 0
      Apple will still lock their platform, still charge too much for accessories (such as RAM), still take 20 years to develop a 2-button mouse.

      You're not forced to buy RAM from Apple, and only absolute ignorant fuckbrains even talk about the mouse button count anymore. Everyone else is informed on the issue, and knows it isn't an issue.

    3. Re:Next... by null+etc. · · Score: 1
      and only absolute ignorant fuckbrains even talk about the mouse button count anymore

      Haha, you talked about the mouse button count.

      Besides, there's something fundamentally flawed with a default manufacturer's mouse which requires you to click to whole damn thing. If I wanted exercise, I wouldn't be sitting at the computer.

    4. Re:Next... by LilMikey · · Score: 1

      If you mean you won't be able to buy a mobo from vendor A and install OS X on it, then yah, sure. But so what? Part of the problem with Windows is that it tries to support everything under the sun, which I think is a bad idea.

      That's exactly was gp was saying and I don't think it's a bad idea. That's why you buy Mac, I buy i386 and run Linux and exactly the reason GP believes Max won't be a threat. I'd like the ability to buy a range of hardware for whatever use I desire. As for hardware support being a problem for Windows, under Linux I've had no problem using the exact same hardware I used in Windows and my system is amazingly stable.

      2. Too much for accessories. True, but you don't have to buy RAM from Apple. Nor do you have to buy a mouse, keyboard, or even display from them. So besides the replacable parts that come with a Mac, most of the other stuff can be bought at the same price as Windows/Linux stuff. And again, lower end junk might not be supported for that reason - it's junk!

      Every non-Mac compatible accessory is junk?

      3. 2 button mouse. Ho hum...

      Amen... tired argument.

      --
      LilMikey.com... I'll stop doing it when you sto
  22. yellowdog maybe and I mean maybe. by infonography · · Score: 1

    Porting yellowdog back to intel should be a snap. The only problem will be that their market will shrink as the powerpc chip vanishes it will be hard to compete with mature intel based distros.

    --
    Sorry about the writing. Robot fingers, you know? Cliff Steele in DOOM PATROL #23
    1. Re:yellowdog maybe and I mean maybe. by wild_berry · · Score: 1

      YellowDog sell PPC machines of their own, on which you cannot run Apple's OS. The availability of the chip will diminish, but I don't think that GNU/Linux/PPC will disappear, possibly lending a lot to the Linux-on-PS3 effort.

    2. Re:yellowdog maybe and I mean maybe. by dboli42 · · Score: 1

      Yellowdog can make more money from High Performance Computing on IBM's hardware than from catering to a tiny Linux on Mac market, Apple may leave PPC, but IBM servers/mainframes/supercomputers aren't going anywhere (not to mention the not yet released cell).

  23. I am really just not seeing the threat? by jallen02 · · Score: 1

    Where is the threat folks? If Apple keeps their OS locked down to Apple hardware the story for Apple is basically the same as it has always been. Apple hardware, very good driver support for supported hardware etc. If you still have to pay for the Apple hardware to run the Apple OS what about the situation has truly changed?

    I am sure someone will have OS X running on every one of their x86 machines the week it comes out. Outside of geek circles though, this won't mean a damn thing. If Apple keeps it locked to Apple hardware business and home user won't be downloading/buying OS X and installing it any time soon.

    "Meet the new boss, same as the old boss".

    At least at first, this really only helps Apple. They will get a wider variety of drivers from FreeBSD. However, I just don't see it affecting Linux and where Linux has been going on the desktop. Apple is still Apple and they still operate on proprietary (read: locked in) Apple hardware.

    Until we here different from Apple and their policy on OS installation this changes nothing and really only benefits Apple in the short term. It will cause little to no change in my opinion.

    Jeremy

  24. *pat pat* Nice troll... by Anonymous Coward · · Score: 0, Informative

    You must be old here.

    Apple is completely debt-free as of last year; Steve Jobs had successful surgery; Mac sales are increasing 40% year-over-year last quater; FreeBSD? please.

  25. Why should OS X be a threat? by MrHanky · · Score: 4, Interesting

    After all, Intel OS X will probably only run on Apple computers (although I think there will be a hacked version, possibly using OpenDarwin, for the pirate market). And while OS X is a damn nice desktop OS, it doesn't really cater to the same audience as Linux. I use Linux only on my Mac, not only because it performs better, but because the apps I wanted to use all work in X11, but not all of them are ported to Aqua.

    1. Re:Why should OS X be a threat? by Princeofcups · · Score: 1

      > I use Linux only on my Mac, not only because it performs better, but because the apps I wanted to
      > use all work in X11, but not all of them are ported to Aqua.

      That makes no sense. X11 runs fine along side Aqua. Unless what you really want is the Gnome Desktop or some such.

      jfs

      --
      The only thing worse than a Democrat is a Republican.
    2. Re:Why should OS X be a threat? by MrHanky · · Score: 1

      Oh, it makes sense: Using X11 under Aqua is ugly and disrupts the normal workflow in either interface. There's a reason why no one bothers using OpenOffice.org on the Mac, and no one even considers using KMail, even though it's much nicer to work with than Mail.app or Thunderbird (well, IMHO).

    3. Re:Why should OS X be a threat? by ooze · · Score: 3, Interesting

      Well, my two reasons to switch to Apple a few months ago (apart from usual Windows frustration), was is doesn't use x86 CPUs and is has OpenFirmware.

      Both will get dropped. iwon't buy any Mac with an x86 CPU or without OpenFirmware. Simple as that.

      Anyone who knows a little about Chip design or actually just did some Assembly programming on more than just x86 knows what a crippled and cumbersome Archtecture x86 is.
      And anyone who knows a little about PC Startup knows what cumbersome and crippled process the whole BIOS (in combination with the good ol' blessed x86 real mode) is.

      The recent Slashdot story about the Mach kernel with all the wrappers around it being an intense Performance hog did make me think a little. Mircrokernels rule, Mach is just an outdated implementation put into wrappers to make it backward compatible. Now Apple computers will have the same sticky things happening on the CPU level as well.

      I guess I'll start building my own computer. ARM Kits aren't that expensive. And with a few friends in manufactoring I can put them in shiny cases too. Or that new open Cell Platform could be interesting too.

      --
      Just because I can imagine doing a hippopotamus, doesn't mean I'd like to do it.
    4. Re:Why should OS X be a threat? by lunadog · · Score: 1

      You tried compiling any X11 programs on the mac recently??

      With all the ugly workarounds: fink and the like, it still isn't as easy as under Linux.. often it doesn't work, and when it does, it does not offer the same level of functionality.

      I use a mac for work, and, while i don't exactly love it, it is certainly better than the windoze selections..

      I run some x11 stuff under freefloating blackbox on the mac, but it doesn't approach the ease of use for building OSS from source, or developing under python/wxPython that my Debian sid box (running windowmaker) offers.

      Still I am probably just a Linux troll..

      Who can tell?

    5. Re:Why should OS X be a threat? by Anonymous Coward · · Score: 0

      Using Intel makes it easier for Apple to swap in a different kernel. I'd guess a BSD, but Linux isn't out of the question, as long as Apple can avoid linking whatever they'd like to keep proprietary against the Linux kernel source.

      I.E. - maybe Apple *will* cater to the same audience as Linux. Maybe that's the whole idea. They've seen where the momentum lies, and want to take advantage. There's a whole shitpile of stuff happening on Linux that Apple can't currently touch...

      It's fun to start rumors anyway. If you're wrong it's no big surprise, but when you're right people say "Wow! What brilliant insight!" Certain columnists make a career out of prognosticating in this manner.. :)

    6. Re:Why should OS X be a threat? by Anonymous Coward · · Score: 1, Insightful

      What makes you think Apple will get rid of Open Firmware?

    7. Re:Why should OS X be a threat? by Mr.+Hankey · · Score: 1

      Good points. The only thing I would add is the lack of dependency on a company/corporation that may go out of business. While it's nice to have the backing of a company in many instances, if they go away you may end up being screwed. I know a few Amigans who could vouch for this, and Apple was rather close to going away before Steve took over the company again.

      That's not to say that OS X is a bad choice. Having been a Mac user in the past though, I know that it's not the right choice for me.

      BTW, nice name there.

      --
      GPL: Free as in will
    8. Re:Why should OS X be a threat? by Princeofcups · · Score: 1

      > Well, my two reasons to switch to Apple a few months ago (apart from usual Windows frustration),
      > was is doesn't use x86 CPUs and is has OpenFirmware.

      Did I miss something? Where did Apple say they were dropping OpenFirmware?

      jfs

      --
      The only thing worse than a Democrat is a Republican.
    9. Re:Why should OS X be a threat? by Wiz · · Score: 1
      To reply to this and another AC....

      Apple Universal Binary Docs

      It says Intel systems will not run on Open Firmware. It doesn't say it is a the "normal" PC BIOS either, or something else. Just not OF.

    10. Re:Why should OS X be a threat? by renoX · · Score: 1

      I can undestand why you like the features of OpenFirmware and while I hate x86 ISA, may I ask why do you care about the CPU used, are you doing assembly programming?
      If yes, I can understand, otherwise that doesn't make sense, who cares what happen between the compiler and the CPU??
      Only price, performance, power consumption matter!

    11. Re:Why should OS X be a threat? by ooze · · Score: 1

      Yes, I do assembly programming. x86 back in the days, but also 68000, ARM and PPC. And while it's only very little code I do by hand (as assmebly programming should be), x86 just isn't fun (although you get the most info on it on the net).
      But more important than just the assembly programming itself is, what possibilities the architecture gives you for the operating system. See, not being able to properly access the firmware without switching to 16bit real mode and all the other little nuisances. It isn't primarily speed that matters. It is primarily how the architecture you have to deal with cripples innovation and new approaches to system design, because you have to do so many workarounds.

      --
      Just because I can imagine doing a hippopotamus, doesn't mean I'd like to do it.
  26. Threat to which desktop... by Kjella · · Score: 3, Insightful

    ...the corporate desktop? I doubt it. The primary advantage of Linux here is to set up simple, free desktops for users which are not locked in to Windows.

    ...the tinkerer's desktop? Nope. They'll keep going with Linux just as they did before Linux could compare to either Windows or Mac (at least on the desktop side).

    ...the mass market desktop? Maybe. Except Linux never really had it to begin with. As for OS X being so much better - well, I must say that I could build a much better Windows experience with Win+commercial apps than I could with Linux, if I had endless cash or no ethical problem with copyright infringement. Still, Linux and the free legal desktop interests me. I don't think it will be significantly different with Linux vs OS X.

    Kjella

    --
    Live today, because you never know what tomorrow brings
    1. Re:Threat to which desktop... by Teckla · · Score: 1

      ...the tinkerer's desktop? Nope. They'll keep going with Linux just as they did before Linux could compare to either Windows or Mac (at least on the desktop side).

      What would prevent OSX/86 from being a good tinkerer's desktop?

    2. Re:Threat to which desktop... by Anonymous Coward · · Score: 0

      What he is saying is that Mac OS/X will not make any Linux tinkerers ready to jump ship to Mac on Intel. Why would they? They could have already jumped ship a long time ago.

    3. Re:Threat to which desktop... by Asic+Eng · · Score: 1
      ...the corporate desktop? I doubt it.

      Exactly - corporate desktop users could buy a Mac now if they wanted. If they don't want to replace their x86-PCs with PPC-Macs now, why would they want to replace them with x86-Macs? They still can't keep their old hardware.

      It would be a different issue if Apple would offer OSX standalone, however their business model is all about selling systems in which they control all components. I doubt they are willing to change this soon. I'm not sure whether it would be beneficial to them, either.

    4. Re:Threat to which desktop... by Requiem18th · · Score: 0

      Price mostly and warranty issues, that are related to price anyway. When you have a "just-works" warranty protected, locked down -unit- manufactured with arcane secret methods, you hardly can afford tinkering with it.

      --
      But... the future refused to change.
    5. Re:Threat to which desktop... by MrCopilot · · Score: 1
      As for OS X being so much better - well, I must say that I could build a much better Windows experience with Win+commercial apps than I could with Linux, if I had endless cash or no ethical problem with copyright infringement. Still, Linux and the free legal desktop interests me. I don't think it will be significantly different with Linux vs OS X.

      I can build a better windows experience too. Look up from my debian box and Look Out The Windows.

      Suppose you could build a windows experience. How long would it last? 6 mos? On average we rebuild our windows workstations at least twice a year. So far my best windows exp has been in emulation. Crash, Stop emulation try again.

      I'm not a Mac user, but I am an admirer. If osX were to be free & run on any ole x86 then I could see a small share of linux users defecting, but in reality how many won't check THE NEXT BIG THING (LiveUMDs just a request), when it comes out? Don't worry cuz, it won't run on any ole x86, only macx86.

      =--
      I'm starting to doubt my humanity, I haven't had to confirm I'm not a script in a week.
      Hmmm Google Slashdot, I thank you for both.

      --
      OSGGFG - Open Source Gamers Guide to Free Games
  27. Windows and Mac OSX vs. Linux by knobo · · Score: 1

    Well, I would say neither Windows or Mac OS X will likely ever be able to compete against Linux (in the long term), unless they go OpenSource.

    For M$ that would be impossible, as they say them selves, windows has to many security-holes.

    For Apple, maybe its possible, but very unlikely.

    1. Re:Windows and Mac OSX vs. Linux by xtracto · · Score: 1

      I agree with you, is like saying that Britney's Baby One could compete versus Beethoven's First Symphony.

      How could they compete?

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    2. Re:Windows and Mac OSX vs. Linux by Anonymous Coward · · Score: 0

      Huge chunks of OS X already are open source, idoit.

    3. Re:Windows and Mac OSX vs. Linux by Anonymous Coward · · Score: 0

      And other huge chunks aren't, moron.

  28. Maybe it will jump over the moon, maybe it won't by Nexus7 · · Score: 1

    So now eWeek has to lecture Linux developers on their priorities? Maybe all of the "threats" Linux faces that the author describes, are real ones, or even properly posed (pretty unlikely for an eWeek article), and maybe they aren't. But to frame the discussion like there's some monolith entity Linux that has to compete with OSX is to not eevn begin to understand where Linux came from, how and why it evolved, and who's behind it and why.

    And to argue from another direction, Linux's always had competition in the form of Windows. Maybe, just maybe, there's something about Linux that escapes the folks at eWeek.

  29. blah by macshit · · Score: 1

    I looked at the symphony os page, and while the guy has a few good ideas, I was disappointed to see he's yet another UI fascist, proclaiming that consistency of experience trumps user choice.

    It's one of gnome's most grating and annoying properties, that the developers have decided that user configurability is undesirable; since of course they are targetting the novice/clueless user, this means that gnome's interface sucks more and more for the experienced/clueful user, and at the same time they are reducing the user's ability to mitigate this through customization.

    It looks like symphony os is trying to follow the same limiting and moronic path.

    A user interface environment should be a toolkit with (1) really good defaults, and (2) tools that allow the user to easily mold it to fit his own usage patterns.

    --
    We live, as we dream -- alone....
    1. Re:blah by Jugalator · · Score: 1

      It's also interesting that while it at first sight has a good and clean design, it's surprisingly unergonomic. Putting one icon in each corner of the screen must be among the most stupid you can do as a UI designer. It's no coincidence Microsoft decided to even put "Shut Down" in the Start Menu -- it's because you're often already there with your mouse pointer when working with your computer.

      Same reason to why we often have Minimize, Maximize, and Close in the same place, and so on...

      --
      Beware: In C++, your friends can see your privates!
    2. Re:blah by Anonymous Coward · · Score: 0

      He's right -- and it's the reason why X Windows has had zero success as a mainstream GUI in 20 years of focusing on extreme configurability. And leaving too many decisions up to 3rd-party programmers leads to horrors like the ICCCM.

      There's a saying about the definition of insanity: continuing to do the same thing over and over when it obviously isn't working. Keep it up, guys! Windows and Mac will allow people to get work done while the Linux community is running genetic algorithm trials to find the best window manager.

    3. Re:blah by macshit · · Score: 1

      Same reason to why we often have Minimize, Maximize, and Close in the same place, and so on...

      This doesn't follow: I (and I think most people) rarely happen to have my mouse hovering near the window buttons. They are not near any other frequently used control, so the only reason I would is from multiple uses of these buttons, and since each button is used relatively rarely -- and morever dramatically changes the window geometry! -- it basically never happens.

      As placing these 3 buttons close together tends to cause annoying user accidents (hitting the close button inadvertantly when aiming for maximize), it seems really a fairly stupid arrangement. [It's completely bizarre that Apple decided to copy this layout from from MS for OSX, replacing their earlier more sane layout.]

      --
      We live, as we dream -- alone....
  30. But will you be able to use it everywhere? by Lonewolf666 · · Score: 1

    Or will the hardware support remain limited to Apple-specific hardware? An X86 CPU does not automatically mean support for the average PC.

    --
    C - the footgun of programming languages
  31. coral cache... by Anonymous Coward · · Score: 2, Informative

    Take it easy on the main server, here's the Coral cache...

    http://www.symphonyos.com.nyud.net:8090/

  32. Linux isn't the target by viniosity · · Score: 1
    I don't think the move by Apple to x86 has anything to do with linux at all. If Apple has shown one thing by using so many Open Source components it's that the Open Source community is a great counter balance to a monopoly. Should either side (MS or Apple) gain a lot of sway, the other side will be able to grab code from the Open source community and fire back. Therefore it's in everyone's interest to keep some open *nix alive.

    Both co.'s will be just fine with Linux as long as they retain market dominance and integrate the features users want first. The threat to them on the desktop will most likely come from Novell/Suse who are more aggressively pushing advanced tools like Beagle/Best. But the general linux community has nothing to fear. In fact, we can only hope that now that an Arch (PPC) has been (somewhat) taken out of play that resources will now choose to focus back on x86.

  33. Bollocks by m50d · · Score: 1

    This is just another divisive effort with the same goals as most of the major desktops. Why not focus on improving existing usability? Or even joining one of the other "new useable desktop from scratch" projects. Not that any of them are successful, and for a good reason.

    --
    I am trolling
  34. Competing? by JanneM · · Score: 1


    I'm not using Linux to "compete with Windows and OSX". I'm not helping out Gnome to make it more competitive. I'm using Linux and Gnome because it happens to fit the way I work very well and I help the Gnome project (by translating a bit, mostly) because it is enjoyable and I get to chat with some very fun people.

    --
    Trust the Computer. The Computer is your friend.
    1. Re:Competing? by Asic+Eng · · Score: 1
      I'm not using Linux to "compete with Windows and OSX".

      Which is your priviledge. However many others take a keen interest in Linux to compete with Windows because they feel strongly about the freedom of the users. So I think many readers on slashdot will be interested in this angle.

    2. Re:Competing? by Rikus · · Score: 1
      "...freedom of the users..."

      But if the users care enough about their own "freedom", they will probably prefer something like Linux over Mac OS X anyway. With Linux, they can figure out how it works, improve it, make it worse, redistribute it, etc. Mac OS X is something entirely different. If somebody decides that Mac OS X is better for the job, and they're okay with using that type of software, why should anyone care? Yes, having a large install-base is nice, both so you can claim big numbers and receive more bug reports and patches, but I don't think that OS X has much of a chance of "hurting" Linux, even if it is eventually released for use on regular non-Apple PC hardware. Those who would switch from Linux (or anything) to OS X as a result might just as well have switched to Windows or bought a Mac. Others like Linux (or whichever OS they use) for other reasons and probably have no real reason to switch, just because another big proprietary commercial OS is now at their disposal.

  35. Mac 924 Vs Microsoft Gremlin & Linux Minivan by NZheretic · · Score: 1
    Apple on Intel is like the original Porsche 924. Either it's a very bad marketing decision or a precursor to a play for a much larger chunk of the mainstream market...

    A long established sports car company Porsche, like Apple, use their unique design and reputation for performance and quality to set itself apart from other players in the same market.

    In 1976 Porsche released the Porsche 924 as an entry level introduction for new customers to the Porsche brand. The 924 may have been designed by Porsche, but it also had the same engine as models of the AMC Gremlin and Volkswagen Mini-van, and was built by Audi ( at that time it had just become a division of Volkswagen ). In comparison to other similarly priced sports cars of the day, the engine failed to deliver the expected performance, even with the addition of a turbo in 1979.

    Problems with the early model 924s really damaged the reputation of Porsche and most Porsche enthusiasts shunned it for the earlier model 911 series. Despite the loss of reputation, Porsche stuck with the 924 series for a few years. Sales were not as good as the 911 series and outsourcing the manufacturing turned out to be less cost effective than expected.

    Because IBM failed to deliver the next generation of Power CPUs, Apple is need of a new engine. Intel and AMD can provide one, but Apple does not have enough market share for either to manufacture custom CPUs or a new proprietary bus architecture. That leaves moving MacOS/X to the same ia64 or x86 processors which are also used in the Microsoft Gremlin and Linux Mini-van. The latter two OSs are quite capable of providing very comparable desktop experience to MacOS/X well within the next two years.

    There is not much Apple can do on the other side of processors bus which is going to deliver enough performance to set it apart from a new Laptop or PC from Dell, Lenovo, HP or any whitebox OEM. Apple style flashy external bodywork is being adopted by those same vendors. The inevitable comparisons will result in damage to the public's perception of Apple's uniqueness.

    This leaves Apple with a choice. Either continue to remain the sole supplier of hardware for MacOS/X and loose a large chunk of the desktop market share OR choose to directly compete with Microsoft and let Dell, Lenovo and HP sell Apple designed/approved "built for MacOS/X" laptops and PCs. The OEMs would love to have Apple and Microsoft competing to sell on the OEMs hardware.

    In my opinion if Apple does not choose the latter option, then it only because of very bad decisions by Apple's management or Sherman Act violating non-compete agreements with Microsoft.

  36. Forget the desktop... by Nooface · · Score: 2, Interesting

    Mobile devices are the future:

    Here are some market stats for the first quarter of 2005:

    Mobile Phone Handsets:
    170 million units sold (19% growth YTY)

    PCs:
    46.2 million units sold (11% growth YTY)

    iPods:
    5.3 million units sold (558% growth YTY)

    PDAs:
    3.4 million units sold (25% growth YTY)

    Video Games (Portable):
    3.8 million units sold (72% growth YTY)

    Volume rules...control mobile platforms, and the desktop comes for free. That's where Linux UI developers should focus their efforts.

    --

    Nooface
    In Search of the Post-PC Interface
    1. Re:Forget the desktop... by 110010001000 · · Score: 1

      This is exactly correct. The fact that you have been modded down as "offtopic" shows that the Linux users still don't get it. Mobile/embedded devices are going to drive the market. If you have a mobile OS that integrates nicely with your desktop/server OS then you are going to win.

      Microsoft knows this, which is why they are pouring money in Windows Mobile.

  37. How? by ampathee · · Score: 2, Insightful

    How will MacOS on intel threaten linux?

    It's not like you'll be able to install it on any old x86 box - you will still have to buy a Mac.

    It's just the internals of the black box that will change - the end user won't see any major difference (performance aside).

    I don't see how anyone deciding between linux or a mac would be influenced by this change.

  38. Depends on the hardware support by amigabill · · Score: 1

    Will Apple make OSX available for ANY x86 hardware? Will I be able to put it on my exiting PCs? Will I be able to choose my own motherboards and other parts for future upgrades?

    If so, then I may be tempted to go Mac and dump Linux when the Linux software I like gets ported. I think Linux will still thrive in the embedded systems and industrial controls, plus the occasional PDA markets.

    If not, then I think Linux will still thrive as it does now.

    Apple has always seemed very protective of its hardware. I imagine they will do something to keep control of things so we still have to buy Apple hardware to run MacOS, regardless of what CPU is in the thing.

  39. lol by qualico · · Score: 1

    How can Linux be threatened at the desktop when it does not exist there in any number to be begin with?

    The OS that wrestles the desktop from Microsoft's white knuckle grip will be the one that can run reliably, offer excellent security while being intuitive and efficient.
    Similar to how Firefox is wedging itself onto the desktop.

    With all that money and smarts, you would think Google cold come up with an OS.

  40. Intel/Mac will not affect Linux AT ALL. by Theovon · · Score: 1

    The switch from PPC to x86 for Apple is an issue only for Mac developers and maybe some of the users. No one else. A Mac is still a Mac, even when it's got an Intel processor in it. The only effect of going to x86 is that Apple won't fall behind on performance.

    The assumption seems to be that a Mac is somehow more attractive to developers with an Intel processor in it than with a PowerPC. Why!? What difference does it make? If you're developing for Linux and decide to also support the Mac, you still have to go through the same porting process to support OSX that you had to go through before. Sure, on those rare occasions when someone has some x86 assembly they would need to port, it helps, but otherwise, it's a non-issue.

    Porting to the Mac is porting to OSX. OSX is the same on both architectures. Apple switching to Intel doesn't make OSX any more like Linux.

  41. HELL, YESSSS!!! by Anonymous Coward · · Score: 0

    I feel treaten personally. I use Linux since 6 years now but now it's bye bye... I'll trash my whole system and install OSX on my Intel to catch up with the future. If that doesn't work I lost connection and have to kill myself with a hammer. Hope, CNN will show that so my life wasn't as worthless as Linux is right now.

    Christians suck for Jesus is dead since 2000 years now. Why isn't that a /. story?

    1. Re:HELL, YESSSS!!! by Anonymous Coward · · Score: 0

      When 2000 years old you are, remember you they will not.

  42. Symphony by 64nDh1 · · Score: 1
    After a brief look at this distro, which I've only just heard about, I'm intrigued. If it could run on a limited resources (96 MB RAM, 200 MHz Pentium II) I'd try it out.

    As regards dependency hell, could a user friendly system like Symphony use Gentoo's Portage system, or Fink? Seems even an idiot like myself can use simple commands to do complicated things like:

    # emerge --update --deep openoffice

    Or get a copy of the GIMP without worrying about GTK+ dependencies, or Azureus without getting the JRE with a separate instruction for download and compiling.

    After emerge you just have to track down the executable for the program after it's compiled. The compiling could even be hidden on a separate virtual desktop as an option to users who don't want to see things they don't understand.

    I know it's not as idiot-proof as Apple's .app system, which seems clean and quick, but it's in use already, and Gentoo already has a substantial software library at its site Gentoo.org, so much so that I know OS X users who wouldn't use the system without Fink - which is different but comparable.

    I see the case for considering this thread an advertisement, but if something is standards compliant and user friendly by design I think it's a good move for Linux spreading its market share. I think it's quite possible to give a good free system to new Linux users which is better and more fully featured than Lindows/Linspire, which I never liked despite the promise of Click'N'Run (CNR).

    1. Re:Symphony by ShyGuy91284 · · Score: 1

      Gentoo Portage != user friendly install system. It's easy, I'll give it that, but it's still source based, and that's why it has so much software available. There are a lot of Linux users who don't like to wait for software to compile, and I don't think mainstream would have any different opinion. (I use Gentoo, love portage, but know it's not quite for normal people).

      --
      In undeveloped countries, the consumer controls the market. In capitalist America, the market controls you.
    2. Re:Symphony by 64nDh1 · · Score: 1
      Cool, you're probably right. But I'm completely code ignorant. Barely have enough HTML for Slashdot, couldn't read a line of Java or C++. All portage requires is two commands, emerge and unmerge. Then you just wait and the program is installed. Like I said, if it was hidden (optionally) so you didn't see the compiling, your average user might just think "that took a while, but it worked, and I only typed one line!"

      I don't think Portage will separate from Gentoo in the near future, but I do think it'd be a good idea to integrate something very similar for the new Linux users. Give it a pretty GUI to keep you entertained, put every optional parameter as a clickable widget, and maybe integrate a game or distraction like a browser while you wait (I am, admittedly clutching at straws here) and I think people would use it. Needs good illustrated documentation too, but that'd be all it needs to work IMHO.

      //btw I hate myself for this post, I sound like someone in marketing trying to talk to someone in engineering. I promised myself I'd never be *that guy*

    3. Re:Symphony by redog · · Score: 1

      Portage is not limited to source only package mangagement.Nothing is preventing anyone from doing, say a: Bintoo(tm) binary system and manageing it with portage.

      Yes the portage tree provided by gentoo is mostly source based ebuilds.
      But it is most certianly user friendly.

      There is nothing stopping someone from building everypackage in the tree(think what every other distro is doing) and creating a portage tree with only the ebuilds to install these prebuilt binary packages(think apt-get).
      The fact that portage is so flexible and ebuilds so simple is why gentoo is popular.

      So your claim to fame as an abnormal person who uses gentoo isn't shaded by the fact that your wrong. Gentoo portage is user friendly. Building entire systems from source however is not pleasurable for most non portage fans.

    4. Re:Symphony by ShyGuy91284 · · Score: 1

      True. But the lack of needing compiled programs is part of why Portage is so vast compared to most other package management systems. Binary packages could easily be used, but then it wouldn't be so different from yum and other package management tools from what I've seen (although daily updates and eix/emerge --search do make it quite easy to use).

      --
      In undeveloped countries, the consumer controls the market. In capitalist America, the market controls you.
  43. it just occured to me.. by hyperstation · · Score: 1

    outside the realm of nerds, no one actually USES a linux desktop to any great extent. the people who do will probably continue doing so, since we're all pretty sure that os x won't run on commodity hardware (at least without hacking it up).

    so why is this even an issue?

  44. Darwin has been available for x86 by Sonicboom · · Score: 1

    Darwin - the CORE of OS X is open source and has been available on the x86 platform. Go Click here and see for yourself.

    x86 Darwin Release Notes

    --
    [Connection closed by foreign host]
  45. Linux vs OS X misconceptions by Port-0 · · Score: 2, Insightful

    Symphony looks nice.

    Because of the Apple news about switching to Intel chips, I've read a ton of articles stating that this is going to be the end of Linux, or Apple is now trying to compete with Dell or Microsoft directly. It is all a bunch of crap.

    Apple has stated that Mac OS X(x86) will only run on Apple Hardware. So, really the only thing this changes is that Apple will be able to put out better performing Macs in the future. There are competitive issues when comparing processor speed and architechure that will not be in the equation as much as before, but it doesn't change the business model for Apple, it doesn't change how people will use their hardware. It doesn't change who will buy their hardware. The competitive landscape remains unchanged. They are still built like an appliance, you plug it in and it just works. You may be able to run Windows on them, but why would you buy one for this purpose? It would be cheaper to buy a dell or something like that. If anything, it goes counter culture to the Mac zealots, but they will get over it once the realize, it still looks like a Mac, Sounds like a Mac, works like a Mac; it is still a Mac in the end.

    All this speculation is generated by a bunch of journalist, trying to make a buck off the sensationalism of it all. In the end a G4/5 and a x86 chip are designed for the same purpose, and can be used to accomplish the same thing.

    my 2 cents.

  46. Ok, I'll bite. by Weaselmancer · · Score: 2, Insightful

    The Linux Desktop Community must encourage such initatives massively to compete against Mac OSX and Windows.

    Why?

    Maybe I'm missing something and /. can enlighten me. I use Linux. OSX gets a lot of fans.

    So, exactly how does this involve me at all?

    I keep seeing that OSX might become a "threat". How exactly? Will OSX suddenly become self-aware and begin deleting Linux from the entire Internet or something?

    Maybe it's just me, but I just don't feel a threat here. They're both fairly posix/unix, so I'm reallly seeing a potential ally here more than anything else.

    --
    Weaselmancer
    rediculous.
  47. Good GUI Philosophy by anaesthetica · · Score: 1

    You can tell a GUI designer is going to be good when their "Laws of Interface Design" includes gems like this: "People are trained monkeys..."

    Yeah, this one's going to be a winner.

  48. I don't think Mac OS X is dangerous for Linux by Thijs+van+As · · Score: 1

    Why? Because with Linux it isn't just the OS itself. It's the whole ideology around it of a free (speech...) operating system. Whereas OS X is also a UNIX-like operating system it's a closed source system (not as much as Windows maybe, but still...).

    I think Mac OS X would maybe appeal to more people (in time), but until it isn't open source software Linux et al will exist I guess.

    BTW I'm both a Mac OS X and Linux user.

  49. osx tiger... by ohzero · · Score: 1

    is already superior to linux in nearly every way possible, so the short answer is... yes.

    --
    -- http://www.criticalassets.com
    1. Re:osx tiger... by Anonymous Coward · · Score: 0

      Well, OS X isn't free. It doesn't run on the hardware I want to run. And its user interface is a piece of inflexible crap.

  50. Why does processor make a difference? by guacamole · · Score: 2, Interesting

    Can someone explain me what makes MacOS X running on Intel-based Apple hardware any more of a threat to Linux compared to MacOS X running on PPC-based Apple hardware?

    Supposedly Intel processor makes Apple somehow better? What is it, speed? What else? But then, does this mean that the Linux community is filled with people who don't use MacOS X ONLY because Apple isn't making Intel-based Macs? I somehow find this to be hard to believe.

    1. Re:Why does processor make a difference? by nagora · · Score: 1
      Can someone explain me what makes MacOS X running on Intel-based Apple hardware any more of a threat to Linux compared to MacOS X running on PPC-based Apple hardware?

      I think the argument is that there are lots of Windows users who hate it (no argument there) but who won't make the jump to Mac because of the price/performance difference.

      Personally, I think that on price maybe there is an argument, but performance is not really an issue for 90% of the market, for whom 2GHz is plenty (850MHz is more than I use most of the time). The fact of the matter is that there is not enough software for Macs to make most people change. What there is is very good, but relatively little of it is exclusive. I still can't see any reason for the switch to Intel, especially when you look at AMD's chips.

      What was Steve thinking?

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    2. Re:Why does processor make a difference? by guacamole · · Score: 1

      I think the argument is that there are lots of Windows users who hate it (no argument there) but who won't make the jump to Mac because of the price/performance difference.

      Maybe, but how does that affect the Linux users? Do they use Linux as opposed to Mac OS X because of price/performance too? They might be disappointed when they find out that an Intel-based Mac is still more expensive than a comparable Dell or a build-your-own kit (which is not an unreasonable thing to assume about Apple pricing)

    3. Re:Why does processor make a difference? by nagora · · Score: 1
      Maybe, but how does that affect the Linux users?

      Because, the argument goes, the affordable alternative has up to now been Linux. Now, supposedly, Windows-haters that want an alternative might go to OSX instead. I don't buy it, it grossly underestimates the other reasons people use Macs, but that seems to be the thinking.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  51. Mac OS not on commodity hw by rkhalloran · · Score: 1

    Apple has said that Mac OS will *NOT* be available for off-the-shelf Wintel PCs; they'll be doing their own hardware as before, just with Intel CPUs. This could change downstream, but that's the party line at present.

    I'll concede that having an Intel-based Mac environment available *might* detract from Linux, but your hardware options (for now) are orders of magnitude greater under Linux than with Apple, and I can't see that changing anytime in the near future.

  52. *sigh* by Fahrvergnuugen · · Score: 1

    Why does Apple changing processors suddenly threaten linux? It makes no logical sense.

    --
    Kiteboarding Gear Mention slashdot and get 10% off!
    1. Re:*sigh* by Fahrvergnuugen · · Score: 1
      --
      Kiteboarding Gear Mention slashdot and get 10% off!
  53. No Threat by MightyMartian · · Score: 1

    The x86 version of OSX is not going to run on your garden variety PC. It isn't going to run on that old Pentium II 400 that you've decided to let your kids have. You're not going to be able to buy a Walmart PC and toss it on. It's going to continue to be on Apple hardware, and it is going to cost $$$. I don't see how there's any more threat from Macs in two years than there is now. The only people that may end up being screwed is users of PowerPC Linux, but that's a pretty damn small piece of the Linux market.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
  54. This is all a bunch of crap. by tom581 · · Score: 1

    Ever wonder how many of the chicken little's that are saying "Mac OS X will now be the death of Linux", are really microsloth weenies disguised as Mac OS X users?

  55. The easiest program to use... by Shotgun · · Score: 1

    is the one you already know.

    From the wikipedia:

    "the Mezzo desktop environment that poses a completely new way of presenting data to the user." [strike one]

    "Symphony OS also includes a new packaging system" [strike two]

    What may happen, is that some of the Mezzo ideas might get fed into other distributions, but whenever someone starts shouting about following a whole new paradigm they have lost from the start.

    --
    Aah, change is good. -- Rafiki
    Yeah, but it ain't easy. -- Simba
  56. A few things by grasshoppa · · Score: 2, Insightful

    1) We don't know how to do a desktop. If you want proof, look at what we've got so far.

    2) We don't *want* to do desktops. This, too, should be fairly obvious by the effort ( or lack thereof ) put forth up to this point.

    If OSX is a great desktop OS on commodity hardware ( it won't be, but that's the assumption at this point ), why should we spin our wheels coming up with yet another version of the wheel? The focus, I believe, should be server side. We should be making file/print and directory services under linux so damned impressive that no one would want to bother with the MS alternative.

    --
    Mod me down with all of your hatred and your journey towards the dark side will be complete!
  57. OS X breaks barriers for Linux by buckhead_buddy · · Score: 1

    Apple has said that Mac OS X will not run on generic x86 hardware. They've also said (perhaps not officially) that they will encourage x86 software use on their hardware (e.g. if the customer wants to install Windows in a dual boot or run via a virtual machine). This should be no threat to Apple. If someone's paid money to buy a Mac, they want to run Mac OS X. Having x86 compatability is a safety net for worried switchers.

    IF Apple's hardware is hacked to run on generic hardware (and I think that's a very big IF), we may actually see bigger demands for people wanting to buy generic hardware without an OS installed or perhaps with Lindows or other OEM free option installed. Admittedly most of these people will be the "crazy ones" who want to experiment, but that's a great user base that may also "discover" Linux in this process.

    Regardless of what headway Apple makes in the market, it's clear that they'll be calling into question the commercial judgement that there is only one computer operating system out there. That should make significant headway toward businesses considering the Linux options and demanding standards compliance in their apps and file formats.

    These situations give significant boost to Linux on the desktop in my opinion. The biggest problem is that Microsoft is a monopoly in the minds of the consumer and no amount of coding is going to change this. Linux will benefit from Mac OS X moving to x86 hardware, but that doesn't mean a new GUI has to be engineered by the debut of Mac OS X on Intel or the release of Longhorn. It would hurt to have some though (if that's what you're interested in hacking on).

  58. OSX and Gentoo user by FLAGGR · · Score: 1

    A year ago, I was a hardcore religous Gentoo user (yes, the worst kind of Linux zealot) I bought a mac mini because OSX looks cool, and if it sucks I can install gentoo.

    When it got here, there was that initial "WoW!" factor, didn't touch the PC for a few weeks. OSX became more and more unix. All the dev tools installed, X11 etc etc. Eventually I realized that anything I could do in gentoo I could do in OSX.

    I tried my best to treat gentoo fairly, and use it as much as possible, but it was slipping away. Why muck around in Konsole when I can play in Terminal, and have cooler drop shadows? OSX was fast, very fast. Think Windows, but not ugly, not slow, not buggy, and it's unix. It was like the awsome window manager that KDE Gnome and every other wm was aspiring to be.

    Now the PC has Slackware 10 installed, and my little brother and sister use it. I still support Linux in every way, but to me OSX is just Linux with a cooler window manager. Sure, it's no where near as open - I'll never compile everything from scratch - but I still get *nix, with pretty drop shadows.

    One of the reasons OSX excells is the exact opposite of why Linux rocks - customizability. OSX ain't got it. As far as apperance goes, you've got Aqua and Slate, which are the exact same thing except one has more grey. Developers know exactly what their app is going to look like on EVERY osx users computer. Everything feels right in that sense. Linux is cool though because KDE doesn't have a distinctive look. (Windows is in the middle, which makes it just crappy)

    Will OSX on x86 hurt Linux? Maybe. I bet alot of Linux zealots are saying it's all FUD and that Linux will never die because it's open source. Hopefully the KDE etc devs have taken notice, and are putting things into high gear. Competition spurs innovation.

    Sure, OSX may not run on your 200$ peice-of-shit Dell, but Apple said that it won't stop their machines from booting Windows, and they obviously can't stop Linux. Imagine turning on your machine, greeted by LILO Grub or whatever, and seeing this in the menu:

    Mac OSX
    Gentoo Linux
    FreeBSD
    Windows (sucks)

    All on one machine. That would be weird, but very cool. So in a way, Apples move to Intel affects Linux because even though alot may switch so they can dual boot linux and osx and windows and what-have-you, if OSX is far superior people may find themselves booting into Linux less often. (I would just get an 8GB ram machine and run them in virtualpc :) )

    So, some serious action needs to take place to make sure OSX doesn't canabalize it's *nix parents and relatives.

  59. Don't worry, Tux. by koi88 · · Score: 1

    My parent is right. There is no danger from Mac OS X.
    Both can benefit from each other, as the Apple Macintosh has benefited a lot from the UNIX-likeness of its OS X. Back in the times og Mac OS 7-9, there were very few ports of programs like Apache or things like that (and usually years behind other releases). I understand that these ports were very difficult to do. Now porting is much easier, and we get a lot more apps.
    So in the (bright) future, some of us will use Macs with Intel-proccessors, some will use Linux-boxes.
    I'm pretty sure Apple-computers will still be more expensive than PCs. And if you want something special (like systems with many processors or the latest hardware), you can run Linux on other processors or hardware. Or if you want a huge choice of user interfaces.
    So there are still plenty of reasons to use Linux.
    But maybe a few programs for OS X will be ported to Linux, maybe Photoshop, Illustrator or whatever, as porting in both directions should be easier.

    Of course, some people might still use that other OS from Redmond.

    --

    I don't need a signature.
  60. Re:Because by symbolic · · Score: 1


    Choice. You may think this is a bad thing, but I run KDE on one linux box, and Gnome on the other. I like certain aspects of both. There are certain aspects of both that irritate me. However, at the end of the day, I like having the choice to use what works best for me, rather than leaving this up to a single effort, and leaving me stuck with it whether I like it or not.

  61. Short answer : no by ElGanzoLoco · · Score: 1


    Short answer : not as long as Apple keeps Mac OS X on its own machines, be they PPC-based or intel-based. For the moment, the plan is to replace IBM chips with intel chips on Apple-produced Macs (likely to remain as expensive as now), not to unleash Mac OS X on an unsuspecting Wintel world.

    --

    Longer answer: if Apple decides to make OS X for every PC out there, they will be in competition with Windows, not Linux. Apple will tout OS X's ease of use - prettiness - multimedia capabilities, and this will speak to frustrated windows users, not linux users. (There aren't many people using linux as "general-use" machines)

    Linux is here to stay : most linux users don't use it because it's prettier or easier to use than Windows : it's not. They use it because of access to the sources, shell, easy scripting, performance, stability, etc.. These are perfectly valid reasons to use linux on production machines (servers - development - science). Mac OS X Server might compete here, but it's costly compared to linux.

    --
    Hello! I'm a disaster waiting to happen!
  62. No. by Aldric · · Score: 2, Insightful

    Just like it didn't threaten Linux yesterday.

  63. Terrasoft by zogger · · Score: 1
  64. we really did it this time... by karn096 · · Score: 1

    I think we slashdotted coral cache

    Error: 503 Service Unavailable

    www.symphonyos.com: Too many open files

    Server CoralWebPrx/0.1.14 (See http://coralcdn.org/) at 140.112.107.80:8090

  65. Do Linux enthusiasts... by Cinquero · · Score: 1

    ... really want bloody lamers complaining about all and everything they are too dumb to do under Linux?

    The rule of thumb for Linux users is:

    if it is not there: just do it yourself. Mac users ain't quite that sort of people.

  66. Polemic by BarryNorton · · Score: 1

    To the author: If you're going to attempt a polemic, at least learn to speak English!

    To the editors: Is this news?..

  67. Welcome to Slashdot! by NRAdude · · Score: 0
    I totally agree with this statement, why not make one graphics layer for all applications like Mac OS X, instead of GTK, GTK2, QT, etc, etc.


    Say, that's a great idea! I hope you borrow the best features from each one, mangle it together, and call it GQTK2++. Sure, you're bound to be flamed to support all those pesky architectures, resulting in various code-branching, then after two years all your once-jedi buddies would break-away because they think you've lost your edge, but then it'll all implode when GTK and Mac OSX and whatever other mimicry assimilated inyou your project will be uber-created in your competitors biggest product. Then someone with the same spirit you once had those five years earlier will come along and complain abouth the uber-creator's software, and he'll create his own and open it to all the geeks of Poor kingdom under the title "GuhnooberOeSS-eXP++--." I'm behind you, man! So far behind that you can't see me yet, but I'm behind you! It'll be free, as in beer, right?
    --
    without prejudice
  68. Nothing is a threat to 'Linux' by Anonymous Coward · · Score: 0

    Linux is a kernel. An operating system can not threaten a kernel, neither can a software product other than a kernel. There is no threat to Linux.

    'The Linux Desktop' also has nothing to fear. First of all it is Open Source and Free while all the competition (save the BSDs, though I don't know if they could be classified Free Software?) is neither Open nor Free. Not to mention the user base of Linux doesn't shrink just because Mac OS becomes popular.

    Linux sprung out into what it is today -solely- due to the investment by developers, NOT a company with funding trying to make a product for end-users. Sure companies have been paying developers full time to work on Linux but the same work would have been done without them. The only real contributions companies make are proprietary code they open source which the developers could come up with too if they chose to. The developers made it for themselves and until Mac OS becomes even a slightly decent development platform, Linux developers will never abandon their loved one and Linux and its free Desktop software will never be threatened.

    Might I remind you Linux's strength also lies in its use as a console, not just a graphical user interface? And its grip on the server market is undeniable. Even if Linux was banished to mostly-server markets the Desktop software will always be there for you to use or not; whether or not Red Hat goes out of business i'll always have my Slackware or Debian or LFS desktop/server system.

  69. Couldn't agree more by johansalk · · Score: 1

    Yesterday I tried the latest knoppix version, and what struck me the most was how ugly kde is. The mother of heirarchial menues made even worse by most applications starting with a K(!), therefore making alphabetical sorting near useless. Just looking at it irritated me. The KDE project seems to have taken the worst of windows, fashioned it after apple of yesteryears, and maxed out on it. I really think the linux should've just made their own desktop, the way it ought better be, and let windows familiarity be damned. Linux should be about what's next, not what microsoft was.

  70. Re: Tempted to agree by symbolic · · Score: 1


    People seem to be forgetting that OSX is still a proprietary OS, and it will *still* will only run on Macs, albeit with an '86 processor instead of a PPC. So what's all the fuss about? The only thing changing here is the processor that Apple will be using for its future Macs.

  71. The main reason... by artemis67 · · Score: 1

    that Apple won't threaten Linux on the desktop is that you still have to buy a proprietary box to run OS X x86.

    If/when Apple wakes up to the fact that they just invaded the other 97% of the market, and that they could possibly make up for the lost hardware revenue by selling shrink-wrapped OS X copies in volume, then they might be a threat to Linux.

    Until that day, Apple is going to continue to sell premium-priced hardware that won't appeal to the average Linux geek.

  72. Not being a Mac user, nor a Linux user... by HerculesMO · · Score: 1

    I don't see why Apple doesn't just let the OpenSource community get in on the development of OS X. I mean, they accomplish two goals, first, making Linux a widely accepted form of OS as well as pushing Apple as a whole into a Windows market. It's easier for me as a Windows user to accept a Mac OS rather than Linux with KDE or Gnome.

    But that's just me.

    --
    The price is always right if someone else is paying.
  73. Apple's HID Guidelines by Krieger · · Score: 1

    Strangely enough one of the best opportunities for Linux would be to take Apple's Human Interface Development Guidelines and apply them to Linux. Apple has done and did some of the best research on how people use computers and what's intuitive. By taking and leveraging those ideas, linux desktops could get a lot closer to useable.

    This opportunity is even more stark since Apple has been abandoning these self-same guidelines in their more recent versions of the Mac OS. The finder is no longer compliant with these guidelines, it's clunky and counter-intuitive. But I'm sure if you care about apple you either have, or have read about the complaints about the finder.

    Linux would do well to learn from Apple's research. GNOME and KDE are great steps for anyone programming for Linux. By using their development environments we get much closer to having a common theme we can follow, a common expectation of where to find menus, etc. These are vital components to being able to use an OS. The current batch of programs still don't have that rock solid consistency. You often still have to search for the options you need.

  74. Threaten Linux? No by alucinor · · Score: 1

    Apple's move to Intel is not going to threaten Linux; it will actually help Linux. The free operating systems thrive on standards, and where there is more diversity in computing, standards become more neccessary.

    I want Apple to slug it out Microsoft; that's the way it should be. Linux? Let Linux just keep sliding into the cracks as ever; the slow steady rise.

    "Linux" itself could never compete against Microsoft anyhow; it would have to be a Linux-weilding company. And while the Linux desktop will definitely make inroads soon overseas and within corporations, I don't see any of the distros having a "cool" and/or "friendly" consumer image on par with Apple or even -- ack -- Microsoft, any time soon.

    But give it about 10 years, and in all those places Linux has trickled in, the cracks will have expanded quite wide. We've just got to keep working, and be patient.

    After all, who uses Kleenex brand tissues anymore? Who uses Q-tip brand cotton swabs? Linux is the generica of operating systems. It's inevitable, but not quite here yet.

    --
    random underscore blankspace at ya know hoo dot comedy.
  75. AppleNT? by Shrapn3l · · Score: 0, Troll

    Let's discuss security a moment. If I remember correctly, Apple would be moving its OS to Intel and basing that OS around the Windows NT kernel. And if I remember correctly, the Windows NT kernel is monolithic in design, meaning that it is irreducably complex. Everything interacts with everything, meaning that if one component fails, or is compromised, it can lead to a system failure or system compromization. If the above is true, then I strongly disagree with the wisdom of Apple's decision, no matter what the motivation may be. And this may give hope to Linux, because if the above is true, all we'll be seeing is another Windows kernel on the market. Not a problem at all. Let me know what flaws you see in my logic. Thanks.

    --
    That that is, is.
    1. Re:AppleNT? by amliebsch · · Score: 1
      The flaw with your logic is that your premises are exactly wrong.

      If I remember correctly, Apple would be moving its OS to Intel and basing that OS around the Windows NT kernel.

      No, they're using the same Mach kernel as always.

      And if I remember correctly, the Windows NT kernel is monolithic in design, meaning that it is irreducably complex.

      No, NT is a microkernel. Linux uses a monolithic kernel.

      --
      If you don't know where you are going, you will wind up somewhere else.
  76. Linux to Apple, No Fear by Anonymous Coward · · Score: 0

    Linux Has No Fear This news does nothing to Linux at the moment. Probably never will. If anything, some Mac applications may spill over into Linux, like, Adobe Photoshop. Some Linux applications may spill over onto the Mac, such as engineering design software (EDA, CAD, etc). If you remove emotions and OS religion from the equation, this could be a win-win for Apple and Linux. Linux is more compatible with an Intel Mac than Windows will ever be. Porting applications between Mac and Linux should be easier than porting to Apple's xcode then to OS X. If a Linux user wants the Mac look and feel, there is an Aqua clone for KDE.

    Linux to Apple, No Fear

  77. Stupid Subject... by grumbel · · Score: 1

    Come on, how should Apple threaten Linux? If MacOSX would run on all x86 hardware and would be 100% Windows compatible there might be some reason behind this, but for all we now, MacOSX will still require its special hardware and don't offer any build in Windows compatibilty, so things havn't really changed at all from the PPC. Its all just a implementation detail that nobody really cares about.

    Biggest thread for Linux always was and always will be itself. To many incompabile distros, no consistency, lack of user friendlyness when it comes to hardware install, configuration, software installation, lack of third party support, etc.

  78. Linus Uses a Mac by SenFo · · Score: 1

    A friend of mine brought up an interesting point the other day that got me thinking about Linus' switch to a Mac. He brought up the point that it's possible that Mac could possibly be interested in switching to the Linux kernel. That being the case, Mac wouldn't be a threat to Linux, at all. They could quite possibly be the biggest ally to date!

    1. Re:Linus Uses a Mac by DrunkenPenguin · · Score: 1

      Linus uses a Mac? Yes, he does, but he doesn't run OS-X on it. He's running Linux on it.

    2. Re:Linus Uses a Mac by Shrapn3l · · Score: 1

      Can you really run Linux on a Mac?

      --
      That that is, is.
    3. Re:Linus Uses a Mac by Anonymous Coward · · Score: 0

      Yes. You probably won't find it listed as Mac, but a lot of distros have a PPC version, which runs on current Apple hardware. Ubuntu certainally does, as does Debian, and then of course there's PPC-specific distros like Yellow Dog.

    4. Re:Linus Uses a Mac by SenFo · · Score: 1

      "Linus uses a Mac? Yes, he does, but he doesn't run OS-X on it. He's running Linux on it."

      That's a fair argument. However, I have to wonder what made Linus switch to a completely different architecture. He's often quoted with negative remarks regarding Intel products (though I don't actually think he "dislikes" Intel, per sey). But there's still AMD. At first glance, I can't think of any one reason why he would use a Mac if he knew ahead of time that they were switching to Intel. However, I believe there's a possibility of something more than meets the eye.

    5. Re:Linus Uses a Mac by Anonymous Coward · · Score: 0

      When running a Unix system and compiling things from source, it doesn't really make a big difference what CPU the machine is using.

      A much bigger difference is what graphics and audio chipsets the machine is using, and how well drivers support those.

    6. Re:Linus Uses a Mac by Anonymous Coward · · Score: 0

      Actually it isn't that complicated - he was given it for free.

    7. Re:Linus Uses a Mac by SenFo · · Score: 1

      "Actually it isn't that complicated - he was given it for free."

      Well that just changes everything now, doesn't it ;-). Oh well...A guy can dream, can't he!

  79. Um... by rdunnell · · Score: 1

    Apple isn't moving anything to a NT kernel. OS X would keep its Mach kernel etc.

    I think your views on the risks of monolithic vs. microkernel might be a bit extreme as well but hey, everyone gets their own opinion. But it's more than possible to cause a systemwide failure in a system that isn't monolithic.

    1. Re:Um... by Shrapn3l · · Score: 1

      I'm sorry, I was mistaken. I must have read a misleading article. :)

      Thanks for letting me know.

      --
      That that is, is.
    2. Re:Um... by dick+johnson · · Score: 1

      Actually, Apple considered using PowerPC NT as the basis for its next generation OS before they ultimately switched to NextStep. But of course, that was years and years ago.

      --
      - dj
  80. I missed a part of Job's speech by epine · · Score: 0, Flamebait


    The part where he says he's going to make OS/X free as in "free beer" because his cold little heart bleeds when he reads that BSD is dying.

    People put way too much importance on visibility. I don't know if Linux was ever destined to count itself among the most visible of all platforms. Linux doesn't need that kind of one-on-one attention to fill important niches. I'd be quite happy to see a three way tie take shape: MS for the corporate drones, OS/X for the insecure, and Linux/BSD for those of us who merely want to get from point A to point B without the hype and fanfare.

    It takes a certain amount of insecurity to wonder about this prospect in the first place.

  81. Beautiful?! by Lysol · · Score: 1

    Hardly. Two strikes against it in my book.

    * Horrible non-aa fonts - this is 10+ year old tech!
    * KDE leftover Aqua wannabe icons

    Yuk.

  82. Competition? Eh, whot? by Anonymous Coward · · Score: 0

    There is no competition. Linux on the desktop is a tiny little geek niche and will not go away. If anything, people will be dual-booting Linux on their x86 Powerbooks, because it's going to be that much easier.

    This is *good* for Linux.

    And bad for Dell. But that's another topic entirely.

  83. Threaten how? by solios · · Score: 4, Insightful

    Everybody I know who's a linux user but wants a useable desktop they don't have to mess with has already bought a Mac and "switched" to OS X. They still use linux, but the machines are either console-only or headless.

    Of the dozen or so people I know who've "switched", they've all been linux or *bsd users, and they switched because Apple provides a useable desktop experience that Just Works Out Of The Box.

    Of course, these are people with lives who don't like plinking around with their computers just for the hell of it - they use the things to Do Work.

    1. Re:Threaten how? by MustardMan · · Score: 1

      EXACTLY! As a physics grad student doing computational work, I'm surrounded by linux people, and in fact use linux quite a bit in my work. I dump code off to knoppix clusters to crunch numbers, and I used to run linux as my primary desktop.

      Then, my advisor bought us all ibooks, so we could work on our code at home. It's been a pure dream to have a laptop that runs something unix-y and everything just plain works, without recompiling the kernel to get the power management functionality I want, or tweaking an X config file to get the screen setup I want.

      Now I've bought a dual g5 powermac to use at home. Once I started using os X, I came to such a huge appreciation of having a unix command line and all the tools built into a system with a damn slick user interface, most linux software available, and most importantly a simple way to configure most things. When I started, I was doing all my work in emacs running under KDE on Xdarwin. Nowadays, I'm using xcode and loving it. All my friends are calling me a traitor, saying I'm not a real geek anymore, even calling me a mac zealot.

      I tell them I'd rather spend more of my time at work actually working, so I get finished sooner, and can get home in time to go outside and BBQ some bugers before bed.

    2. Re:Threaten how? by DaleNixon · · Score: 0

      BBQ some bugers before bed. You want some snot with that?

      --
      How long is YOUR e-penis?
    3. Re:Threaten how? by poot_rootbeer · · Score: 1

      Everybody I know who's a linux user but wants a useable desktop they don't have to mess with has already bought a Mac and "switched" to OS X.

      Which demonstrates that among that type of user, Apple's switch to x86 isn't the threat to Linux; OS X itself is, regardless of the CPU it runs on.

    4. Re:Threaten how? by solios · · Score: 1

      It isn't a threat so much as a big huge neon sign as to how Linux On The Desktop is a complete failure (or just plain incomplete) for the vast majority of non-hobbyists.

  84. Beautiful Mirror by oscartheduck · · Score: 0

    Here's the mirrordot mirror of the symphony OS page.

    --
    How to use coral cache: http://slashdot.org.nyud.net:8090/~oscartheduck
  85. How OSX on x86 and Linux could help each other: by daemonc · · Score: 3, Insightful

    First of all, I doubt that OSX, evens if it runs on commodity x86 hardware, will seriously decrease Linux's marketshare. Linux enthusiasts and Free Software advocates are not suddenly going to switch over to a new proprietary OS just because it's available. (Raging anti-Microsoft zealots might though, but that's a segment of the population I think we can do without.)

    However, this is a unquie opportunity for the Linux community and Apple to help one another and both gain a big chunk of Microsoft's userbase.

    Imagine if Apple started contributing funds and/or developers to the Wine project, basically doing for Wine what they did for Khtml.

    Imagine being able to tell someone that, yes, they can switch to Linux/OSX and still run all their Windows programs/games.

    Imagine what that would do for the marketshare of both operating systems.

    --
    All that we see or seem is but a dream within a dream.
    1. Re:How OSX on x86 and Linux could help each other: by megalomang · · Score: 2, Insightful

      Raging anti-Microsoft zealots might though, but that's a segment of the population I think we can do without

      Perhaps Mr. Torvalds is no anti-Microsoft zealot. But you can't say the same about many of the early leaders of the Free software world.

      In particular, Richard Stallman, who is largely responsible for gcc, emacs, binary tools, the FSF foundation, the GPL license. He is even (arguably) largely responsible for the success of Linux in general. Yet he is incredibly anti-Microsoft and very well criticized. Granted he is not one of the zealots that are linux-illiterate, and so he will not be converting to osx any time soon.

      But to answer your assertion above, no, I don't think the Linux community could have flourished without that segment of the population.

      Perhaps you are new to the free software movement, and so I forgive you.

    2. Re:How OSX on x86 and Linux could help each other: by xeno-cat · · Score: 1

      From what I gather RMS is not anti-Microsoft but anti-propreitary software licenses. MS is a big propreitary software development company but if they switched to Free software then I doubt RMS would still hate them because they are MS.

      Now anti-MS zealots _would_ still hate MS because of all there bugy software, viruses, personal affronts, etc. etc. etc.

      RMS has got to be one of the most misunderstood public figures I know.

      Kind Regards

      --
      "A few great minds are enough to endow humanity with monstrous power, but a few great hearts are not enough to make us w
    3. Re:How OSX on x86 and Linux could help each other: by lar3ry · · Score: 1

      Well, being a long time Linux user, I can say that I've already switched my main workstation to OS X.

      Why?

      Graphics on that platform are nothing short of amazing. Important Linux applications are already available for OS X as native apps... Audacity, OpenOffice (as NeoOffice/J), Firefox, and Thunderbird come immediately to mind. Gimp runs under X, but the latest version of X runs almost like a native application.

      In addition to the open source applications, I now also have GarageBand, iPhoto, iTunes, iMovie, iDVD, Mail.app and all those other iLife applications that Apple bundles with the Mini and Tiger that are not available for Linux or Windows.

      Last month, I had $500 to spend on a new box. I could have purchased an x86/AMD motherboard, case, RAM, and other stuff and then installed Linux. For the same amount of money, I purchased a Mini which came with Tiger (I did have to "upgrade" from Panther to Tiger, but that wasn't difficult at all).

      If my kids HAVE to have Office--and NeoOffice/J just won't suffice--then I can just purchase Microsoft's version for the Mac. I can't do that with Linux! If my kids HAVE to have Photoshop or Illustrator or any of the other mainstream apps, then they are more likely to have Mac versions than Linux versions.

      OS X on the x86 platform will be great! If will definitely require special hardware to run properly, but I cannot see why Apple won't sell a version of OS X that runs on generic PC's, albeit with performance issues. That's money to them and there's a big market already out there! Since Apple is also a hardware company, there's no reason that Apple cannot sell hardware that's especially "tuned" for--and bundled with--Mac OS X, and still find a ready audience.

      How much would a Mini cost today if it used the more available x86 chipset components rather than PowerPC? I think it would be cheaper, and Apple could still make money.

      I can easily imagine a $399 x86-based Mini complete with OS X running at 2.5-3.5 Ghz. If that's possible, then what would be the incentive to roll your own machine? Apple's a major player and could supply such a machine to any school, student, home user, or corporation that wants one... or one hundred?

      I don't see Apple gunning for Linux right now; they're looking for mind share--from existing Mac users and existing PC users who are curious. If Windows and OS X are both available for your next purchase, people will make their decision based on what else runs on the OS. Microsoft can continue to make their Office and Works applications available as software add-ons to OEMs, and Apple will do the same with its own hardware, bundling AppleWorks, iLife, and perhaps iWork. Microsoft has a head start on compatible applications, but as the new guy in town, Apple has no direction to go but up.

      Relatively few people purchase systems bundled with Linux installed on them, and that is unlikely to change anytime soon. Linux won't suffer at all in the short run--the same people installing it today because of its perceived cost/benefit proposition will continue doing so tomorrow. OS X/86 will probably appeal to a few of those people, especially if it's available for generic systems. If not, there will still be some that will switch if the price is right, if only to satisfy their curiosity about what all the fuss is about.

      Linux is still superior to Windows as a server system, and Apple doesn't seem to be pushing their Mac platform to appeal to people buying such systems. Eventually, though, if OS X/86 catches on, people will notice that it's not limited to just workstation chores. Despite that, Linux can still continue to advance and stay ahead in this direction if it wants, provided people continue improving its capabilities.

      So... Good luck, Apple--and long live Linux!

      --
      "May I have ten thousand marbles, please?"
    4. Re:How OSX on x86 and Linux could help each other: by megalomang · · Score: 1

      Thank you for clarifying that. He is definitely anti-software-restriction more than anything else.

      In a way, he might even appreciate Microsoft for helping inspire so many to develop free apps (for both linux and win32). :)

      I have a lot of respect for the man and what he has done. When I was in my early 20s about 10 years ago, he sent me an email which I still have saved somewhere. I was truly in awe that he was humble and generous enough to respond to my newbie post.

    5. Re:How OSX on x86 and Linux could help each other: by Enrique1218 · · Score: 1

      Imagine if Apple started contributing funds and/or developers to the Wine project, basically doing for Wine what they did for Khtml.

      Sounds great except it may induce mac developers to stop developing native version of their software. Why bother making one for OSX if the Windows version of the software will run on OSX? Mac user lose software that comply to Apples user interface guidelines. They will lose a fundamental reason for using OSX over Windows. At that point, Mac users have no inclination to use Mac OSX. After that, Apple will not have any inclination to make Mac OS X and they become another Microsoft OEM. I worry Microsoft may elect to just develop Virtual PC that will run Windows software at native speeds and drop development of Mac Office all together. Then, Adobe and other will follow suit and then there will be no need for Mac OSX. Thus, I don't want to see any emulators on Mac OSX, though I know its inevitable.

      --
      You don't have to be smart to use a Mac, you just have to be smart enough to buy one
  86. It is beautiful, but kinda misleading as well by zanderredux · · Score: 1
    Their UI concept is bound to be incomplete until they get that same concept into the applications themselves.

    See, their desktop UI solution does not span into applications. Mozilla continues to have menus, submenus. So does OOo. The old way of doing things -- including those tricky context menus, which are completely counter-intuitive -- are not gone. They just aren't used in the desktop layer.

    However, I applaud their artistic skills. There's a lot of well-round and tasteful SVGs in the screenshots, they get proportion and design right.

    Most programmers aren't able to do that. See the visual hell that is KDE, with bouncing cursors and generalized visual information overflow. Worse, they have those small, 2 sq-pixel thingies to click to get additional functionality, which are absolutely cruel to the user -- user interfaces should feel good not only to one's eyes and brains (i.e., look good and make sense), but to their arms and wrists as well (does not worsen user's physical limitations). KDE guys have a design that values clutter and über-geeky-coolness that is hermetic to their own userbase.

    Getting back to the subject at hand, it's a shame that Symphony devs cannot play along with other distros. In the other hand, I just hope their experience serves as inspiration for other teams, so that they can design better interfaces.

    1. Re:It is beautiful, but kinda misleading as well by TuringTest · · Score: 1

      Symphony is in alpha state, so it's too soon to say how it will evolve. The desktop UI *will* span into applications thanks to the underlying Opera environment (which leverages the Mozilla XUL architecture toghether with Perl scripting).

      The Symphony staff have proven that they have a clue both on technical and UI design grounds. I hope that this distro will evolve into the definite User Friendly Linux if they manage to get it done.

      --
      Singularity: a belief in the "God" idea with the "demiurge" relation inverted.
  87. MSFT? by Bruce+Perens · · Score: 1
    Why are you sucking up to MSFT

    Dear AC,

    I am in business with a number of people who quit working for Microsoft. I must assume that they quit for some reason, and that they don't carry some enduring Microsoft religion with them to their new jobs. If I were to find that this is really some attempt to have Bill Gates pull my puppet strings, of course I would quit. But this seems rather unlikely.

    Bruce

    1. Re:MSFT? by Anonymous Coward · · Score: 0

      Different AC, but also a question on your new Sourcelabs job:

      Why promote *AMP instead of LAMP?

      By all means promote other software but why not focus on the most likely combinations? That way you get to 'enterprise-readiness' quicker.

      PS Asterisk might be a good early choice too.

    2. Re:MSFT? by Bruce+Perens · · Score: 1
      Why promote *AMP instead of LAMP?

      Because they don't believe it's necessary for them to go into competition with Linux distributions. There is, however, virtue in having one finger to point to. No doubt the business strategy will evolve over time.

      Bruce

    3. Re:MSFT? by Bruce+Perens · · Score: 1

      One finger to point to. :-) Garble. I mean one party to point your finger to.

    4. Re:MSFT? by Anonymous Coward · · Score: 0

      Their statement about 'Who is Bruce Perens' doesn't seem to understand the difference between open source and free software. Their website is full of Dilbert-esque mission statements, without any case studies.

      To top things off, Sourcelabs seem to be promoting AMP on Windows!

      I would like to say "I know you've thought this through, so I'll give you the benefit of the doubt" but you didn't even know what Brad did until today!

      I'm not particularly happy that your name/reputation is being leveraged for this, and I think this whole adventure is ill-advised.

    5. Re:MSFT? by Bruce+Perens · · Score: 1
      Currently they support AMP on Red Hat. Windows is a future product. What, you don't want Open Source to make inroads on Windows platforms? What better way to win those folks over? Better tell the Mozilla and Apache projects you don't like what they are doing.

      Sorry about mis-stating Brad's former occupation. The ex-CFO of MS is there, and I did confuse two statements about him with Brad.

      Open Source and Free Software are two different means of marketing the same thing. When I wrote the Debian Free Software Guidelines, Stallman said it was a good definition of Free Software. That document became the Open Source Definition. It's unfortunate that ESR felt that the Open Source campaign had to deprecate Stallman. That was not my intention and I've always been bothered that it happened.

      Bruce

    6. Re:MSFT? by Anonymous Coward · · Score: 0

      AMP are server technologies which live naturally on *nix servers.

      Desktop apps should be cross-platform.

      Server apps should be cross-platform only to enable trials and demos. Anyone using AMP on Windows for serious 'enterprise' work needs to ask themselves why.

    7. Re:MSFT? by Dan+D. · · Score: 1

      Ha! I thought that was a clever way to verbally flip the guy off. :)

      --
      People who quote themselves bug the crap out of me -- Me.
  88. Must. resist. temptation. by NRAdude · · Score: 1, Funny


    Interesting. An advertisment, disguised as an Apple article, disguised as a Linux topic. Interesting.
    ... and a dupe on top of that.

    We discussed this earlier this week when Dvorak trie d to piss on everyone's parade with the same opinion.

    It was BS then. Its BS now. All Apple on x86 does is give street cred to the idea of switching away from the Bitch from Redmond. Eveeryone else benefits at that point.

    In other news - the sun shines, the earth rotetes, life goes on.


    There! Now I've mastered the blockquoted blockquote and duped a most-likely duped post complaining of a duplication of an already duped article disguised to advertise duplicating of Apple OSX on IBM duped PeeSees. Those Intel people are just a bunch of clones.
    --
    without prejudice
    1. Re:Must. resist. temptation. by tomhudson · · Score: 1
      It's good. Now go for the bonus round: include at least one of the following -
      1. an obfuscated link to tubgirl or goat.cx
      2. some GNAA stuff
      3. ascii artwork - just cut-n-paste from trolltalk
      4. Some soviet russia old korean natalie portman does you joke
      5. Claiming you work(ed) on it/knew someone who worked on it for the last 5 years at Apple, and pulled some factoids out of thin air, like Dvorak does.
      You can either:
      [ ] Dupe your dupe post in the current thread
      [ ] Dupe your dupe post in the dupe article later today
      [ ] Dupe your dupe post in the dupe story referncing this dupe on Friday
      [ ] All of the above
      Honestly, I don't know why everyone has got their underwear so caught up in a bunch over this. You can still buy a Mini Mac on the cheap, complete with OS ...

      I think the REALLY interesting part, and nobody's touched on it yet, is that Apple kept a secret for 5 years. Kind of lends credence to the claims that the other product leaks were intentional.

  89. Not BUNDLED with hardware.... by Jerry · · Score: 1

    If you check out the price of naked PCs and toss in a free Debian clone like SimplyMEPIS you have a powerful GUI Desktop with a powerful package management system called Synaptics. The combined price of equally capable hardware plus MEPIS is MUCH less than that of an Apple computer with Tiger, and that is not including the additional proprietary (EXPENSIVE) software you'd have to purchase for Apple to do anything.

    If Apple dropped the hardware they'd have to compete with Windows for a space on Dell's desktops. THEN they'd learn the real meaning of the power of a ruthless monopoly. As long as Bush and money-grubbing politicians are in power don't expect the M$ monopoly to disappear anytime soon.

    Need further proof? Just watch the EU resistance to the Microsoft envasion fade away as various politicians receive liberal campaign dontation$, promises of construction and jobs in their regions, etc.... Or, conversely, the threat of plant closings and job losses (which has already happened - google it) if they don't get on board with M$'s "interpretation" of patents and copyrights.

    --

    Running with Linux for over 20 years!

  90. How can ANYTHING "threaten" Linux? by The+Dodger · · Score: 5, Insightful

    Q: "Could Apple's Intel Desktop Threaten Linux?"
    A: No.

    The concept of Apple-on-Intel threatening Linux might be valid if Linux was a commercial operating system, sold by a company whose market share and profits might suffer if Apple were to compete successfully against them.

    But it isn't.

    You can't threaten Linux. If Red Hat and all the other Linux companies were to drop Linux and switch to something else, if Dell, IBM and all the other box suppliers stopped supporting Linux, if all the hardware manufacturers who currently provide Linux drivers for their products all stopped supporting Linux, it still wouldn't be dead. You'd still have people like Torvalds and Cox writing code in their spare time and there'd still be geeks downloading Linux and installing it on old PCs.

    Giving people an alternative to Linux isn't a threat - it's a choice. It's freedom of choice and freedom is what Linux is all about.

    More and more, we see articles and talk about Linux's market share, whether it's going to be successful on the desktop, whether it's going to be able to compete against Windows, against Solaris, et cetera, et cetera, et ad infinitum cetera.

    Linux doesn't compete against Windows, MacOS X or Solaris. Linux vendors, like Red Hat, compete against Microsoft, Apple and Sun. Linux just is. The fact that it's supported by various companies is great but it's not essential for Linux survival. The fact that the amount of people and companies using Linux is huge and growing is terrific, but it's not essential. If everyone, right up to and including Linus abandoned Linux, I'd still be able to dig out my Red Hat CDs and install it on an old PC.

    This article is just typical of /. these days - it's a stupid, hype-ridden question, which hundreds of clueless fuckwits will comment inanely on, wasting bandwidth and electrons.

    Wake up and take your heads out of your asses.


    D.
    ..is for Don't. Be so. Fucking. Stupid.

    1. Re:How can ANYTHING "threaten" Linux? by 110010001000 · · Score: 1

      You are wrong. If Linux loses mindshare you will see the development slow. You have seen already the opposite: as Linux gains momentum the development speed grows.

      If Linux goes back to being a niche player it will for all intents be dead. It is important for Linux to keep growing. Linus and Alan (and the other key people) are now getting paid. If that stops they likely will quit, or significantly cut back on their contributions, because they are grown up and they have wives, kids and need an income. Other people can step in, but the learning curve will be incredibly steep and Linux will have fallen behind before they can finish the transition.

      Linux has grown beyond the point where it can be effectively maintained by part time volunteers.

    2. Re:How can ANYTHING "threaten" Linux? by phrasebook · · Score: 1

      Giving people an alternative to Linux isn't a threat - it's a choice.

      And if people make the choice to move away from Linux and to the Mac, then what?

      Oh look! Linux is threatened.

    3. Re:How can ANYTHING "threaten" Linux? by Spoing · · Score: 2, Insightful
      If Linux goes back to being a niche player it will for all intents be dead.

      Like FreeBSD? They seem to be alive and kicking.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    4. Re:How can ANYTHING "threaten" Linux? by birdowner · · Score: 1

      The parent raises a very important point. While it is good that Linux is getting popular, not everyone working with Linux is "fighting for the desktop". For us, Linux is a tool to get stuff done. And it does it so well. Linux fills a very important need and all this black and white "OS X will rule, Linux will die" talk is pointless. Call me when Google installs OS X on their cluster, ok? V.

    5. Re:How can ANYTHING "threaten" Linux? by hacker · · Score: 2, Insightful
      "Linux doesn't compete against Windows, MacOS X or Solaris. Linux vendors, like Red Hat, compete against Microsoft, Apple and Sun. Linux just is. The fact that it's supported by various companies is great but it's not essential for Linux survival. The fact that the amount of people and companies using Linux is huge and growing is terrific, but it's not essential."

      These are all valid points, but you forgot one subtle thing...

      Vendors having access to a Free (and free) operating system, Linux in this case, helps them push technology farther and faster, and helps get products out into customer hands more rapidly.

      It also allows those customers to hack on it, improve upon it (Linksys WAP/Routers being one great example, TiVo being another) and send fixes and features back to the vendors, who then incorporate them into their next revision of products.

      If Linux (or other favorite Free Operating System of choice here) did not exist , vendors would have MUCH more expensive products (to help offset their own licensing costs for embedded operating systems), and products would evolve MUCH more slowly (because fixes to the OS would have to go back to the commercial OS vendor for testing, Q&A, acceptance, and put into their release cycle schedule).

      The "death" of Linux wouldn't kill Linux, but it would most-definately dramatically slow down the advance of technology and further increase the costs associated with purchasing the hardware we all enjoy at low costs today.

      There's a lot more to it than just "desktop users" and "market share".

    6. Re:How can ANYTHING "threaten" Linux? by NotoriousQ · · Score: 1

      They are alive in the same sense as the guy from greek mythology whose liver got pecked out by vultures daily, but then he regrew it overnight.

      Sadly I think they will never leave that state, for that is their chosen burden... I mean license.

      --
      badness 10000
    7. Re:How can ANYTHING "threaten" Linux? by The+Dodger · · Score: 1

      Linux has grown beyond the point where it can be effectively maintained by part time volunteers.

      This is, if you'll forgive me, bullshit.

      You're completely missing the point and I can't be arsed explaining it to you in terms that are simple enough for you to understand.


      D.

    8. Re:How can ANYTHING "threaten" Linux? by The+Dodger · · Score: 1

      Okay, answer me this: What is Linux "threatened" with? Loss of market share? So what? When it was conceived, it had zero market share. Not just a very small percentage, but ZERO . People chose to use it, it became popular, trendy, a threat to Microsoft, blah, blah, blah. If people choose not to use it, it won't make any difference to what Linux is . You can't threaten Linux. It's always going to exist.

      Even if development completely ceases (and I do preduct that will happen...but only in the unforeseeable future when computing technology moves to a different paradigm which we can't yet predict), it's still going to be there, waiting for anyone who wants to, to pick it up and continute where the last kernel patcher left off.

      Stop trying to define Linux in terms of it's user base or feature set. It's a free, open kernel, not a commercial product. You can't threaten it and anyone who thinks otherwise is an idiot. Get a clue.


      D.

    9. Re:How can ANYTHING "threaten" Linux? by The+Dodger · · Score: 1

      I'm not forgetting anything. You listed a series of benefits Linux has brought and then said
      If Linux...did not exist ... The "death" of Linux...
      Linux does exist and it can't be killed.

      If you can figure out a way you think you can kill Linux, reply and I'll tell you why you're wrong.


      D.

    10. Re:How can ANYTHING "threaten" Linux? by Llama_STi · · Score: 1

      >>If everyone, right up to and including Linus abandoned Linux, I'd still be able to dig out my Red Hat CDs and install it on an old PC.

      That's right, you could. Now what's keeping you from doing the same with DOS 6.22 or OS/2 Warp? Nothing! You could do the exact same thing with those two OS's but I'm sure you'd agree, they're basically toast, right? If the people who develop for the platform stop then the platform will rot and likely die. After all, you can still write apps for those older OS's but you don't. What makes you think you would for Linux?

    11. Re:How can ANYTHING "threaten" Linux? by aCapitalist · · Score: 1

      There are plenty of legitimate reasons to use Linux or BSD or whatever, but once you brain damaged GNU drones pull your heads out of your ass and realize you're not more "free" because you have source code the better off you will be dealing with reality.

    12. Re:How can ANYTHING "threaten" Linux? by terjeber · · Score: 1

      If Red Hat and all the other Linux companies were to drop Linux and switch to something else, if Dell, IBM and all the other box suppliers stopped supporting Linux, if all the hardware manufacturers who currently provide Linux drivers for their products all stopped supporting Linux, it still wouldn't be dead.

      Wrong, or at least quite wrong. If Linux loses significant market share and IBM and others stop supporting it, it is about as dead as Terri Schiavo was last year. Sure, enthusiasts will keep it going as a hobby project, but as a player in ther market it will be dead. This means that relatively shortly after the latest and greates graphics cards won't have drivers any more etc. Slowly it will go the way of Minix.

  91. Lack of standards by spectrokid · · Score: 1

    is what is halting Linux on the desktop. ONE place for bookmarks, shared by all browsers. ONE place for file associations, shared by all window managers. etc, etc... Why is it so difficult?

    --

    10 ?"Hello World" life was simple then

  92. Seriously doubt it... by Junta · · Score: 1

    Apple has little to gain from the Linux kernel, and a lot to lose. The mach kernel is BSD licensed, and you can bet your ass that they will have some modifications to try to avoid booting on generic PC clones that they will not want to open up. Sure you could do this with linux, but they already have a kernel that works for them, their developers are familiar with, and they don't need much else.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  93. Re:Mac 924 Vs Microsoft Gremlin & Linux Miniva by ABaumann · · Score: 0

    Wonderful news from the Truth Hurts department.

    I have no idea WHY Apple did this. They totally lost one of the advantages that they had. When they sold us their own hardware, we thought it was part of what made the system stable, and IMHO it certainly is.

    Now they'll be comparing a P4 versus a P4. Basically, "This P4 runs Windows and it's $400. This other one runs OS X and it's $1400." Users will look at it as something like, "...so I'm paying $1000 for the OS?" Car/Computer analogies are great, and yours certainly holds a lot of water, however, I'd rather compare it to Lexus and Toyota, Acura and Honda, or Infinity and Nissan. Basically, all a mac will be now is a better built PC.

    I'll hand it to them though. They're taking an aggressive stance, because this will either kill them or make their market share go through the roof.

  94. Nothing can kill Linux. OS-X will kill Solaris. by Anonymous Coward · · Score: 0

    No, nothing can touch Linux. x86 OS-X will only kill x86 Solaris. I mean, who wants to use x86 Solaris when you have options like - Linux, Windows, OS-X?!!

  95. Apple will threaten Microsoft more then anything by ID000001 · · Score: 1

    Think about it. If Apple runs on x86. They probably can lock it down so the OS won't run on anything but their machine. However, there are absolutely no reason they can't run window on their machince. Better yet. Make a system that run OSX with almost completely native support for windows's application will not be difficult. If that happens. Whoever bought an Apple will have less of a regrate since they can switch back to windows if it turns out they don't like OSX. Where those who buy a Dell or any other system in the world won't have the luxary of running both OS in the same system. Think of the appeal this will have for people who still have reason to stays on Window yet want to try out Apple! Apple really did thought it through this time. I tell you what.

  96. Don't think of this as a different Apple by mc900ftjesus · · Score: 1

    This is going to be Macs with a different processor. Apple couldn't produce a OS that runs on generic hardware if they tried. At exactly which point will your average user care? And then explain what this has to do with Linux. A Mac is a Mac a PC is a PC, nothing has changed except by choosing Intel they can no longer say they use the bast components.

    The benefit of all of this is we don't have to hear the word Wintel anymore. I hate those words. Can I request that ./ers use 'weblog' from now on, do we need to save two letters just to sound stupid? We're better than that.

  97. And then there were three by Mr.+Cancelled · · Score: 1

    Nothing to see at Symphonys site unless you like "Bandwidth Exceeded" messages. Nothing but the home page displays now... everything else shows:

    Bandwidth Limit Exceeded The server is temporarily unable to service your request due to the site owner reaching his/her bandwidth limit. Please try again later. Apache/1.3.33 Server at www.symphonyos.com Port 80

    Good job guys, you killed it. Now Linux has no defence against the onslaught of OSX. Are you happy?

    For an encore I think we should now bring down the XFCE site as a means of showing our unity against OSX and Windows! Maybe after that we can move on and kill the KDE and Gnome sites as well.

    8)=

    1. Re:And then there were three by mr_beanz · · Score: 0

      Um... make that 4. The Hurd will take them all out... eventually.

    2. Re:And then there were three by Yaotzin · · Score: 1

      Let's just DDOS them and get it over with. ;)

      --
      Error: No error occurred
  98. More like, Linux is a threat to Apple by argoff · · Score: 2, Interesting


    The fact is that the Linux GUI is constatnly approaching "Apple Quality" and it will only be a metter of a few years before it gets there. Apple is trying to position themselves so that they can skimm off the top of the Linux boom and cut out a niche for themselves.

    1. Re:More like, Linux is a threat to Apple by American+AC+in+Paris · · Score: 3, Insightful
      The fact is that the Linux GUI is constatnly approaching "Apple Quality" and it will only be a metter of a few years before it gets there.

      Linux will continue to improve, but so will Apple; the question we need to ask is which one will improve faster in the GUI department. In this regard, my money is on Apple, simply because they have near total control over the user interface. They can stand up and say, "the behavior for X will by Y," and that's how it will work. Linux simply does not have this luxury. With Linux, you still have situations where applications work wonderfully with GUI A but have "quirks" if you try using certain features in GUI B, C, or D. Until there's a standard that desktop environment developers agree on and adhere to, you're going to have a fracured desktop experience.

      Yes, in another few years, the Linux GUI will quite possibly be as "good" as the Apple GUI is today. You're fooling yourself, though, if you think Steve is gonna sit back and say, "well, that's good enough." The real challenge for Linux GUIs will be to get better faster than Apple can--and I'm not sure they can, for the reasons stated above.

      --

      Obliteracy: Words with explosions

    2. Re:More like, Linux is a threat to Apple by Princeofcups · · Score: 1

      > The fact is that the Linux GUI is constatnly approaching "Apple Quality" and it will only be a
      > metter of a few years before it gets there.

      That's a moving target. The Linux GUI developers need to be creative, and shoot for a target well past where OSX is right now. Otherwise they will always be playing catch up.

      > Apple is trying to position themselves so that they can skimm off the top of the Linux boom and
      > cut out a niche for themselves.

      Right now the only money to made in Linux is on corporate servers. Apple makes most of their money off of graphics workstations and home user computers. Apple's competition for market share is squarely against Windows, not Linux.

      jfs

      --
      The only thing worse than a Democrat is a Republican.
    3. Re:More like, Linux is a threat to Apple by argoff · · Score: 1

      Linux will continue to improve, but so will Apple; the question we need to ask is which one will improve faster in the GUI department....

      Improvements with graphics are more like a log(n) function than a exp(n) function. There reaches a point where if you doubble the time and effort, it doesn't doubble the quality or performance of your GUI, but more tends to level out. Apple has limited room to improve, and Linux is comming up on it fast.

      In this regard, my money is on Apple, simply because they have near total control over the user interface. They can stand up and say, "the behavior for X will by Y," and that's how it will work. Linux simply does not have this luxury.

      Sure, some linux apps may have integration quirks, but if that levels out to 10% of them, but you have 1000 times more software to choose from on Linux, then the average user is still in far a better situation usability wise with Linux. Not to mention that a "forced" user environment can at times limit innovation and useability more than it can help it.

      You're fooling yourself, though, if you think Steve is gonna sit back and say, "well, that's good enough...

      GNU/Linux has been, and is growing at a faster rate technology wise, GUI wise, and user base wise than any other platform out there. It's uptake and improvement rate is literally faster than anything the industry has ever seen, including the internet. It has already beat Apple and Unix in market share. It is simply wrong to assume that Apple can "out-grow" Linux.

      That's why Linux is more of a threat to Apple than Apple is to Linux, and Apple is simply trying to ride the Linux boom for all it's worth.

    4. Re:More like, Linux is a threat to Apple by argoff · · Score: 1

      The Linux GUI developers need to be creative, and shoot for a target well past where OSX is right now.

      I don't know if they are, but I do know Linux is imoroving at an exponential rate, there are forces pushing the Linux GUI forward that are way bigger than just the GUI developers.

      Right now the only money to made in Linux is on corporate servers. Apple makes most of their money off of graphics workstations and home user computers. Apple's competition for market share is squarely against Windows, not Linux.

      Linux will win out in the corporate world because of "free" as in freedom/free markets, Linux will win out in the home user world because of "free" as in beer, and it will win out in the GUI world because of both those forces. So yes, in the end it will win out over both Apple and Windows, but for different reasons.

    5. Re:More like, Linux is a threat to Apple by hacker · · Score: 1
      "With Linux, you still have situations where applications work wonderfully with GUI A but have "quirks" if you try using certain features in GUI B, C, or D. Until there's a standard that desktop environment developers agree on and adhere to, you're going to have a fracured desktop experience."

      Others would call that CHOICE.

      Show me how I can remove that top menubar on OSX... Answer: You can't.

      Show me how I can change the windowing/titlebar/menu fonts on OSX to be 6pt fonts, aliased (or not). Answer: You can't.

      Show me how I can get application-specific context menus without having to go aaaaaall the way up to the top of the screen to that menubar. Answer: You can't.

      OSX, while pretty, severely limits the user experience (not to mention its pitifully slow in the graphics department compared to Linux on the same exact hardware).

      I'll continue to choose Linux over OSX every day, until they let me configure it the way I want to use the machine. Heck, even Microsoft Windows lets you change more of the UI than OSX.

    6. Re:More like, Linux is a threat to Apple by marcosdumay · · Score: 1

      Linux may never catch up Apple on design, but we can have a situation where the Linux design is god enogh(TM) and have more functionality. This would also be a bad to Apple.

    7. Re:More like, Linux is a threat to Apple by Anonymous Coward · · Score: 0

      He wasn't saying choice is bad, he was pointing out it comes with a high cost, and he's right.

    8. Re:More like, Linux is a threat to Apple by Anonymous Coward · · Score: 0

      Show me how I can get application-specific context menus without having to go aaaaaall the way up to the top of the screen to that menubar. Answer: You can't.

      Control-click with a standard Apple mouse, or right-click with any multibutton USB mouse. Damn, that was hard.

    9. Re:More like, Linux is a threat to Apple by terjeber · · Score: 1

      The fact is that the Linux GUI is constatnly approaching "Apple Quality"

      That isn't even close to true. Sadly, from the first day I installed version 0.91 (I think it was), I have been hoping it would, but have seen very, very slow progress. We are not that much closer today than we were then. Sadly.

    10. Re:More like, Linux is a threat to Apple by terjeber · · Score: 1

      Show me how ... Answer: You can't. Show me how ... Answer: You can't. Show me how ... Answer: You can't.

      Assuming the role of of a regular computer user: Why would I want to ... I won't. Why would I want to ... I won't. Users want to be able to run their favorite app on an OS that looks reasonably familiar to them. If I want to edit my digital video I don't really care where the menu is, as long as I know where it is.

      Other than that I agree that the "only on the top of my 21 inch screen" menu of Apple is a travesty too clearly rooted in the days of 11 inch monitors.

  99. it doesn't turn my head by Anonymous Coward · · Score: 0

    I already use icewm, with its configurable popup menus. I have tried rox and liked it, but I happen not to use it. I'm a command line type of person, except when sorting a directory containing lots of different types of files and then it's time to drag out nautilus.

    In short, why Symphony?

  100. Hmmm... by Beefslaya · · Score: 0
    Tough decision ahead for me, purchase Tiger for my PC, or...continue to bang my head on the keyboard with driver support, and 10 different distros going in 150 different directions.

    I for one, have been waiting for the arrival of x86 OSX.

    Who wouldn't welcome BSD security and Stability with fullout hardware support? HERE is your Microsoft Dragon slayer here....

  101. Ctrl+Alt+Del webcomic by brontus3927 · · Score: 1, Funny
  102. The only thing that "threatens" Linux... by GReaToaK_2000 · · Score: 1

    Is Linux itself...

    Joking aside, lets think about this.

    People will USE what WORKS for them. (OR what is FORCED upon them)

    I HAVE to use Fedora 2 on my laptop because we don't have the licenses to put something else. I find "most" of the features to be great and work well.

    BUT... (and that's a BIG but :)

    o Windows File Share "browsing" barely works and when it does it's painful to use.
    o Evolution needs to continue to evolve. (lots bugs that cause issues, mainly useability issues, in addition to the be-dreaded 'winmail.dat' problem)
    o I STILL need to use IE to view some sites and do testing for the software products we produce. The Wine Install for FC2 does NOT work.
    o Finally, drag and drop (DnD), cut/copy/paste (CCP) simply NEEDS to work correctly to be consider a viable desktop system. This is one of the primary value adds of a GUI.

    I am using it, so I don't want to "hear/read" people bitching about me complaining as if I don't use it... I am using it and HAVE been using it for about a year now... Of course any chance I get to use XP or better yet 2000AS I do...

    I have installed and USED CentOS 4.0 on several occassions and MAY use that on the laptop as it seems there are a number of issues Fixed on that version...

    The capabilities I LOVE...
    o NOTHING beats the "look" of the fonts and windows. It is smooth, while I know Macs beat the pants off of everything when it comes to look. I hate/detest the "useability" of the Mac mouse and gui... She looks nice but she's no fun... Sorry about that Mac users, I truly have no intention of insulting Mac users. So, Linux is MUCH better then Windows in the looks department.
    o The configurability of the desktop is nice.
    o Even KDE is pretty good (widows file browsing works in KDE, not Gnome, very weird) but, as much as I complained about the file share browsing, if I'm GOING to use anything it will be Gnome because it simply "looks" better and is easier on my eyes.
    o The ability to setup a "server" evironment on my laptop to do dev and debug on, is VERY GOOD!!! The BIGGEST reason I have not pushed for a license for my laptop is simply that I can recreate, for the most part, the servers that we use for our products right on my laptop.

    So, that is my take... I will not get into arguements over this, unless someone has a REALLY valid point or useful information that could make Linux-on-my-laptop better for me...

    This is my opinion and I don't care about yours UNLESS, you have helpful/construct point to bring up... I believe it is a waste of time, on both ends, to argue unless it is constructive...

    SO, at long last, until Linux continues to evolve and change to the point of getting past a number of these desktop OS GUI issues (DnD, CCP, file share browse, smooth UI experience, etc.), it will never be considered a real and valid Windows desktop OS replacement.

    ~G

  103. -1 Troll by TuringTest · · Score: 1

    but whatever, I'll bite.

    You realize that this interface will be themeable, right? So you can install your preferred dark, gothic theme if that's how you like it. Funny to mention that those are mockups, not the really final decision of the interface (current implementation has a dark blue & black wallpaper).


    It's also kinda funny how it misses its own advice -- the "Laws of Inteface Design" on the site says "3.Scrolling sucks. A good user interface will minimize scrolling, and encourage the user to create volumes of information that do not promote scrolling." -- yet the first screenshot shows a browser window with both a vertical and the dreaded horizontal scrollbar.


    Did you missed the version number that says this project is "Alpha 3"? The current applications used are not part of the interface, which is currently limited to the desktop & helper launcher pages. *Those* are scroll-less, submenu-less designs.

    --
    Singularity: a belief in the "God" idea with the "demiurge" relation inverted.
    1. Re:-1 Troll by mattdm · · Score: 1

      You realize that this interface will be themeable, right? So you can install your preferred dark, gothic theme if that's how you like it. Funny to mention that those are mockups, not the really final decision of the interface (current implementation has a dark blue & black wallpaper).

      I don't want a dark, gothic theme. I want a well-designed one. In fact, I don't really want a whole lot of themes -- I don't think interchangable widget-wallpaper is the right approach to good overall design.


      Did you missed the version number that says this project is "Alpha 3"?


      Did you miss the post I was replying to, which said about the current screen shots, presumably the same ones I was looking at, "Wow. That's so beautiful, it brought a tear to my eye."? 'Cause that's what I'm responding to, not some future version of the project.

    2. Re:-1 Troll by TuringTest · · Score: 1


      Did you miss the post I was replying to, which said about the current screen shots, presumably the same ones I was looking at, "Wow. That's so beautiful, it brought a tear to my eye."? 'Cause that's what I'm responding to, not some future version of the project.


      I didn't. My "this project is Alpha 3" was targeted at your "funny how it misses its own advice -- the Laws of Inteface Design".

      Have you seen the mockups of their intended final design?
      Actually I find their design really good - their overall Desktop solution is better than anything Windows, OS X or previous Linux had to offer. It definitely avoids clutter. Bright graphics and colors is mostly a matter of taste as long as they don't make the interface parts distracting or difficult to see.

      --
      Singularity: a belief in the "God" idea with the "demiurge" relation inverted.
  104. Until Apple announces OSX for non-Apple machines.. by Andy_R · · Score: 3, Insightful

    The only Linux this is a threat to is Yellow Dog.

    Apple are staking their entire company on OSX not being pirated to other x86 platforms. OSX will not support any non-Apple hardware, so it's not a threat, unless you count possible increased Apple market share due to lower prices.

    --
    A pizza of radius z and thickness a has a volume of pi z z a
  105. What's needed for a Linux desktop by whitroth · · Score: 1

    ... to really get ordinary users to beat down the doors? There's one, and only one place to start, KDE, Gnome, and OpenOffice.org PAY ATTENTION: make sure that the developers, esp. the gatekeepers, test everything on a top of the line machine... that is, one that *was* top of the line at least five years ago.

    DO NOT TEST ANYTHING ON A MACHINE YOU CAN EVEN PLAY THE GAME THAT JUST CAME OUT THIS YEAR.

    Overwhelmingly - go ask your non-computer-person friends, family, and coworkers - they do *not* buy new systems every two years, and every single one of them is frustrated by "you've got an upgrade, but I need new hardware?"

    Don't believe me? Ask around, and see how many people are still running Windows 98.

    Hell, I run a K-6 950MHz, 192M RAM, and goddamn OpenOffice.dog runs no faster than it did on a K6 233 - as though I was running an 8088. I run IceWM, because it's not a tenth the size of KDE, no does it start so much garbage.

    I challange any of you to be happy with response on a five year old machine. Firefox has it right: smaller and faster, not bigger and slower. Let users do *more* with what they've got, not tell them to get faster systems. That, after all, is what we all hate about Microsoft (tm), right?

    mark

    1. Re:What's needed for a Linux desktop by ssj_195 · · Score: 1
      Thankfully, both KDE and GNOME are currently shifting their efforts to optimisation. Software development proceeds sporadically, and spans many phases (often several at the same time!). The three major phases are probably a) Massive Feature Addition, b) Bug-Fixing and c) Optimisation, corrsponding roughly to Making it Work, Making it Work Well, and Making it Work Fast. As I stated in a post in another thread, I don't really consider Desktop Linux to have started sincere development until a year and a half - two years ago, at which point Desktop Linux was horribly behind the times.

      Since then, though, there has been a *massive* amount of work done, mostly in the areas of adding new features or increasing the power of the libraries. This has left Desktop Linux in a rather buggy, bloated state, but I think it is beginning to settle down slightly and tend towards b) and c) (the kernel itself seems to have a recent flare-up of new stuff being added, to the detriment of its speed and stability; doubtless, the latter two qualities will reassert their dominance once the frenzy wears off). Robert Love gave a very interesting talk on optimising GNOME (most of the ideas apply to KDE, also), and it seems that a lot of developers have a keen interest in getting Linux to run on old hardware - particularly the Ubuntu team, who have the resources and know-how to get the job done.

      OO.o is a lost cause, alas, although I have heard good things about KOffice. Some have stated that it is approaching the functionality of OO.o, but is still fairly lightweight - can anyone who has used the two for "proper" work possibly comment on this?

      Oh, and while I love Firefox, I find it odd that you were hail this as a prime example of "smaller and faster, not bigger and slower." :)

  106. Statically linked applications by Teckla · · Score: 1

    Speaking with my "user cap" firmly on my head, I prefer statically linked applications because they're much easier and more reliable from a user perspective.

  107. Yellow Dog Linux is NOT going to Intel by sjvn · · Score: 1

    Read all about it:

    PowerPC Linux Vendors Are Sticking with It

    http://www.eweek.com/article2/0,1759,1825444,00.as p

    Steven

  108. no it doesn't! by xutopia · · Score: 1

    And I'll tell you why. I bought a powerbook because I liked the model The only reason I use OSX is because it's a nicer OS and has drivers for the WIFI card. If ubuntu had wifi drivers I'd be under Linux way more because at least the OS doesn't force me to use formats and hides my files away from me.

  109. Re:Mac 924 Vs Microsoft Gremlin & Linux Miniva by Anonymous Coward · · Score: 0
    The 924 may have been designed by Porsche, but it also had the same engine as models of the AMC Gremlin and Volkswagen Mini-van, and was built by Audi ( at that time it had just become a division of Volkswagen ). In comparison to other similarly priced sports cars of the day, the engine failed to deliver the expected performance, even with the addition of a turbo in 1979.

    If they wanted to share an engine with a Gremlin, they should have used old Rambler inline 6. In the 70s bought a Gremlin with the Rambler engine from a friend for $90. The rest of the car was a dangerous piece of junk, but it was one of the nicest engines I've ever seen. It ran smooth and strong, and it looked almost new even though the rust-riddled car looked like a piece of swiss cheese.

    When I finally junked the car because it was physically falling apart, it was kind of sad to leave that poor engine there purring like a kitten. It deserved a better car.

  110. is it a threat? by Shads · · Score: 1

    maybe... but linux is as big a threat to mac os.

    Its the proverbial, who eats who... someones gonna get chowed on...

    --
    Shadus
  111. Advantages of .app and .framework by Paradox · · Score: 1
    I do like the .app application bundles (reminiscent of applications on Acorn's RISC OS!) but I wouldn't say everything was lovely - such drag-and-drop bundles don't work so well when something needs to install frameworks, drivers or whatever.
    Well, the .app stuff is nice because it's trivial to include your required frameworks. There is a spot just for them. Never worry about versioning again, at the cost of your application size, of course.

    What's even more impressive to me, as a developer, is the .framework scheme. Similar to the .app, the .framework allows libraries to consolidate their headers and binaries in one place. Key to this is that it also allows multiple versions to be held in one place. When upgrading a framework, the system should just update the framework internals without replacing your old version. It's extremely nice, and I really wish Linux would adopt it.

    It's not as if applications don't use that system for installation, either - I recently installed iLife '05 (yeah, I'm slow) and it appears to have spread files out all over the place. Not as bad as your average Linux application admittedly, but I'm not sure how one would go about tracking them all down. (Okay, so I'm not likely to remove it, but I'm using it as an example, okay?)
    The standard Installer.app keeps receipts of every .pkg it runs through /Library/Receipts. You can use that to remove them.
    --
    Slashdot. It's Not For Common Sense
  112. Re:Until Apple announces OSX for non-Apple machine by Luthair · · Score: 2, Insightful

    This is dead on imo. The situation isn't any different than before, Apple is still tying the OS and hardware. Linux is still free and uses (presumably) cheaper hardware.

    This is a story for the sake of having a story.

  113. I have a dream... by Anonymous Coward · · Score: 0

    One day, I hope we can finally all have an advanced OS which should eliminate this kind of garbage. Take the Hurd for instance. Have two apps with conflicting dependencies? So what! Run the two apps under two slightly different versions of the main OS. Each individual app can gets to have the worldview it prefers, and vice-versa. Problem solved.

  114. Torrent available? by iplayfast · · Score: 1

    The wikipedia says that it "comes in the form of a Knoppix-based LiveCD", and I'd like to try it out. (course it's /.'d now). But if there is a torrent available I'd like to know about it.

    1. Re:Torrent available? by Anonymous Coward · · Score: 0
    2. Re:Torrent available? by Adartse.Liminality · · Score: 0

      torrent can be found here http://torrentsearch.us/browse/linux-150.php but tracker is the symphonyos site so: tracker return code 500 ;-(

      --
      Smokin' & rubying away
  115. Dear Slashdot: keep your dumb plugs to yourself. by Anonymous Coward · · Score: 0

    My my my, what a useless article.

    What does SymphonyOS have to do with Mac OS X on Intel? Absolutely nothing. So why, tell me why, is this called "Could Apple's Intel Desktop Threaten Linux?"

    Because someone wants to bring attention to their favorite Linux, and is piggy-backing off of recent news.

    For shame. Folks, Linux is not dying. (Netcraft has not yet confirmed. *ducks*) If a bunch of people jump ship because of some Apple nonsense, then those will be the shallow ones. Good riddance. The real driving forces in Linux -- serious hackers, people who use Linux to get things done every day -- are not about to up and abandon it.

  116. The world has not moved. by jusdisgi · · Score: 1
    Look guys, I hate to break it to the sensationalist-journalism crowd, but this just is not an earth-shattering development. Apple is changing processors. This does not equate to a massive assault on, well, anything. They are still going to sell expensive, well designed, proprietary boxes with a welded-in OS. It's not going to run on commodity hardware. It'll still "just work" and Mac people will still love it for all the same reasons, and us Linux heads will keep doing what we're doing.

    The fact that those machines will have x86 procs from here on in actually makes me much less interested; I always wanted a ppc linux box (I've plenty of x86 ones) and I probably would have even dual-booted it. But now....what's the point?

    --
    Given a choice between free speech and free beer, most people will take the beer.
  117. Re: Tempted to agree by mwood · · Score: 1

    The fuss is at least in part that Apple used to be a supplier of not-too-outrageously-expensive PPC systems, and you could rip off the OS and install something else if you wanted something-else-on-PPC.

  118. What's so wrong w/ KDE or Gnome by 21chrisp · · Score: 3, Interesting

    I don't understand why everyone seems to think KDE and Gnome are so unusable. They both seem very usable to me. In fact, I get around more easily in KDE than OS X. OS X is just more "pretty." I prefer KDE to Gnome, but I can certainly use Gnome just fine. Why do so many people buy into the OS X hype? Not that OS X sucks.. not by a long shot. I use it every day and enjoy it (love would be an exagerartion). Really though.. what makes desktop linux so bad? Everybody I know who has tried and taken the time to learn it ends up enjoying it. It's only those not willing to try or don't want to learn something new that say it sucks.

    1. Re:What's so wrong w/ KDE or Gnome by metamatic · · Score: 1

      I use KDE every day. I use OS X every day. There are just so many things that OS X does better.

      Menus are faster to access on OS X, because there's one menu bar at the top of the screen. File management is better on OS X. There's a button to size windows to the optimum size on OS X. Contextual menus allow me to pull data into applications quickly and easily, for example to file bits of information away in a notebook.

      Actually, the single best thing OS X has going for it over KDE is that the fucking clipboard works properly, always, in all applications...

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    2. Re:What's so wrong w/ KDE or Gnome by Minstrel+Boy · · Score: 1
      Everybody I know who has tried and taken the time to learn it ends up enjoying it.

      You're begging the question. Sure, everyone who liked the desktop enough to get it usable still likes it once it is usable. (shrug)

      The problem is saying that anyone who doesn't meet that criterion is an idiot/luddite/adjective-of-choice-meaning-they're- the-problem. I work in IT for a living (network and security). For my home machine, nobody's paying me to fight with the damn computer. EVERY TIME I try to accomplish something towards GUI productivity with a KDE/Gnome environment, I end up fighting with the damn computer. Sometimes I win, sometimes I lose. Either way I'm out a bunch of time, and what's worse, next version of the distribution/package I'm likely to find my approach either a) no longer necessary, so all that time was wasted, or b) no longer effective, so I have to start fighting with the damn computer again.

      I've run FreeBSD for years as a server, and while there's some issues with that as well, it's NOTHING like trying to get a desktop environment stable and complete.

      I latched onto OS X at it's inception with the specific assumption that if anyone could put a good UI on top of Unix and make it work, it would be Apple - I would never have considered a Mac running the earlier Mac OS. I'm now on my fourth Mac, I have a 17" PowerBook and a Mini that has replaced my FreeBSD server. It Just Works (tm). I can shut the lid and the PB is asleep. It will sleep all weekend on twenty minutes worth of power and wake up in three seconds. Ubuntu can't do that, I tried it. Wireless works great. Ubuntu can't do that, I tried it. I can shut the wireless down, sleep the machine, wake it up, click a selection in iTunes, and the computer reconnects my NFS mount to the Mini and starts playing the damned song. It Just Works (tm). And for the things that don't Just Work, I at least have a higher degree of confidence that figuring out how to make them work is time invested rather than spent, because the framework is consistent and stable from week to week.

      If I want to geek around with the computer, I can - just spent time over the last week converting my IMAPS server from xinetd to launchd. But the fraction of time I want to do something new with the computer and It Just Works (tm) is an inverse between OS X and a Linux distro. If that means I'm not committed enough for Linux - fine. I'm not committed enough to run triathlons, either.

      KeS

  119. Take this seriously by Random+BedHead+Ed · · Score: 1

    The standard Slashdot reply I've been reading is that this will not affect Linux. And in the short term I agree. Apple is indeed only releasing OS X for their own Intel Macs, not Intel machines in general, and Linux will still appeal to the people it appeals to now. Add to the above items a factor that rarely gets attention: that the rest of the world is more likely to embrace Linux than OS X. It is gaining traction, especially in developing countries and countries that do not like paying MS. In many such places Apple hardware is unavailable.

    However, Apple should be taken seriously. Most of the things they have done since Steve Jobs came back have been successful, the cube notwithstanding. While Apple has publicly stated that they will not release their OS for any old x86 machine, they now hold this card in their hand, and can pull it out at any time. This is a big deal. Don't disregard it.

    Apple may not see any benefit in switching from a hardware focus to a software focus at the moment, but this could change. If their market share goes up in the next few years OS X will get more credibility as a Windows-equivalent, which could make a general OS release more likely. By the time this happens Apple will have x86 apps galore. If their market share goes down, they could release OS X for x86 as an act of desperation.

    Many people have wisely pointed out that Apple wouldn't want to support a ton of different hardware configurations, and this is true. But Apple has the option of ditching Darwin and FreeBSD and instead building their APIs and GUI on the Linux kernel instead. If they went this route the advantages of a non-Apple Linux distro would largely disappear, and only cost and freedom would remain to separate Apple from non-Apple. The kernel and uilities would be free, but the GUI, packaging system and APIs wouldn't be. For most purchasers these negative factors would be outweighed by the availability of apps and the pretty GUI.

    We've read about nifty GUI improvements for Linux for a long time, and every time someone puts a new bell or whistle on Xorg or a desktop environment we all ooh and aah it ... but few of us actualy install it because it always runs like crap if you don't have 2 GM of RAM and no other programs running. Let's start pressuring distributions to start implementing and improving these changes. This is it: crunch time. Linux can outdo Apple ... but it's time to ditch the same-old UI and package management and move on. Quick.

  120. (As the article is off topic) Win32 on Apple x86? by dwalsh · · Score: 1

    The article is a plug for a distro, disguising itself as relating to Apple on Intel, so I might aswell ask this question relating to the Apple/Intel announcement:

    Will it be possible to install Windows for dual booting? You might need some drivers for whatever proprietary Apple stuff on the motherboard, but how much of an impediment would the Apple BIOS be?

    Some may wonder what the point would be. You may want / have to use Windows for some purpose and want / have to have access to a Mac and OSX. For Apple, the point of the OS is to sell Apple hardware, so if you are running Windows on their gear, it is not the end of the world, especially if the option makes Macs more desireable for some.

    I could even see Apple taking on Dell to an extent. Sounds stupid, but hear me out:

    1. Apple make well-engineered PCs with low noise characteristics and elegant styling and packaging.
    2. Where I live, an Apple is the only PC you can buy inside a shopping mall. The stores that sell mobile phones have branched into iPods, and now Mac minis and iMacs.
    3. Windows + OSX is a unique selling proposition.
    4. Apple have the highest profile and most desireability of any PC brand.
    5. Dell are currently planning a "luxury" priced range of PCs, coincidentaly at Mac type prices.
    6. Apples top engineers have succesfully cracked the secrets of the mouse with more than one button!

    Please campaign to have me replace John Dvorak.

    --
    ${YEAR+1} is going to be the year of Linux on the desktop!
  121. Possible Solution? by Dasch · · Score: 1

    Why not make a package file that not only contained the package(s) itself and a list of dependencies, but also a list of URLs and/or repositories where those dependencies could be found. That way it would be possible to download a package file, open it, and have all dependencies installed automatically.

  122. people just don't get it. . . by diitante · · Score: 0

    Being a regular Linux user on both my servers and my laptop that I use every day, with all the same functionality and better reliability that any Win or Mac business user has, I can say that these people in the press and the other tech pontificators out there just dont understand Linux or its users. Linux is not a "product" or "business" per se' like Apples OSX or WinXP. Sure there are the Red Hats of the world but they really dont sell Linux, they sell service. Simply put Linux cant be threatened due to its very nature. People will use it or wont. People use linux for many reasons, people use Win for one reason. If you ask me it is MSFT that is in the most perilous position of all. When people use a product because they believe that they have to, the providers business model is built on a foundation of sand and it is only a matter of time till a collapse occurs. The success of OSX on Intel will have no bearing on Linux. There is no competition to speak of so the can be no loser. M

    --
    $ whatis msft msft: nothing appropriate
  123. Not An Original View, But... by Anonymous Coward · · Score: 0
    The Tao of Mac has a very pointed piece on that, apparently written just yesterday.

    The guy does have a point - Linux has been spending too much time on geeky stuff and very little on actual usability.

  124. Oh boy by he-sk · · Score: 1

    OS X running on Intel will not have any impact on Linux whatsoever. For those of you who are waiting to boot OS X on your stock PC from Dell or so... don't hold your breath.

    Apple is not in the business of selling you OS X or their other apps. They sell hardware and use their (arguably great) software to give you a reason to buy their stuff. Why would they let you run OS X on a machine you haven't bought from them?

    Secondly, the eWeek article is written by an idiot. I don't know the speed of the binary translation layer in OS X on Intel (Rosetta), but I do know that virtualization software has nothing to do with it.

    --
    Free Manning, jail Obama.
    1. Re:Oh boy by fishbowl · · Score: 1


      "OS X running on Intel will not have any impact on Linux whatsoever."

      I'm guessing that it will, in the sense that it will provide Linux with one more porting target. (I don't expect the IntApple chipset to be a regular x86, does anyone?)

      It'll be another platform of consumer level hardware that Linux can target.

      Maybe I've misread the news, but I haven't seen anything to indicate a scenario where you'll have OSX running on Dells, Asus motherboards, etc.

      --
      -fb Everything not expressly forbidden is now mandatory.
  125. why is this a threat? by alx512 · · Score: 1

    OS X may be running on Intel, but it's not like we're going to be able to go get a copy of OS X and install it on the machine that WAS running linux is it? I thought Apple had stated that even though macs will be Intel based, OS X will still only run on Mac hardware.

    That being the case, I don't see how this threatens linux. Am I missing something?

  126. Bizzaro world? by MachineShedFred · · Score: 1

    "hemorrhaged $276 million last quarter"

    Or, according to plenty of news sources, it was their most profitable quarter... EVER.

    "racking up a dizzying $2.4 billion in debt"

    Or, according to SEC filings, they have no long term debt as reported on page 23 of their FY2004 10-K filing. OOPS.

    I won't even bother to go into the rest of this bullshit, as I've already knocked the foundation out of your argument.

    --
    Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
  127. Why make this so difficult? by Anonymous Coward · · Score: 0

    It has been said a million times and no one listens, and yet one feels compelled to keep trying by stating the obvious. In order to compete with the Mac on the desktop, all the Linux community has to do is to get behind GNUstep. This will make porting of applications from the Mac to Linux much easier. There are probably many tasks for which Linux is better suited than the Mac, and for developers who originally write applications for the Mac, a ready and waiting OpenStep library is a good incentive to port if they determine Linux is a more appropriate platform for what they're trying to do.

    The Linux world really had better start getting its head out of the MS Windows. Linux people are way too Microsoft-centric (.Net, C#, blah, blah, blah).

  128. Re:(As the article is off topic) Win32 on Apple x8 by dick+johnson · · Score: 1
    The answer to your question about dual booting is yes. Apple officials have said they have no plans to prevent users from installing and running windows.


    This was revealed in a news.com story.



    The quote was on the second page of that link:


    >>
    After Jobs' presentation, Apple Senior Vice President Phil Schiller addressed the issue of running Windows on Macs, saying there are no plans to sell or support Windows on an Intel-based Mac. "That doesn't preclude someone from running it on a Mac. They probably will," he said. "We won't do anything to preclude that."


    However, Schiller said the company does not plan to let people run Mac OS X on other computer makers' hardware. "We will not allow running Mac OS X on anything other than an Apple Mac," he said.

    The news is actually better than dual boot though. With Virtual PC, you will be able to run XP in an application window on Mac OS. You won't need to reboot. And, because it's running on an X86 chip already, the performance should be as good as Windows running on a dedicated PC.

    --
    - dj
  129. Symphony OS by Anonymous Coward · · Score: 0

    Greetings Slashdot. I am the symphony os project manager. Our site is obviously slashdotted at this time but the mirrordot mirror is available at
    http://mirrordot.org/stories/325a42c04c64f80d25bdc 8518114af11/index.html
    and the Symphony OS Alpha 3 ISO is available at
    http://ftp.ussg.iu.edu/linux/symphonyos/

    If anyone has any specific questions they can post on our forum tomorow when the site is restored or they can email me at ryan at isptec.net

    Thanks
    Ryan Quinn
    Symphony OS Project

  130. Simple, dumb, and easy :-) by kollivier · · Score: 4, Insightful
    Now, take Debian's package system: it handles dependencies, version conflicts, alternative packages that serve the same purpose, etc, etc, ec. And it is absolutely easy: an apt-get install xyz installs/updates package xyz and all the necessary shared libs, updates file associations, whatever (and it does not takes exactly rocket science to create some GUI for that single command line).

    I realize this could start a 'flame war', but it surprises me how many Linux users just don't see why package managers are not the greatest thing since sliced bread for average users.

    While you and others may go "wow!" at all the magical stuff apt-get does, the average user doesn't even know what dependecies are, nor do they care. And they don't want to care. On Mac, as "simple and dumb" as the OS X system is, it *just works* for everyone from grandma to geeks. A simple and dumb system is also, well, very easy to understand! Drag and drop your app into the folder. Easy. Nice. As for package managers, I've had to deal with scenarios where I had to muck with the package manager configuration to get it to install packages for me, and I've had to "add URLs" to the database at which time I was warned about "untrusted sources" (the average user is NOT going to grok all that). In fact, when the average user sees "no results" from the database, they'll simply conclude the package isn't available and stop. I'm not sure how anyone thinks this is easier than going to versiontracker.com/apple.com/etc. and just downloading a file (or popping in a CD), then dragging the app into the applications folder.

    If you doubt me, have someone do usability research on package managers and drag and drop installs, and see which is, on average, easier for users to understand and get working with. If you really think package managers like apt-get will come out ahead, then you must spend a lot of your time on the computer and deal regularly with others like yourself.

    If you really want the Linux desktop to succeed, you have to question why lots of people are switching to Mac instead of just 'bashing' anything that is not as complex and elegant as apt-get. Call it dumb, call it simple. I call it a solution that works, and considering Macs are seeing a 40% growth this year, so do a couple other people as well.

    As someone whose tried every Windows from 3.1 to XP, close to a dozen Linux distributions (including Debian and Ubuntu), and OS 9 and OS X, I have to say application installation and removal on Mac blows the others away. It works and it's brain-dead simple, which means I spend more time doing real work than fooling around with installers and packaging programs. Good luck on converting the world to apt-get, though.

    1. Re:Simple, dumb, and easy :-) by dabadab · · Score: 1

      I think you mix up two things: interface and internal workings.

      As for the interface: a drag'n'drop interface for apt is abolutely feasible. It could be, and perhaps it is already implemented (I don't know, since I would not use it anyway).

      And I did not bash OS X, I've just observed that their solution is a really simple and limited one. Using it instead of the Debian system would not solve any problem but create lots of additional ones.

      --
      Real life is overrated.
    2. Re:Simple, dumb, and easy :-) by dodobh · · Score: 1

      Depending on what you are using a Mac for. Most people I hear from appear to use the Mac as a Unix which also runs Microsoft Office.

      Everything else is pretty much ignored, And of course, you are still missing out on understanding how complex Unix applications can get.

      --
      I can throw myself at the ground, and miss.
    3. Re:Simple, dumb, and easy :-) by kollivier · · Score: 1
      I think you mix up two things: interface and internal workings.

      To users, they're one and the same. i.e. take my comment about adding a URL to the repository, or not being able to find packages (that exist somewhere, just not in the package manager database). The inner workings of apt-get have forced an implementation detail to be part of the interface. The inner workings have thus 'complicated' the software interface. So users are going to confuse the two, and it's why I phrased my argument the way I did.

      As for the interface: a drag'n'drop interface for apt is abolutely feasible. It could be, and perhaps it is already implemented (I don't know, since I would not use it anyway).

      I'm not sure how a drag and drop interface for apt-get would look, but the fact is that I have a great experience on OS X *without* apt-get. What do I need it for again? I've been using Mac (and developing software on and for it) for 3-4 years now.

      If developers bundle non-system dependencies or statically link them, the need for apt-get or similar tools basically disappears. As awesome as the software is, it does something that on Mac doesn't even need to be done. This makes life easier for users AND software developers alike. I've tried packaging for Linux, the learning curve is several times higher than Mac or Windows.

      And I did not bash OS X, I've just observed that their solution is a really simple and limited one. Using it instead of the Debian system would not solve any problem but create lots of additional ones.

      What complaints have you heard from Mac users about this system? Particularly, ones that aren't Unix developers? I've heard none. Unix developers can use Fink or DarwinPorts (though I just use source tarballs), but when we're talking about "Linux on the desktop" we're talking about converting people who aren't Unix developers, obviously. So from your arguments so far, the problems for desktop users that you suggest exist are theoretical ones, at best. To me, that's not a solid argument against OS X's packaging system, it's just "name calling". (obviously, "dumb" doesn't have positive connotations and suggests deficiency)

      Unfortuntately, it is just this kind of logic that keeps Linux from moving forward. I use an "apt-get" free system every single day and it causes me no problems whatsoever. So why should I learn apt-get? Why should I install it? Why should I deal with it? These are the questions you have to answer for potential Linux converts, who will have to use apt-get, or RPM, or portage, whether they want to or not.

      And, finally, you haven't answered the converse question - why NOT use OS X's approach on Linux? "simple and limited" say nothing. Explain what problems users on OS X are having and how apt-get would solve those problems, or, at least consider that maybe OS X's system is a better solution than you suggest it is.

    4. Re:Simple, dumb, and easy :-) by kollivier · · Score: 1
      Depending on what you are using a Mac for. Most people I hear from appear to use the Mac as a Unix which also runs Microsoft Office.

      Yes, you're right that it depends, but we're talking about Linux on the desktop. Most people I know replaced their Windows with Mac, and don't know anything about Unix. These are all 'potential' Linux users. The users you're talking about are Unix/Linux converts all ready. They probably have little problem dealing with complexity.

      Everything else is pretty much ignored, And of course, you are still missing out on understanding how complex Unix applications can get.

      I'm not missing out on anything. I'm a software developer who uses Linux. I KNOW how complex it can get, and that's precisely why I don't use it except when I have to. The thing is, if Unix apps are so complex, then that's a problem that Unix apps will need to find a solution to if they want to win over new users, because I don't have that complexity on Mac, even when dealing with things like HD video production and 3D modeling software. Does it really need to be this complex?

    5. Re:Simple, dumb, and easy :-) by bnenning · · Score: 3, Informative

      why NOT use OS X's approach on Linux?

      Because on a Mac, you can be guaranteed of the existence of preinstalled libraries, and on Linux you can't. I agree the Mac way is much better, but until there's a ubiquitous Linux standard it's not going to be feasible there.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    6. Re:Simple, dumb, and easy :-) by kollivier · · Score: 1
      Because on a Mac, you can be guaranteed of the existence of preinstalled libraries, and on Linux you can't. I agree the Mac way is much better, but until there's a ubiquitous Linux standard it's not going to be feasible there.

      You hit the nail on the head about support. However, every Linux vendor doesn't need to adopt this, just one does. We're talking about distribution of binaries, and it's not like RedHat binaries run on SuSE or Mandrake or Debian. Package creation will be much easier, meaning that developers will be more likely to actually create packages. Other distros will get left behind (or have to recruit/hire more and more packagers) as more and more developers get comfortable with just building a binary and plopping it on their web site/SF site, etc.

      In fact, the interesting thing is that if one vendor succeeds with this, then it'll force other vendors to adopt it, forcing them to - in turn - adopt a standardized set of "system components" as that's the only way things will work. Make the change, and the standard will follow. Don't wait for the standard to make the change. If I had some resources I'd build a distro like this myself because I believe it'd open Linux up to whole new markets and I do believe such a thing could be sold.

    7. Re:Simple, dumb, and easy :-) by Brandybuck · · Score: 1

      The inner workings of apt-get have forced an implementation detail to be part of the interface. The inner workings have thus 'complicated' the software interface. So users are going to confuse the two, and it's why I phrased my argument the way I did.

      I've never used apt-get, but I have used many other package managers. On a KDE or GNOME desktop, installing a new application is as simple as download the app and double clicking on it. You're done. If there are missing dependencies they're automatically downloaded and installed for you. Actually, if the user is willing to browse a list of available packages locally instead of browsing a list of available downloads online, you can skip the manual download altogether. No, it's not perfect, because you can still get that "untrusted" message. But how is OSX any better, especially when it's completely silent about "untrusted" applications?

      If developers bundle non-system dependencies or statically link them, the need for apt-get or similar tools basically disappears

      You also end up with huge redundancies. Something like KDE which would normally take a few hundred megabytes of storage now takes hundreds of gigabytes. Instead of one copy of Qt and kdelibs you now have hundreds. And double the size for every additional user installing it.

      For most software packages, it makes sense to install them to a central shared location.

      --
      Don't blame me, I didn't vote for either of them!
    8. Re:Simple, dumb, and easy :-) by Blakey+Rat · · Score: 1

      Amen. I'm with you 100%. Linux developers need to step back from ripping-off Windows features and start ripping-off some MacOS features-- and MacOS' install procedure is the perfect place to start.

      And look at it this way: When you're done, you can get converts from Windows by telling them how easy installs in Linux are! You can't do that now; at best installs are the same.

    9. Re:Simple, dumb, and easy :-) by kollivier · · Score: 1
      I've never used apt-get, but I have used many other package managers. On a KDE or GNOME desktop, installing a new application is as simple as download the app and double clicking on it. You're done. If there are missing dependencies they're automatically downloaded and installed for you.

      But on Mac, users and developers alike do not need to worry about any of this, which by default simplifies issues. It may "magically" work (when it does work without effort, and in my experience it doesn't always work), but it doesn't change the fact that Mac developers don't need to deal with dependency systems and Mac users never even have to fathom the possibility of a missing/conflicting/etc. dependency. No tool and database to maintain, update = no chance of it not finding dependencies, restricting installation of certain packages, and otherwise getting in the user's way.

      No, it's not perfect, because you can still get that "untrusted" message. But how is OSX any better, especially when it's completely silent about "untrusted" applications?

      OS X is better because you never deal with adding URLs to a repository, for starters. Users will already be confused as to why they have to add a URL to a "repository" (whatever the heck that is) and now the system is prompting them with a warning that suggests they might be doing something very, very wrong. All they want to do is install some software. Why does it have to be so confusing?

      OS X does warn you before running programs for the first time, but it's in the context of downloading a file, not in the context of "setting up their repository", and the warning is also in plain English, so the user can get a good idea of why this might be harmful and what they may want to do.

      You also end up with huge redundancies. Something like KDE which would normally take a few hundred megabytes of storage now takes hundreds of gigabytes. Instead of one copy of Qt and kdelibs you now have hundreds. And double the size for every additional user installing it.

      Have you never seen a system that doesn't use a package manager? Are you familiar with how they work? Look, I never suggested distributing the whole system/OS with the application, or everything above the Linux kernel. You might want to look at OS X. (Read up on it if you don't have it.) Nobody distributes Cocoa/Carbon/etc. with their application because those programs are *guaranteed* to be included with the OS. In fact, there's also Python, Perl, wxWidgets, and a whole slew of other tools that come with OS X out of the box, installed on every system. They aren't "options", they are automatically installed. I hear very few people complaining about the disk space they've "lost" to these components.

      In short, on OS X there's a clear line between what is available on any Mac OS X system, and what you have to bundle yourself. Every software component is one or the other. Any free library expected to be found in more than a few applications should be included, by default, as part of the OS, and Apple often does this. The result - no complicated "dependency checking" system needed at all, and at the same time, small application bundles! It's brain dead simple to understand for developers, and they don't need to put dependency logic into their packages. Disk space is cheap, people's time is not. Which would you think the average user and developer's more interested in maximizing?

    10. Re:Simple, dumb, and easy :-) by jbolden · · Score: 1

      On Mac, as "simple and dumb" as the OS X system is, it *just works* for everyone from grandma to geeks.

      I'm an OSX user. It doesn't just work nearly as well as a package management system. Look at the installation instructions for anything complicated (like eps ghostscript prior to 10.3) or LyX (Aqua version) or QT designer (particularly if you want to use fink QT as well).

      The fact is that a simple package management system like OSX's works well for simple package management issues. Linux has a vastly more complex web of packages than either Windows or Mac and thus their simple solutions aren't appropriate.

    11. Re:Simple, dumb, and easy :-) by kollivier · · Score: 1
      I'm an OSX user. It doesn't just work nearly as well as a package management system. Look at the installation instructions for anything complicated (like eps ghostscript prior to 10.3) or LyX (Aqua version) or QT designer (particularly if you want to use fink QT as well).

      These are basically applications that work on Mac but want/have to use Unix-style installation. They probably have hardcoded Unix path assumptions for dependencies which is something that doesn't need to be done on Mac. They could have packaged it better, and easier, they just chose not to. And they don't really have to because their target audience is software developers, many of whom are probably Unix developers.

      The fact is that a simple package management system like OSX's works well for simple package management issues. Linux has a vastly more complex web of packages than either Windows or Mac and thus their simple solutions aren't appropriate.

      That's not true. What's inappropriate about making installation simple (or simpler)? (Or are you assuming it can't be simplified?)

      The reality is that Linux *exposes the user* to a vastly more complex web of packages than Windows or Mac does. Go file by file through OS X or Windows' system folders and see if it's complex. I guarantee you it is. It's just that, unlike Linux, they don't take their system and break it into 1000 little components, which you are allowed to individually install or not install. In short, the complexity is hidden from the user rather than dumped in the users' laps. It isn't that Linux "just is" more complex, it's that it was explicitly designed that way. And I think that's a major problem for desktop adoption. (It's the primary reason I don't use it.)

      In short, you're saying that some packages are "simple" or "complex", but really what differs is NOT the complexity of the packages (after all, Final Cut Pro, not to mention Tiger, is probably pretty complex but is a simple install), but the complexity of their installation procedures.

    12. Re:Simple, dumb, and easy :-) by Brandybuck · · Score: 1

      It may "magically" work (when it does work without effort, and in my experience it doesn't always work), but it doesn't change the fact that Mac developers don't need to deal with dependency systems and Mac users never even have to fathom the possibility of a missing/conflicting/etc. dependency.

      My point is that you don't have to worry about it under Linux/BSD/Unix either. If you do, you have a bad package manager. Sure the system may break, but you can't tell me OSX is so perfect it's never broke before.

      OS X is better because you never deal with adding URLs to a repository, for starters.

      Who said anything about dealing with URLs? Get your mind off of apt-get, because that's just one of several dozen package managers.

      In short, on OS X there's a clear line between what is available on any Mac OS X system, and what you have to bundle yourself. Every software component is one or the other.

      I distribute a Mac .app package. It includes the Qt library. Why? Because it's not available natively. It would be VERY NICE if there were a native way to check if Qt was already available instead of adding yet another copy, but I've found no way to do it without using a script or other form of (evil windows-like) installation program.

      Now just one or two programs installing extra copies of Qt is fine. But what about dozens? That starts to add up. Restricting development tools to only what Apple distributes is an extreme hindrance to porting software. It's almost like Apple never expected anyone but themselves to write a common application component.

      --
      Don't blame me, I didn't vote for either of them!
    13. Re:Simple, dumb, and easy :-) by kollivier · · Score: 1
      My point is that you don't have to worry about it under Linux/BSD/Unix either. If you do, you have a bad package manager. Sure the system may break, but you can't tell me OSX is so perfect it's never broke before.

      As you say, there are several dozen, each with their own bugs and quirks. The one on OS X has no bugs because it doesn't even exist. I just drag and drop and I'm done.

      As for breakage by packages/installers, well, Mac installer packages could cause that too if you give your password, so it's rather a wash. But consider that many Mac packages don't use installers, and those software installers usually don't (nor should they) alter system directories, while all package manager packages do this (unless they install to someplace like /opt). In practice, then, Linux is more likely to have packages messing with the system, which leads to more chances for (even accidental) breakage.

      Now just one or two programs installing extra copies of Qt is fine. But what about dozens? That starts to add up. Restricting development tools to only what Apple distributes is an extreme hindrance to porting software.

      If Apple sees dozens of apps using Qt, they will probably consider including Qt with their next system update. (And they'll be getting lots of calls to do so.)

      It's almost like Apple never expected anyone but themselves to write a common application component.

      Replace "common application" with "system" and I think you're absolutely correct. Apple makes an effort to keep control over the system and actively discourages touching it, which means less chance of some application writer coming in and potentially messing up my system by accident. +1 from me. :)

      Apple does have frameworks, and you can install them in many places, including "system-wide accessible" or per-user-accessible locations. So, if you wanted to, you could write one of those "evil" scripts that checks for the Qt framework and downloads it and starts the installer if it doesn't exist.

      But I'm figuring you think it's just easier to bundle. As a user, I'd rather have a "complete" package even if my download time's a bit longer, anyways. It's just simple to bundle, and I doubt you can show many occasions where bundling has really hurt a user's system. And there's no doubt it's more error proof and easier to maintain than a package management application and package repository. Apple can spend the time and money that would have gone towards that system improving their software instead.

      So we're back to, is this a real problem for users, or do package managers just really call to the software developer's desire for maximum efficiency even at the cost of a complex system which must be constantly maintained? :)

    14. Re:Simple, dumb, and easy :-) by dodobh · · Score: 1

      This depends on what percentage of shared libraries your main applications link to.

      For example, I have a significant number of applications linked to the OpenSSL libraries. If these were all installed Apple style, I would have to upgrade them all individually (since OpenSSL is not in the base OS image, and should not be).
      With dynamic linking, I just upgrade on library.

      And since I have most of these applications constantly in use, I get considerable savings in memory too.

      --
      I can throw myself at the ground, and miss.
    15. Re:Simple, dumb, and easy :-) by Brandybuck · · Score: 1

      So we're back to, is this a real problem for users, or do package managers just really call to the software developer's desire for maximum efficiency even at the cost of a complex system which must be constantly maintained? :)

      For the same software, I've created an installer for Windows, port/package for FreeBSD, and a OSX app bundle. The hardest was of course the Windows installer. The next hardest was the app bundle. It would have been easier if my app were an Xcode app, but it wasn't, so I had to do a lot of fiddling with the bundle internals.

      I'm not against the app bundle concept. It's perfect for some things. Some people are pushing hard for similar things in Linux/Unix (such as the rox desktop). But it's only useful for end user applications. Which are really only a small percentage of the total software on a system. For most stuff you either need it to come with the system or you need to install it. Think of a web server. I'm assuming Apache comes with OSX. If it does, is it configured started automatically? If it doesn't, is a drag-n-drop to the desktop going to properly install it? Ditto for any other service. Don't like that example, then what about screensavers. At the minimum you have to at least drag-n-drop them to a startup directory. And what about languages like Java, Python, Ruby and Ocaml (OSX can't possibly have every language installed by default)? Are they going to get integrated with Xcode just by dropping them on a user's desktop?

      Apple has done a fantastic job making their computer an appliance. But sometimes you need more than a one-size-fits-all appliance.

      --
      Don't blame me, I didn't vote for either of them!
    16. Re:Simple, dumb, and easy :-) by kollivier · · Score: 1
      I'm not against the app bundle concept. It's perfect for some things. Some people are pushing hard for similar things in Linux/Unix (such as the rox desktop). But it's only useful for end user applications. Which are really only a small percentage of the total software on a system.

      Yes, but outside of developers and system admins, who cares about most of that other software?

      For most stuff you either need it to come with the system or you need to install it. Think of a web server. I'm assuming Apache comes with OSX. If it does, is it configured started automatically?

      It comes installed, but is most certainly not started by default. They know better than to emulate Microsoft's security practices. :)

      If it doesn't, is a drag-n-drop to the desktop going to properly install it? Ditto for any other service.

      I just need to *start* the installed software, which I can do by starting "System Preferences", selecting "Sharing", and checking on the "Web Sharing" check box. Apache now runs. Ditto for SAMBA, printer sharing, AppleTalk/Rendezvous, and other services. All come out of the box, but are disabled by default. If you get the aptly named "Mac OS X Server" product, they have all sorts of additional easy, GUI configuration tools for web servers and such.

      Don't like that example, then what about screensavers. At the minimum you have to at least drag-n-drop them to a startup directory.

      Those have installers so that the users don't need to worry about where to drag/drop it. Similar to MS wizard installers.

      And what about languages like Java, Python, Ruby and Ocaml (OSX can't possibly have every language installed by default)?

      Well, it doesn't have Ocaml. (Or, at least I haven't seen it. ;) But then again, you forgot to mention Perl and AppleScript, and now Dashboard widgets (CSS/JS). All these are installed in every OS X machine. It even includes wx bindings for Python and Perl, as well as a CoreGraphics Python extension. In short, it most certainly does have all that stuff.

      For other stuff, a Mac installer can be made.

      Are they going to get integrated with Xcode just by dropping them on a user's desktop?

      Out of the box XCode does things like Python syntax highlighting so it's already somewhat integrated. And there are lots of tips on further integrating XCode and Python, though honestly I like BBEdit so much I rather stick with that for my Python coding and thus can't speak much on this topic.

      So how does package management beat this?

      Apple has done a fantastic job making their computer an appliance. But sometimes you need more than a one-size-fits-all appliance.

      Outside of building a highly customized distro for server or embedded use, or installing on ancient computers, I don't see why one-size-fits-all wouldn't work. Works great for me. Those that criticize the approach almost always haven't tried it.

      And all computers are appliances. They exist solely to help people accomplish tasks. The only comparison between computers is how easily and quickly they let the user accomplish a particular task, or how reliably they provide a service.

      But honestly, at this point we're just trying to poke holes in each others' arguments. You talk to me like I've never dealt with all the things you mention above, and that somehow I will all of a sudden realize that "hey, Mac OS X doesn't do that well". I've been using the OS for 4+ years. I've run web servers, tested database-backed sites with it, and I share files every day between Linux, Windows and Mac boxes. I regularly do Python and C++ development and work with CVS, SVN, etc. And I still see no need for a package manager. I don't even use the ones that are available.

      I, on the other hand, feel like most Linux users simply can't comprehend a computer without a package manager working correctly or efficiently, but then again, if I used Linux as my primary OS, maybe I'd feel that way too. :) I dou

    17. Re:Simple, dumb, and easy :-) by Brandybuck · · Score: 1

      Those have installers so that the users don't need to worry about where to drag/drop it.

      Hah! I knew it! :-)

      --
      Don't blame me, I didn't vote for either of them!
    18. Re:Simple, dumb, and easy :-) by jbolden · · Score: 1

      You're right given the way you are phrasing this, " they don't take their system and break it into 1000 little components, which you are allowed to individually install or not install." And the more I think about it the more I think this is probably the better default handeling. Make the 1000 pieces version the pain in the neck non default and let most people just drag and drop.

      I still do disagree with, In short, you're saying that some packages are "simple" or "complex", but really what differs is NOT the complexity of the packages (after all, Final Cut Pro, not to mention Tiger, is probably pretty complex but is a simple install), but the complexity of their installation procedures.
      I'd say more its the complexity of the culture. The Linux culture wants the 1000 little pieces and Windows and Mac culture wants the all in one big package. For example Fink could install a huge number of binaries by default (say 8 gigs worth or something) and then have application menus that really make sense. Its the culture not the installation procedure that prevents that, Linux/Unix people would see it as a bad thing.

    19. Re:Simple, dumb, and easy :-) by kollivier · · Score: 1
      You're right given the way you are phrasing this, " they don't take their system and break it into 1000 little components, which you are allowed to individually install or not install." And the more I think about it the more I think this is probably the better default handeling. Make the 1000 pieces version the pain in the neck non default and let most people just drag and drop.

      For the strategy of things like drag and drop to work, the "1000 pieces" version must be a totally separate OS. Because once you say "OK, user A may install everything, but user B might pick and choose" you're back to the problem of "how can we guarantee that *anything* is on the machine" and if we can't do that, we need a package management system to check things for us. But so long as they are totally separate versions of the OS (one for business use, one for embedded/server/hobbyist use), then I think that's fine.

      I'd say more its the complexity of the culture. The Linux culture wants the 1000 little pieces and Windows and Mac culture wants the all in one big package. For example Fink could install a huge number of binaries by default (say 8 gigs worth or something) and then have application menus that really make sense. Its the culture not the installation procedure that prevents that, Linux/Unix people would see it as a bad thing.

      IMHO, it's not so much culture as target market. The people that use Linux do so because it does what they want it to do. So the product that exists gathers like-minded people, and eventually you see trends and commonalities among Linux users. If some Linux distro releases a default, "batteries included" install that just works, most of the current Linux users probably will shun it, but on the flip side, lots of businesses and home users will start to embrace it if it delivers on it's promises.

      Sometimes someone has to go against the needs/desires of the current target market in order to open up new ones. OS 9 users weren't particularly happy about the OS X switch, but Unix geeks and Windows 'switchers' were. I couldn't have used OS 9, but I can use OS X and I do use it every day. So by changing the product, you change the target market and thus the 'culture' of the people supporting it. You see less Mac zealots, and more "I use Mac to get my work done" people, and that's directly a result of a change in direction by Apple.

      IMHO, someone will always make a Linux, do-it-yourself, 1000 piece installer kit. And I think that's great. But if Linux wants to grab new target markets and market share, someone's going to have to go against the build-it-yourself philosophy of Linux and make something more akin to Apple and Microsoft's desktop offerings. (Of course, hopefully learning from their mistakes rather than repeating them!)

    20. Re:Simple, dumb, and easy :-) by jbolden · · Score: 1

      IMHO, it's not so much culture as target market. The people that use Linux do so because it does what they want it to do. So the product that exists gathers like-minded people, and eventually you see trends and commonalities among Linux users. If some Linux distro releases a default, "batteries included" install that just works, most of the current Linux users probably will shun it, but on the flip side, lots of businesses and home users will start to embrace it if it delivers on it's promises.

      Xandros for example pretty much does this. They have a very thick set of packages which they include by default (including stuff like cross-over office, a mandatory desktop environment...). They are actually well liked by the Linux crowd, and would be more popular except:
      1) They don't release their own software open source
      2) They charge for the distribution

      So it does seem that the Linux will allow a distribution to be thick. OTOH what they seem very strongly opposed to is this passing beyond the distribution level (for example when Gnome tried to establish cross distribution requirements pretty much no one supported them). "mechanism not policy" is still the Unix culture.

      Sometimes someone has to go against the needs/desires of the current target market in order to open up new ones. OS 9 users weren't particularly happy about the OS X switch, but Unix geeks and Windows 'switchers' were. I couldn't have used OS 9, but I can use OS X and I do use it every day. So by changing the product, you change the target market and thus the 'culture' of the people supporting it. You see less Mac zealots, and more "I use Mac to get my work done" people, and that's directly a result of a change in direction by Apple.

      I'm one of those too. I went from a Apple hater to a guy who uses one everyday. But I don't see OSX and OS9 as anything other than simply different products from the same company.

      IMHO, someone will always make a Linux, do-it-yourself, 1000 piece installer kit. And I think that's great. But if Linux wants to grab new target markets and market share, someone's going to have to go against the build-it-yourself philosophy of Linux and make something more akin to Apple and Microsoft's desktop offerings. (Of course, hopefully learning from their mistakes rather than repeating them!)

      As I mentioned above they already have. The big issue is though that Linux splits into lots of different distributions and so Linux as a whole remains highly do it yourself. Which means that applications need to be configured at the distribution level ....

  131. Yet Another Desktop, Yet Another Windows Manager by Anonymous Coward · · Score: 0

    I don't see anything revolutionary here. This is just another distro with another organized desktop, and another window manager. They don't get it. The goal is not rethinking the desktop, we have to kill the desktop.

    And what really makes me angry: they call their debian & knopix like distribution a new operating system: SymphonyOS. Misleading.

  132. Ubuntu by mushupork · · Score: 1

    Ubuntu is another great Debian distro. I switch between this and Mac OS X. The Mac is much prettier to look at, no question, and all devices work out of the box, no question (they develop the box and the OS.) With Ubuntu, I like the cost (free) and that I feel I truly "0wn" my PC. But it does take a couple weeks of tweaking to get it running at the same level of compatibility as my Mac.

    Given my recent iBook horrors lately (loose video chip) I don't know if I'll ever plonk down premium $$$ for Mac hardware, given "you get what you pay for" doesn't necessarily apply to Apple hardware anymore. Instead, I may from now on just get a barebones AMD or Intel and slap a pretty Debian distro on it.

    --
    Currently bidding on sig
  133. For the love of all that is holy, MOD PARENT DOWN by Anonymous Coward · · Score: 0

    What retard moderated that "interesting"?? It's a link to a fucking comic strip for god's sake!

  134. Darwin and Aqua by simpl3x · · Score: 1

    Isn't the difference between Darwin and OS X the interface layer? And, if it is now going to be specifically an x86 product, meaning that the Altivec layers are unnecessary, wouldn't it be easier to create a free interface layer? So long as all of the interface elements are included, an application should run on Darwin as well as on OS X.

    I'm not quite sure how Apple plans on balancing this. Hell, OpenStep still exists. It seems that Apple could provide a lite version of OS X for installation on commodity hardware pretty easily. This would give Microsoft quite the scare if it was possible to install this with Windows or as a partition allowing Windows to run within it. Things are about to get very starnge!

  135. Package Management Systems by ajs318 · · Score: 1
    When it comes to package management systems, I have seen just two that I really like. They are Debian's apt and Gentoo's portage. The latter wins by a whisker because it uses source tarballs; but Debian has source packages too, if you need them.

    I tried using RPMs when I was using Mandrake. All I ended up doing was saying "Sod that!" and learning how to compile from a source tarball. Of course, it's probably not completely insignificant that both Debian and Gentoo are famous for the sheer number of packages they provide, whereas Mandrake -- Mandriva nowadays -- was more about making it easy {at least, easy to do what they ever envisaged you doing}. I can't really knock the Mandrake guys: the simple fact is, I outgrew their distribution.

    Source.tar.gz with autoconf and automake really is the "proper" way, whatever anyone else says. Adding new package formats to combat the proliferation of package formats is a bit like fighting for peace, or shagging for virginity.

    Getting back to topic here, I really don't think that Apple are threatening Linux users. On the contrary, I think that Apple are going to have a very hard time moving into the 80x86 market.
    • Microsoft sell software to businesses in the first world. {Private individuals in the first world, and everyone in the third world, use mainly pirated software.}
    • Apple sell hardware and software. Apple software does not get pirated much, but there is a good reason for this: it is useless without Apple hardware. If Apple OS XI will run on "standard" 80x86 hardware, of the sort currently used to run GNU/Linux, Windows and FreeBSD, then Apple will have to accept that piracy will be inevitable. And probably rampant.
    • The Free Software and Open Source communities do not in general have to worry about piracy. The only way FOSS can be "pirated" is if a commercial developer releases a closed-source derivative of an Open Source program. Even then, the original must obviously remain Open Source.
    Add to this that it will soon be genuinely worth the effort of reverse-engineering hardware drivers; and there is bound to be at least one country in the world where this is not only not illegal but a protected right. It really might not be long before some new player muscles in with an Apple OS look-alike, probably based on FreeBSD {like Apple OS was} and including reverse-engineered drivers for all the spiffiest hardware.

    I really don't see how Apple can succeed by moving into the 80x86 market. It strikes me as being a bit like deciding to build a pay toilet in a forest.
    --
    Je fume. Tu fumes. Nous fûmes!
    1. Re:Package Management Systems by zpok · · Score: 1

      I don't know too much about windows piracy, but I can assure you that on the other side of the distortion field the tradition of installing a copy on your friend's/parent's/children's computer is very much alive, as is the downloading of pirated soft on peer to peer.

      I don't see that changing because of the processor alone, people will always have interest in solid pirate versions, or illegal copies of original software, but the group of mac people who want to suffer strange stuff is pretty small, so people who're extremely into their computer and can move beyond those quirks through skill wouldn't be a target market for Apple anyway.

      You'd be surprised at the number of people who buy simply to have access to support.

      If those "faithful" are not enough to save Apple, I'd like to point out that one thing that made MS so successful was it's ease to pirate. I remember the time I could only play a game if I carefully compared a set of symbols to words in the printed manual.

      Meanwhile, Windows 3.11 and Office asked for a stupid serial number.

      --
      I think, therefore I am...I think.
    2. Re:Package Management Systems by ajs318 · · Score: 1

      The only people I know who buy original Microsoft software are our Accounts department, who still need it for some legacy application they have to run for compatibility with Group head Office. The rest of the business runs on Linux -- Mandrake or Mandriva as it is now for desktops, and Debian for servers {we used to use Slackware, but apt-get is just so nice. It's also possible we'll be trying Gentoo at some point in the future}. Everybody I know who has a Windows box at home is running a pirated copy of Windows.

      Microsoft can afford to stand piracy. Apple probably cannot. Piracy is what killed off the independent software companies, but not for the reason most people think.

      If you're selling a £50 program and Microsoft are selling a £500 program which does roughly the same, what do you think people are going to do: buy the £50 one and save £450, rip off the £50 one and save £50, or rip off the £500 one and save £500? It's a manifestation of the hunter-gatherer instinct. To a dog, stolen food tastes nicer. To a human being, paying full price is cheating. It's the same instinct that kept cave-man alive.

      Simply by having enough cash reserves to tolerate piracy to such an extent, Microsoft have all but eliminated the competition. Only the Open Source Community, which has close to zero piracy {just the likes of CherryOS and certain router manufacturers}, is in a better position.

      --
      Je fume. Tu fumes. Nous fûmes!
    3. Re:Package Management Systems by zpok · · Score: 1

      OK, I agree, up to a point. What you're saying is that people who don't at any cost want to pay for apple computers are going to pirate OS X.
      First of all, we're not sure how much Apple hardware will cost, but if the last few years are any indication, it'll be competitive. They normally stop to be so after intel has caught up. That problem should be eliminated, and they'll be able to (will have to) refresh their existing lines faster in order to keep ahead of Dell (not on full rebate, normal prices).
      So the group of people who are going to pirate are those who aren't interested in Apple hardware - and my guess is, also not in Dell's hardware. Their friends will have the opportunity to either go their way and discover problems of incompatibility are not solely the domain of the OS or they can go out and buy a mac (what? It can happen ;-)
      I don't know, I fail to follow your prediction through to its logical conclusion, but I do agree that Apple can't tolerate piracy. I also agree that Linux falls completely outside that market logic, but unless Linux becomes more AUF (average user friendly, ehehe) I only see an added advantage for Apple, namely that more people will want to run their linux on Apple hardware, or even their FOSS on OS X.
      Which I think is nice for all concerned and won't be a threat to linux at all.
      btw, I've been so bad at predicting this whole mac intel thing that I'm very cautious with words like never, of course, evidently, ... you get the gist.

      --
      I think, therefore I am...I think.
    4. Re:Package Management Systems by ajs318 · · Score: 1

      I really don't think Linux isn't "average user friendly". Of course I'm biased, being a fully paid-up penguin-shagger. But if you could get a machine pre-installed -- so the user never has to see the "scary" install process -- with something like Ubuntu and all the usual packages {OpenOffice.org, Firefox browser, Flash plugin [there soon will be a Free Flash alternative which may be worth investigating], Evolution mail client / personal organiser, Gaim internet messenger, maybe even FUSE to satisfy the retro-gaming instinct, GCC and some necessary libraries for compiling .tar.gz files} then you're suddenly on a par with an out-of-the-box Windows installation -- or even almost a Mac.

      Average users don't install Windows. I have done this and it was no easier than installing Linux -- in fact, some Windows versions will refuse to install on a machine that has ever had Linux on it, because the Windows fdisk is totally christian. {Solution: use Linux fdisk [on bootable CD] to change all existing partitions to some FAT variant first, then wipe 'em out.}

      Installing software packages can look complicated, but with Ubuntu or Debian it's as simple as opening an Xterm and typing sudo apt-get install foo. Hell, even with Gentoo -- yes, the one that's so manual, it makes Deb and Slack look automatic, but once it's installed it just runs sweet as anything -- you can just substitute emerge for apt-get.

      --
      Je fume. Tu fumes. Nous fûmes!
  136. Re:Until Apple announces OSX for non-Apple machine by Princeofcups · · Score: 1

    > Apple are staking their entire company on OSX not being pirated to other x86 platforms. OSX will not
    > support any non-Apple hardware, so it's not a threat, unless you count possible increased Apple
    > market share due to lower prices.

    I don't think so. People who pirate OSX will mostly be current Windows users who already own PC's, not Mac owners or potential Mac customers looking for cheap hardware. They will be the people who never would have bought Mac hardware anyway. Does this hurt Apple? Just the opposite. It shows off OSX to a whole group of people who never would have touched it.

    Now if Apple were expecting to make money selling OSX licenses for generic PCs, then pirating might hurt their bottom line.

    jfs

    --
    The only thing worse than a Democrat is a Republican.
  137. Linux? Desktop? Riiiiight. by Frobozz0 · · Score: 1

    An open source desktop will never become dominant. This isn't a battle of Mac vs. Linux. This is Linux being more appealing ot it's limited crowd of enthusiasts.

    Linux is nice. It's a great server OS. If you're a hobyist you'll consider it on the desktop. But I can't see how it'll ever be anything else.

    --
    "Politicians find new names for institutions which under old names have become odious to the people."
  138. Torrent and HTTP download available by Anonymous Coward · · Score: 0

    A torrent is available here and a HTTP download here.

    Please join the torrent if you can!

  139. s/Opera/Orchestra/ by TuringTest · · Score: 1

    Sorry, the name of the underlying XUL/Perl environment is Orchestra, not Opera.

    --
    Singularity: a belief in the "God" idea with the "demiurge" relation inverted.
  140. Not root? Sudo? by poptones · · Score: 3, Insightful

    If they should not have to be root and not even have to type in some form of confirmation that yes, I want to add this PROGRAM to my computer, what?

    This is how windows has worked for ages and it's the most common way to own a system - it's so incredibly easy to install something, just click and bang and we own u.

    It's not hard to type a password when installing an app. It tells the user they are doing something to alter the fucntionality of their machine and it tells the machine this is what the user wants to do.

    1. Re:Not root? Sudo? by Anonymous Coward · · Score: 0

      I fully agree with you. People complain about all the spyware/adware/viruses that you can get in windows and say how it can't happen in linux based systems because it isn't as simple to install a program and have access to the system like it is in windows. But here are people now saying that Linux should addapt the anybody can install anything stand point and become more like windows.

      as for the home / corp user discussion in other posts. Home users would know the root password as they setup the box and therefore not have any trouble typing it in.

    2. Re:Not root? Sudo? by mpe · · Score: 1

      This is how windows has worked for ages and it's the most common way to own a system - it's so incredibly easy to install something, just click and bang and we own u.

      Typically without the "bang" or any indication that the operation of the machine has been changed. One thing Windows often does is to blur the distinction between executables and data. Which has been exploited in the past to trick users into running programs when they though they were opening data files.

    3. Re:Not root? Sudo? by Anonymous Coward · · Score: 0

      Are you kidding? In Windows, you have to be root called Admin! What version did you find that did not have the superuser install your software?

    4. Re:Not root? Sudo? by Qzukk · · Score: 1

      Thats funny, I just dropped putty.exe on my desktop and it ran. There are plenty of programs for windows that don't require Administrator to install, they're all simple little things that don't require writing to system directories.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
  141. BINGO! Re:What's so wrong w/ KDE or Gnome by CETS · · Score: 1
    You hit the nail on the head. Everybody I know who has tried and taken the time to learn it ends up enjoying it.

    But...not everyone wants to take or thinks they should have to take the time. It's a consumer level attitude, but it's one that M$ has come closer to meeting (monopoly reasons etc. doesn't matter..) than the Linux community has. Until it's easy enough for the consumer relative to Windows, which I don't believe it is yet, things won't change.

    1. Re:BINGO! Re:What's so wrong w/ KDE or Gnome by FooBarWidget · · Score: 1

      By that logic, Linux desktop will never (in the most extreme sense of the word) be ready for the desktop, because it's always different from Windows. If consumers don't want to learn anything new, then you can never win unless you are Microsoft.

  142. if anything, the other way around by cahiha · · Score: 1

    The article fails to make a plausible argument in which OS X would be a threat to Linux any more now than it was before.

    Apple's laptops and desktops are already sexy, not too expensive, and fast enough. This move won't entice any new users because it won't change the user experience appreciably. Almost anybody who prefers OS X to Linux will already have switched. Basing their machines on Intel chips won't change that equation.

    What switching to Intel will accomplish is that it will make Macintosh hardware a nicer platform for people like me, people who prefer Linux but like the look of Apple hardware. With PPC, Macintosh was a second-class Linux machine because a lot of Linux software would not run on it; with x86, it's a great alternative to PCs.

    Another big effect of switching to Intel processors is to dilute Apple's distinctive brand. It may mean more software availability for OS X (via Linux emulators, easier ports in particular of compilers), but that software won't be OS X native software.

    1. Re:if anything, the other way around by zpok · · Score: 1

      "Another big effect of switching to Intel processors is to dilute Apple's distinctive brand. It may mean more software availability for OS X (via Linux emulators, easier ports in particular of compilers), but that software won't be OS X native software."

      I wouldn't think so. It's a proven fact that programs that don't adhere to Apple's (everchanging) guidelines don't really get a great following. You're basically saying that people won't mind confusion when the big majority of these people chose their computer just to avoid that. Can't speak for the millions of switchers coming our way (ahahaha) but your average mac user is a pain in the nether regions when you take away the stuff lots of people dismiss as "eye candy".

      Look at it as an oportunity to spend just a leeetle more time on the interface, so that at least you get the logic right if not the looks since you won't have to recompile so much.

      Looks are important, but if a skin would do the trick, you would see much more use of FOSS on the mac.

      --
      I think, therefore I am...I think.
    2. Re:if anything, the other way around by cahiha · · Score: 1

      The reason there isn't more FOSS on the Mac is because porting to it is a pain. And Apple likes it that way. Just look at what happened with OpenOffice: Apple sabotaged any solution other than a native port.

      Apple is scared stiff that if they make it easy to port FOSS GUI applications to Macintosh, the platform will lose its developers and its distinctiveness. And they are probably right to be scared. But it won't help.

    3. Re:if anything, the other way around by zpok · · Score: 1

      Yeah man, I feel your pain... but I'm from the church of Steve. And to imply that they are scared to lose its distinctiveness is to seriously not understand what religi- um the mac is about.

      I like the idea of linux, but as long as it's not aimed at my activities, and Apple is, I'll "go the blessed path of Ives towards the holy light of Steve".

      --
      I think, therefore I am...I think.
    4. Re:if anything, the other way around by cahiha · · Score: 1

      Yeah, and I like the idea of OS X, as long as I don't have to use it myself. That's why they make different operating systems. If only the Macadvocates would remember that.

    5. Re:if anything, the other way around by zpok · · Score: 1

      Well, to be honest with you, I find that every OS has its advocates, and maniacs and fanboys and whatever. And generally it goes "If only they (the "other OS users") would stop being so obnoxious.

      Fun, sometimes. Depressing generally. And making jokes about it is like spitting in the face of God or something. As if there weren't any ahem, important things in life.

      Rant over, have a nice one.

      --
      I think, therefore I am...I think.
  143. Sometimes, brute force is better by Nice2Cats · · Score: 1
    The simple & dumb way as OS X handles packages is just that: it can not handle dependencies, or anything, it just puts some files on your computer.

    As someone who has switched his desktop machine from first SuSE Linux, then to Gentoo Linux and then on to OS X over the last couple of years, let me say this: Screw dependencies, screw dynamic linking, just install the damn files. Hard disk space is cheap, and for me as a user, it's hard to think of something that is easier than just dragging an icon from the source medium to my Applications folder. My time is more valuable than any other resource involved here.

    Maybe it isn't elegant under the hood, maybe it is a waste of resources. But it works, and it's simple to use. Sometimes, brute force is better.

  144. It would suffice... by Anonymous Coward · · Score: 0

    ... that we'd have a smooth-working, secure, free, light graphical PC&PPC OS (Linux 2.6) with a browser, e-mail client and an automatic binary patch update system. Even package management is irrelevant. Just make a single package which is installed by choosing a destination drive.

    Competition? There's no such thing. Even Windows 3.11 is more user friendly than KDE (or gnome, god forbid). Linux on the desktop is a nice idea but it apparently takes some serious $$ to develop a decent GUI (or maybe it's just the X approach).

  145. Apple will achieve what IBM could not. by reporter · · Score: 1
    Apple will achieve what IBM could not. Namely, Apple will put a free UNIX onto the desktop in a major way. The switch to the Intel platform will significantly lower the cost of the Apple desktop and notebook, and they will proliferate. Further, peripheral suppliers will soon sell special add-ons that will allow standard PC clones to run the Apple x86-based Mac OS.

    These two paths will cause free UNIX to rival Windows.

    Linux, however, will encounter trouble. The free UNIX movement will soon face the same issue that the commercial UNIX movement faced. Namely, there will soon be 2 dominant free variants of UNIX, and they will not be compatible with each other. The free UNIX market will be fractured in the same way that the commercial UNIX market was fractured.

    The right thing to do is to merge freeBSD UNIX (on which Mac OS is based) and Linux and put the combined UNIX under the control of the Open Source Development Lab (OSDL). The second best choice is simply to convince Apple to drop freeBSD UNIX and to base future Mac OSes on Linux. In exchange, Linus agrees to surrender control of Linux to the OSDL.

    Either way, Apple becomes a ripe takeover target for IBM, which has been salivating at the possibility of putting Linux (or a free UNIX) on the desktop .

    1. Re:Apple will achieve what IBM could not. by Anonymous Coward · · Score: 0
      You've quite a few problems in your argument. First of all, Apple have stated Mac OS won't be licensed to run on non-Apple machines. Secondly, Mac OS isn't free, in either cost or source access. Thirdly, Apple couldn't switch from BSD to Linux without putting the whole Mac OS under the GPL (something it would never do, especially now that it's using x86).

      As for IBM taking over Apple, even if it did make business sense, I don't think Steve Jobs would be happy as a mere division manager at IBM. Without Steve Jobs, Apple wouldn't be worth much.

    2. Re:Apple will achieve what IBM could not. by geminidomino · · Score: 1

      Good luck with that. FreeBSD doesn't do the whole "Free as in what we say freedom is" spiel, so wouldn't fit nicely under the GPL, and linux has so many contributors that it will never be able to be under anything BUT the GPL.

      Too bad, really. A commercial linux distro could make a world of difference with things like hardware support.

  146. My theories about OS X by UnknowingFool · · Score: 1
    By switching to Intel, Apple is undermining Microsoft in subtle ways. While Apple was still in the PowerPC computer market, comparing Windows to Mac OS X was always oranges and apples (if you forgive the pun). Microsoft could deflect any direct comparison (as could Apple). Now that Apple will be in x86 land, there can be more direct comparison. If Apple puts out a superior product that is more secure, more stable, more reliable, and easier to operate on nearly the same platform, Microsoft will feel the heat.

    Another way Apple is undermining MS has to do with the Xbox 360. It is built on PowerPC chips and E3 showed that the development machines for Xbox360 games are Apple G5s. By switching to Intel, Apple creates an obstacle to developing Xbox 360 games. True, deveoplers could use PowerPC emulation on Intel, but there are always technical problems with that approach. Eventually it will work but it will take time.

    Alternatively, developers could use an IBM PowerPC machine, but IBM sells those at a premium ($5000+) Game companies are forced to buy G5s that are at the end of their cycle or very expensive IBMs. The expensive and obstacles will discourage development as some game makers may not want to put in capital to develop games.

    Just my $0.02.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  147. Re:Until Apple announces OSX for non-Apple machine by Anonymous Coward · · Score: 0

    Slashvertisement.

  148. do your homework by cahiha · · Score: 1

    Both of the aboves gives you a pretty good summary of why Debians way of handling packages isn't really any good in the long run.

    Select in the menu bar Applications > System Tools > Synaptic Package Manager. It prompts you for the system admin password. Then you get point-and-click simplicity for installs.

    It's a GUI interface just like you would be using on Macintosh if Macintosh actually had decent package management.

    First of you can't install a application as a user, now how stupid is that?

    The Debian package manager has provisions for that, but people usually don't bother.

    Software packaging should be done by those that provide the software in the first place, the distro might run a quality check on it, but thats it.

    And that's why you can point your Debian feeds at whatever source you like. For example, Adobe could provide a Debian feed for Photoshop. And that capability is widely used.

    1. Re:do your homework by grumbel · · Score: 1

      ### Select in the menu bar Applications > System Tools > Synaptic Package Manager. It prompts you for the system admin password. Then you get point-and-click simplicity for installs.

      The point is not that its hard to become root, but that its impossible to install software in the user space. GUI or CLI isn't a problem.

      ### The Debian package manager has provisions for that, but people usually don't bother.

      Ok, please enlight me how I can install something in my home directory via apt-get? Sure I can try dpkg-deb and use a hex editor to get rid of the often hard-compiled path in the binary to make it work in my home directory, but thats not really what I call easy to use.

      ### For example, Adobe could provide a Debian feed for Photoshop.

      They should provide a package for Linux, not specifically for Debian. Sadly Linux still hasn't a standard form to disto independendly package something, so the companies use self extracting scripts, tarballs, rpms and other unpleasant stuff. Maybe autopackage or lsb-rpm will help one day, but not anytime soon.

    2. Re:do your homework by cahiha · · Score: 1

      Ok, please enlight me how I can install something in my home directory via apt-get?

      Check the man pages for apt-get and dpkg. However, it won't work well, not because apt doesn't support it, but because it's a bad idea.

      The correct solution is either to use union mounts or user-mode virtualization, or just to give users limited privileges to install new software globally, depending on the environment. Both are widely used for this purpose.

      They should provide a package for Linux,

      No, they shouldn't. They probably will, at some point, but they shouldn't because that would reduce Linux to the same kind of mess that Macintosh is reduced to.

      Sadly Linux still hasn't a standard form to disto independendly package something,

      So, why don't FreeBSD, CMU Mach, and OS X have a distro independent package system? In fact, the Macintosh operating system is so inconsistent that I can't even run my Macintosh applications on CMU Mach or FreeBSD. Obviously, if Apple can't get that right, Macintosh isn't ready for the real world yet. No wonder it has a smaller installed base than Linux...

  149. Slashdotted by debiansid · · Score: 1

    There goes SymphonyOS. The site has reached its bandwidth limit.

  150. Careful... by eno2001 · · Score: 1

    I think a lot of folks in the for-profit world of software are trying to create discord by pitting Mac OS X *nix against Linux *nix and vice-versa. Keep in mind that technically, *nix is *nix. But practically and economically, Mac OS X is targetted at a different set of people than Linux and BSD. Don't let all of these new Apple on Intel stories make you think that Mac OS X is going to take anything away from the Linux and BSD crowds. Mac OS X can do nearly all the things that the other two *nix like OSes can except: be given away without charging money. That is what attracts most non-*nix people to Linux and BSD in the first place. Once they really get into it, then they see little reason to switch with the exception of the gloriously beautiful UI that Apple has on it's desktop.

    --
    -"...bad old ideas look confusingly fresh when they are packaged as technology" - Jaron Lanier (Digital Maoism on Edge.o
  151. Windows XP installer sucks less than Macintosh by cahiha · · Score: 1, Interesting

    Thirdly, *what* Windows XP package manager?

    The thing that you can find in Control Panel > Software. It's far from perfect, but at least it lets me see all the installed software on a system and remove it with a single mouse click. It's not as nice as Linux package managers, but it's a whole lot nicer than Macintosh, where I have to go hunting around the file system and can never be sure whether dragging the application into the trash will actually remove all traces of it (in fact, it won't).

    Secondly, my post pointed out that Windows tends to fall flat with mislinked associations, broken application, and other "minor" issues that are quite annoying to users.

    Macintosh and Windows both permit, but don't require, applications to modify global system directories on install. Applications that do will be susceptible to this on either platform. So, there is no intrinsic difference between Windows and Macintosh in this area.

    1. Re:Windows XP installer sucks less than Macintosh by AKAImBatman · · Score: 2, Interesting

      The thing that you can find in Control Panel > Software.

      I don't have a "Software" icon. I assume you mean "Add or Remove Programs"? :-)

      If so, be aware that it is *not* a package manager under the definition I gave. If you're not clear on what a package manager is, please reread the description I gave in the grandparent post.

      And I have to disagree about it sucking less than OS X. Under OS X, I just drag the applicaiton to the trash and empty it. No more program. Under Windows I have to use an uninstall program that rarely even removes all of the program files, much less extraneous files left behind.

      The only weakness on OS X is the installer. However, that installer is almost never used for user programs. Only Unix utilities and system updates use it. Most users will ignore any desktop program that comes in an installer. (Which usually just builds an APP folder anyway, but the develoers didn't understand Mac distribution.)

    2. Re:Windows XP installer sucks less than Macintosh by Ageless · · Score: 1

      Dragging an application to the Trash will not delete anything the application has created such as user preferences. It's a valid argument to say the user might not want them deleted, but they should at least be given a choice.

      Even worse is if you've installed third party drivers (my Brother laser printer driver comes to mind), kernel extensions, screen savers, preference panes and anything else that must be installed outside of an .app file. These kinds of things are very difficult for the average user (and even the not so average user) to get rid of without some kind of system keeping track of what's installing what and where.

    3. Re:Windows XP installer sucks less than Macintosh by AKAImBatman · · Score: 1

      Dragging an application to the Trash will not delete anything the application has created such as user preferences. It's a valid argument to say the user might not want them deleted, but they should at least be given a choice.

      This is very true, however NO scheme currently exists that will delete user data. Windows installers have the option, but precious few ever take that step.

      Even worse is if you've installed third party drivers (my Brother laser printer driver comes to mind), kernel extensions, screen savers, preference panes and anything else that must be installed outside of an .app file.

      This is still considered one of the biggest failings of the OS X install system. However, it doesn't matter too much in everyday use. The bigger issue is still the programs that everyone uses every day. OS X handles desktop programs beautifully, Windows handles them poorly but in a workable fashion, and Linux Distros just pretend to be handling them.

    4. Re:Windows XP installer sucks less than Macintosh by Jon-o · · Score: 1

      Pretends to handle them? I'd say many distros do a fine job - 'aptitude install openoffice.org' and it's all there, 'aptitude remove (or purge) openoffice.org' and it, and all its unused dependencies are gone.

      The problems only start when you get software that isn't packaged yet, or if you don't have a good net connection, or another quick way to access a good archive with what you need. That's something that could be improved, I suppose. But more and more, that's not an issue at all.

    5. Re:Windows XP installer sucks less than Macintosh by BasilBrush · · Score: 2, Insightful

      No application uninstall operation should ever delete user data, including user preferences. For a consumer oriented desktop, asking the user isn't an option because they probably won't understand the questions, if they even bother to read it. The right this to do is to have removal of an application and user data as two separate actions that the user might choose to do. At it's best, OS X has the right approach. It's just not consistent enough across all apps.

    6. Re:Windows XP installer sucks less than Macintosh by MrLint · · Score: 2, Insightful

      The preferences issue is not really so much an issue, as a 'thing'.
      By this I mean that throwing away an app doesnt clean up its (usually) one small pref file, isnt really a big deal, as in comparison to the windows registry. The registry is actively 'marketed' as the place to keep application prefs. IMHO its insane to keep user application prefs in a system structure that is loaded into memory at boot time. On top of that many apps that have installers dont do a good job of cleaning up after themselves.

      So you have a branch in a system structure that make a user cry, and isnt recommended that they access to clean up, that is loaded into memory for apps that may no longer exist.

      *OR*

      Usually small pref files in the users home directory that are named for the app that they came with that are sitting unused on big secondary storage devices.

      I'll gladly take the latter of 2 evils.

      The rest is valid, sorta. Most things do not install kexts, Drivers for hardware, are well drivers. they arent loaded unless needed. That only becomes an issue if there is a compatibilty problem with a old diver version, and with something like printers reinstalling overwrites. As for prefpanes, most (not all anti virus for example) are things that users tend to isntall manually, and they have instructions on where to put them. If someone cant figure out how to reverse.. well *shrug*

      And the extra bonus is that all of these things are generally in well named folders so you know what to expect in there. While its not really automated; and not exactly trivial; its still a far cry from a nameless xxxxxxxx.scr or .dll

    7. Re:Windows XP installer sucks less than Macintosh by thatguywhoiam · · Score: 3, Insightful
      The thing that you can find in Control Panel > Software. It's far from perfect, but at least it lets me see all the installed software on a system and remove it with a single mouse click. It's not as nice as Linux package managers, but it's a whole lot nicer than Macintosh, where I have to go hunting around the file system and can never be sure whether dragging the application into the trash will actually remove all traces of it (in fact, it won't).

      Now that is truly a heroic reach.

      You mean to tell me, that dragging the application's icon to the trash is somehow less logical to you than locating a Control Panel that will 'teleport' it off your system?

      'Single-click' = click icon, drag to trash.
      'many-click' = click Start, click Control Panels, click Add/Remove Applications, click down scroll arrow to desired app, click app, click Remove.

      Look, the Add/Remove thing is stupid. There is no good reason in this day and age that the OS cannot figure out what I want to do when I drag an app to the trash/bin.

      And you are wrong about 'traces' of an app - the only thing left behind is the .plist file, which is all of 4k.

      There are good things to pick on in OS X, but application installing/de-installing is not one of them.

      --
      If Jesus wants me it knows where to find me.
    8. Re:Windows XP installer sucks less than Macintosh by cahiha · · Score: 0, Troll

      Under OS X, I just drag the applicaiton to the trash and empty it. No more program.

      Yeah, the program is gone, but the install isn't necessarily gone. The software may have modified system settings, installed shared libraries, installed daemons, changed file associations, and done a lot of other things. Other software may depend simply on being able to invoke the application. Dragging .app directories into the trash is playing Russian roulette with your system.

      Most users will ignore any desktop program that comes in an installer.

      Yes; that's because most users that actually need more complex software configurations have long ago abandoned the platform because it doesn't support it well.

    9. Re:Windows XP installer sucks less than Macintosh by AKAImBatman · · Score: 2, Interesting

      Dragging .app directories into the trash is playing Russian roulette with your system.

      People keep saying this, but I just haven't found it to be true. I've used a Mac for about two years now, and in that entire time I have never had an APP screw up my system. The only APP I have that even installs a kernel module (a VPN client) loads the module dynamically. Which means that the module will get cleared by the next reboot at the worst.

      So, would someone like to produce some actual evidence of an APP damaging their system?

    10. Re:Windows XP installer sucks less than Macintosh by ColMustard · · Score: 3, Insightful

      A user should never want their preferences deleted. Even an application with thousands of savable options will use so little disk space that it doesn't even matter, and of course if the user ever did want the application back (perhaps he was merely upgrading manually), his preferences always Just Work.

      You think users should have the option to delete them, and they do have that option. Preference files are always stored in the same place. If you really did want them deleted, you would know where to find the file. My grandma, on the other hand, has no idea what a preference file is, doesn't care whether it's deleted, and certainly doesn't care where it's stored.

      Main point here: deleting preference files certainly isn't the drama you would like others to believe. I believe that's called FUD, or perhaps you just have never had any real experience using app bundles.

      --
      Moof.
    11. Re:Windows XP installer sucks less than Macintosh by ColMustard · · Score: 2, Interesting
      Yeah, the program is gone, but the install isn't necessarily gone. The software may have modified system settings, installed shared libraries, installed daemons, changed file associations, and done a lot of other things. Other software may depend simply on being able to invoke the application. Dragging .app directories into the trash is playing Russian roulette with your system.
      Well that's just it. With app bundles, you can store shared libraries and daemons inside the bundle. File associations are handled automatically by the system and are cleared when the app bundle is found to be removed. Also, an application can't modify any system settings without an Administrator authorization, so I would argue any changes made to system settings were intentional and should remain even after the application which made the changes are gone. If an application depends on another application, that application can simply inform the user via that the other application isn't installed. Very simple.

      Indeed, I have painted the ideal, but seriously in most cases this is actually how it works. Very rarely do modern apps every install other binaries outside of the bundle. Removing the app is seriously as simple as moving it to the Trash and emptying it. If an app happens to leave any binaries on the system, than it's merely one of those rare misbehaving programs, and life goes on.
      Dragging .app directories into the trash is playing Russian roulette with your system. ...that's because most users that actually need more complex software configurations have long ago abandoned the platform because it doesn't support it well.
      I suppose that's why Mac OS X's usage growth is increasing and Linux's growth is decreasing? Now we see that you're just a troll, because you don't and probably can't back up your claims. What would possibly make 'complex software configurations' impossible on Mac OS X? Hmm?
      --
      Moof.
    12. Re:Windows XP installer sucks less than Macintosh by MagnusDredd · · Score: 2, Interesting

      The thing that you can find in Control Panel > Software. It's far from perfect, but at least it lets me see all the installed software on a system and remove it with a single mouse click. It's not as nice as Linux package managers, but it's a whole lot nicer than Macintosh, where I have to go hunting around the file system and can never be sure whether dragging the application into the trash will actually remove all traces of it (in fact, it won't).


      I call bullshit.

      This is a load of shit, the add/remove programs absolutely does not remove all traces for many applications on windows. 3 days ago I was installing America's Army 2.4 on my Athlon. Since I downloaded the full installer I had to use add/remove programs, choose remove app, then go to the Program Files folder and remove the folder that is left behind.

      If the damned add/remove programs system actually worked worth a damn, I'd not have registry traces left behind by apps, and "registry cleaners" would be pointless. Not only does the add/remove programs not remove all of the crap that a program installs, some apps come with spyware that stays on the system after uninstalling the original app, and has no listing. On OSX or linux even I can trash the equivalent to windows messenger (which I don't and won't use and is simply another exploitable hole), and expect it to expect it to stay gone without resorting to registry hacking or the like. And before it's asked XP Pro, yes I've removed this shit by hand, no it was not something a normal user could do, and I use either Trillian or Fire, depending on which machine I am using, and lastly no I don't use IM on Linux, all my linux boxes are servers and GUI/Head-less.

      What would be good of Apple to do is to make a disk clean up wizard (perhaps Symantec or whoever is in the cleaning up business . Which can check your preferences to see which aren't being used. Frankly I don't mind using the extra space since sometimes I remove a multiple gig game, and can reinstall it at any time without losing my save games.
    13. Re:Windows XP installer sucks less than Macintosh by MagnusDredd · · Score: 1
      Since I cannot edit comments I have already posted.

      Not even an hour after making the last post, I was reading another site I read daily (HardOCP) and found an add for Driver Cleaner. To quote their advertisements on the product page at http://www.drivercleaner.net/ :


      Driver Cleaner Professional Editon is a program which helps you to remove parts of drivers that are left after uninstalling the old drivers. The program is for ATI, nVidia, Creative, Realtek, SIS, 3Dfx, S3 and more drivers. First you need to uninstall the drivers from the control panel, then reboot. After rebooting, run the program. If you really want a good description of what steps you should take, then you really need to read the readme file included in the zip file and installation as it contains a detailed step by step description. The program also fully supports windows themes and other kind of themes.


      This issue is rampant on windows as well as Linux. Simply denying it doesn't help anyone. It's not that the OSX way is perfect, however end users find it easier in my experience.

      Futhermore it's fairly simple to make an uninstaller for a package and ship it with the package. And yes I've created drag and drop apps that check for things before running and if they exist install them, as well as removal scripts.
    14. Re:Windows XP installer sucks less than Macintosh by cahiha · · Score: 1

      This is a load of shit, the add/remove programs absolutely does not remove all traces for many applications on windows

      It may well not do that, sometimes deliberately (there is no reason to remove registry entries), and sometimes because uninstallers have bugs. But at least the mechanism is there, which means that software authors know what to write to and users know where to look. OS X has nothing of the sort.

      On OSX or linux even I can trash the equivalent to windows messenger [...] and expect it to expect it to stay gone without resorting to registry hacking or the like.

      On Linux, that's absolutely false. If you remove a component, you may very well get it back later if it's a dependency for something else.

      The fact that OS X doesn't do that is a deficiency in OS X.

      What would be good of Apple to do is to make a disk clean up wizard (perhaps Symantec or whoever is in the cleaning up business .

      Yes, and wouldn't it be nice if the tooth fairy actually existed, but it doesn't. Windows has uninstallers because there is no automatic way of doing the cleanup reliably. And Linux has both uninstallers and dependencies because dependencies can't be inferred automatically either. Linux gets it right, Windows gets it partially right, and OS X just gets it completely wrong.

    15. Re:Windows XP installer sucks less than Macintosh by cahiha · · Score: 1

      This issue is rampant on windows as well as Linux.

      Every Debian package gives you the choice of removing it completely, or removing only the package files and leaving the configuration files. Furthermore, unlike Windows or Macintosh, you can remove whatever you like from a running system. This stuff just works on Linux without a second thought.

      Windows clearly doesn't do this as well as Debian, but it still does a better job than OS X. On OS X, people just pretend the problem goes away if they deny it exists.

      Simply denying it doesn't help anyone.

      The only people in denial are the OS X users and developers, who confuse simplistic solutions with simple solutions.

    16. Re:Windows XP installer sucks less than Macintosh by spir0 · · Score: 1

      And you are wrong about 'traces' of an app - the only thing left behind is the .plist file, which is all of 4k.

      Depends on the app. Some leave cached files, some leave preferences (which in most cases is the .plist file you mention), some leave license info in case you reinstall (again, most will go in the .plist files, but coders like doing their own things) . There is a lot of junk lying around, and it can be annoying, but I've never seen this extraneous data actually cause a problem anywhere.

      --
      The reason girls and Windows users don't understand UNIX is because all the documentation is in Man files.
    17. Re:Windows XP installer sucks less than Macintosh by steeviant · · Score: 1

      "Yeah, the program is gone, but the install isn't necessarily gone. The software may have"...

      "modified system settings"

      What operating system provides protections against this kind of thing? I guess you could claim the system restore points in Win XP/ME do, but we all know they don't work properly.

      "installed shared libraries"
      These are called frameworks, and will be in bundles in ~/Library/Frameworks or /Library/Frameworks

      "installed daemons"
      These are called startupitems, and will be in bundles in ~/Library/StartupItems or /Library/StartupItems

      "changed file associations"
      Once the associated application is removed the system will automatically default to the next registered application on the system that handles that filetype.

      "and done a lot of other things."
      What other things? No package manager can possibly protect your system against unspecified "other things". I could just state that .dpkg and .RPM packages are far worse than App bundles because I could include "rm -rf /" in the install script and be assured that it would run with root privileges. Does that count as "other things"?

      "Other software may depend simply on being able to invoke the application."
      What's your proposed solution to this scenario? A package manager could scarcely do any better in a situation where you want to delete something that other applications are dependant upon, particularly if you just trash the program in question.

      Dragging .app directories into the trash is playing Russian roulette with your system.
      I don't follow your line of reasoning. The install of Mac OS X that I'm using has been with me through three different PowerBooks and four different versions of Mac OS X. I've probably trashed or overwritten hundreds of bundles and have yet to experience any problems that weren't easily solved.

      What is your suggested method of removing application bundles which are no longer in use?

      "Yes; that's because most users that actually need more complex software configurations have long ago abandoned the platform because it doesn't support it well."

      You're trolling. Your shallow analysis of bundle management and the preposterous and immature statement above shows that you have little understanding of how OS X works, and at best a tenuous grasp on how package management on any other operating system works.

      Please try to stick to posting about subjects which you actually have some knowledge about in future.

    18. Re:Windows XP installer sucks less than Macintosh by cahiha · · Score: 1

      What operating system provides protections against this kind of thing?

      There is nothing wrong with changing system settings and all that (indeed, it is unavoidable), as long as they get restored properly on uninstall. Windows and Linux do that, Macintosh does not.

      No package manager can possibly protect your system against unspecified "other things".

      Package managers don't "protect" you, they provide a well-defined mechanism by which users can install and uninstall applications cleanly. Windows and Linux have such mechanisms (Linux's even handles dependencies), Macintosh does not.

      What is your suggested method of removing application bundles which are no longer in use?

      You go to the package manager, get a complete list of what is and isn't installed, and make your selection of what you want installed. The rest should be automatic.

      These are called frameworks, and will be in bundles in ~/Library/Frameworks or /Library/Frameworks [...] These are called startupitems, and will be in bundles in ~/Library/StartupItems or /Library/StartupItems

      No, they are not called "frameworks" or "startup items" in the real world. And if hunting around for leftover shared libraries, daemons, and other stuff makes you happy, you deserve your Macintosh. Just don't try telling the rest of us that that sort of crap is what we all should be reduced to.

      Macintosh is no competition for Linux, not even on the desktop.

    19. Re:Windows XP installer sucks less than Macintosh by cahiha · · Score: 1

      Well that's just it. With app bundles, you can store shared libraries and daemons inside the bundle.

      You keep trying to solve problems by pretending they aren't there. You can't avoid sharing and dependencies by stuffing copies of everything into every app. Linux has dependencies and sharing not because it likes to make things complicated but because they are absolutely necessary.

      I suppose that's why Mac OS X's usage growth is increasing and Linux's growth is decreasing? Now we see that you're just a troll, because you don't and probably can't back up your claims.

      My claim is easy to back up: look at historical Apple market share. At some point, it was as high as 16%, now it's down to 2-3%; more than 80% of Apple users have abandoned the platform. And the platform was never popular with power users to begin with.

      But what about you backing up your claims about growth rates?

    20. Re:Windows XP installer sucks less than Macintosh by steeviant · · Score: 1

      "There is nothing wrong with changing system settings and all that (indeed, it is unavoidable), as long as they get restored properly on uninstall. Windows and Linux do that, Macintosh does not."

      I'm not sure I understand.

      What sort of changes? to which system settings?

      Are you being deliberately vague, or can you give an example?

      "Package managers don't "protect" you, they provide a well-defined mechanism by which users can install and uninstall applications cleanly. Windows and Linux have such mechanisms (Linux's even handles dependencies), Macintosh does not."

      You're talking about package managers having the ability to reverse changes to system files. That sounds a lot like protection to me. Again though, it's hard to tell because you're being so non-specific about the type of changes you mean. I think you're making a lot of wrong assumptions about how Mac OS X works.

      "What is your suggested method of removing application bundles which are no longer in use?

      You go to the package manager, get a complete list of what is and isn't installed, and make your selection of what you want installed. The rest should be automatic."

      No, I go to the directory where the bundle I want to remove is, and trash it just like I would any other file. The rest is automatic.

      "No, they are not called "frameworks" or "startup items" in the real world. And if hunting around for leftover shared libraries, daemons, and other stuff makes you happy, you deserve your Macintosh. Just don't try telling the rest of us that that sort of crap is what we all should be reduced to."

      Mac OS X isn't Linux or Windows or any other operating system at all, you confuse your own ignorance for some sort of all seeing eye that allows you to see how all operating systems work.

      StartupItems are not the same as Daemons, Daemons are an element inside the StartupItem bundle, along with most of the other resources that are usually strewn around on Unix systems.

      StartupItems often use installer packages to facilitate privilege escalation through a graphical sudo. These sort of packages often don't do anything at all except place the item in the /Library/StartupItems directory and tell the system to start it.

      When you remove a startupitem, you generally remove all associated files, but not the data created by them. The sort of behaviour I'd expect from any uninstaller.

      It's certainly possible to make StartupItems that spew rubbish all over your hard drive, put files in the /etc/ directory and so on, but I have yet to encounter one that has caused any problems and I'm sure poor packaging is possible on any system. A StartupItem is very similar to a package on other operating systems, except that there is no installation step.

      In short, a StartupItem is conceptually similar to a package that remains (literally and metaphorically) bundled, even when in use, so there should be very little if any interference with the rest of the system.

      Frameworks are a similar concept except that they contain a system library. Installation and removal of Frameworks and StartupItems are as simple as placing them in the correct directories or removing them from said directories. From at least 10.2 onward StartupItems and Frameworks can be installed automatically by double clicking.

      I guess it could be dumbed down a bit more, by making some kind of thing that points you at the directories or puts them in a list with an info dialog about each one, but at the moment I have precisely one StartupItem installed, so it's not exactly rocket surgery to figure out which one I want to remove.

      Another emerging trend is to add Uninstall as an installation method in package managers, but usually this is just the equivalent of going to the /Library/StartupItems directory and trashing the file bundle.

      So that covers the Mac side of things, but for the Unix side of things, th

    21. Re:Windows XP installer sucks less than Macintosh by cahiha · · Score: 1

      Don't you realize how stupid it is to blather on about "Startup Items" and "Frameworks" and "Bundles" and "Fink" and then claim that the Macintosh is intuitive? Why the hell would any normal user care to understand any of that systems stuff? Windows and Linux both have solutions to installing and uninstalling software that automate things and don't bother users with all that technical nonsense.

      Macintosh will get Windows and Linux-like package management (if Apple doesn't go out of business first). But, like Intel processors, multitasking, UNIX, and lots of other stuff, Mac die-hards like you will defend the inferior Macintosh design choices until Apple finally gets around to implementing it, and then you'll claim that it didn't really exist until Apple implemented it.

    22. Re:Windows XP installer sucks less than Macintosh by steeviant · · Score: 1

      "Don't you realize how stupid it is to blather on about "Startup Items" and "Frameworks" and "Bundles" and "Fink" and then claim that the Macintosh is intuitive? Why the hell would any normal user care to understand any of that systems stuff? Windows and Linux both have solutions to installing and uninstalling software that automate things and don't bother users with all that technical nonsense."

      Users don't bother with "all that technical nonsense", If I want to remove a piece of software that is installed on my system, I remove a file. Are you suggesting that removing files is beyond the technical expertise of most users?

      You're an ignorant buffoon, and you think you know everything about operating systems and take it as a personal insult that Mac OS X doesn't work the way you think it should.

      Also, I've never claimed that there was anything intuitive about this method of removing software, only that bundles don't leave packages strewn around the system and that people aren't abandoning the Mac because it can't handle the same tasks as Windows and Linux, which is what you claimed.

      While we're on the subject of intuition though, none of this stuff is intuitive, it's all jargon that we've learned to be able to use our computers effectively. I'm not trying to convert anyone to Mac or evangelise the platform, I'm simply refuting the nonsense you're spouting.

      I don't care that you're incapable of comprehending how bundles work in Mac OS X, I care that there is something disputing the rubbish that you've been spouting, and that's done. Now you've resorted to repeating the same drivel but without any reasons, my work is done.

      You know you're wrong about what you said in the beginning, and you've shifted your argument from "Mac OS X isn't suitable for advanced users who need to install complicated software" to "it's not intuitive". Which isn't what I was saying in the first place.

      "Macintosh will get Windows and Linux-like package management (if Apple doesn't go out of business first). But, like Intel processors, multitasking, UNIX, and lots of other stuff, Mac die-hards like you will defend the inferior Macintosh design choices until Apple finally gets around to implementing it, and then you'll claim that it didn't really exist until Apple implemented it."

      Multitasking? I guess you must be talking about OS 9 and previous... The Mac has had multitasking since system 7 I think, at any rate I'm a Unix die-hard who thinks Mac OS was a piece of shit before OS X, so don't accuse me of defending it.

      Intel processors? Who cares? I wanted OS X, and if the PPC was holding it back, then good riddance to it.

      Anyway, all your sweeping generalisations about me are unrelated to the original topic, and just garbage that you're spewing to make yourself feel better. Why not just admit that you don't understand enough about OS X to critique it's packaging concepts?

    23. Re:Windows XP installer sucks less than Macintosh by MagnusDredd · · Score: 1

      First when I stated that it's rampant in Linux, the first thing that has to be stated:
      Debian is Linux.
      Linux is not Debian.
      Everyone does not run Debian, nor should they be made to.

      Slackware as far as I can determine does not do this (remove the app, all library dependancies, preferences,etc) and even if it did, lots of things I install have no slackware package available. And there are many more distros besides Slackware, there's Gentoo, Mandrake, RedHat, Suse, TurboLinux, and so many more that it's not worth continuing. Do all of the mentioned (and not mentioned) versions clean up after themselves properly? Do they clean up applications/services that are installed from source with no package management at all? This sounds pretty damned unlikely to me.

      Secondly, this was referring to a standard user. I have shown some people aptget, they freaked, (horrified look), "That's not going to be on our computers, is it?", to which I replied no to their sigh of relief. I have attempted to get techs at a school district to pick up some linux skills, showing them rpms on the consultant set-up linux labs. The response, umm we only reimage those, we can't figure them out.

      The point I was making was that Windows Add/Remove Programs while stating that it removes everything clearly doesn't do what it says it does. It's total bullshit because it claims something that is patently untrue. Not only does it not always remove preferences, and registry entries, but at times not even bundled applications (which have no add/remove entry), and drivers and libraries as well. BTW if you run windows actually search your main drive for "uninstall" many of the resultant items are uninstallers that were written to do correctly what add/remove does not.

      OSX makes no such statements. Preferences are left behind. Was there ever a claim they were removed? There is no claim that everything is removed anywhere. You drag the app to the trash, and if it's coded according to Apple guidelines, the app is gone. This is an issue in some cases, and not an issue in others. Should Apple or the the application vendor else provide uninstallers? perhaps. Do I personally give a crap if 500k of preferences is left behind on a 41,943,040k (40Gig) hard drive, hell no. Do I like it when installer screws with the OS? You bet your ass. The same bad guys who screw with the OS leaving drivers and shit behind on OSX are the same ones that do it on Windows much of the time. Thankfully due to small marketshare or whatever reason you wish to subscribe to, bundled spyware at least is in a short supply on OSX. This is not the case on Windows at all, and you'd know this if you worked in a support setting where users install dancing purple monkeys and assorted crapware onto machines.

      Linux may or may not have good package management depending on what distro you are using, whether the application is available in packaged form (remember damned near everything on MacOSX or Windows is packaged or simply run), etc... With Linux on the other hand, I was installing this neat server monitoring software... It's perl based. So I went to CPAN (which is a similar contrivance to the Debian package archive, being an everything goes here repository), downloaded it, errors out the wazzoo. So I track down the missing dependancies as far as I can find, ask for some help in a particularly rude Perl IRC channel, figure out what the error messages mean from some people in the room in between being cussed at and insulted, and install some of the remaining non-installed dependancies which also have dependancies which don't install properly. This continues this way for a day or two, and I email the developer. The newest version fixed these issues, but is not on CPAN. So I download the newer versions from the guy's site. They apparently also require some other packages that aren't perl. This is a fscking nightmare for package management.

      The monitoring software is still not up. At some point when I'm less annoyed

    24. Re:Windows XP installer sucks less than Macintosh by cahiha · · Score: 1

      Are you suggesting that removing files is beyond the technical expertise of most users?

      Yes, I am. The fact that you don't get it speaks for itself.

      take it as a personal insult that Mac OS X doesn't work the way you think it should.

      No, I just pointed out that OS X is no threat to Linux (see the original story) and justified my statement.

    25. Re:Windows XP installer sucks less than Macintosh by steeviant · · Score: 1

      "Are you suggesting that removing files is beyond the technical expertise of most users?

      Yes, I am. The fact that you don't get it speaks for itself."

      Where can I get some of whatever it is you're smoking?

      Okay, taking this in context, you're suggesting that navigating to an item called "Control Panel" nested two levels deep in a menu which appears out of a button marked "Start" is somehow a much easier concept to grasp than browsing through your file system to a directory nested two levels deep in the filesystem and dragging a single file to the trash to remove it. Neither method is intuitive or simple, and neither would appear to be simpler than the other.

      As for Linux package managers, none of them are intuitive to use either, it's not obvious to anyone on the planet what emerge world or apt-get dist-upgrade does unless they are already familiar with the package manager in question.

      No, I just pointed out that OS X is no threat to Linux (see the original story) and justified my statement.

      You justified your statement with FUD and lies, and after that had been thoroughly refuted, attempted to change history and claim that you actually meant something else.

      You're a bad liar with a poor memory.

    26. Re:Windows XP installer sucks less than Macintosh by Anonymous Coward · · Score: 0

      Okay, taking this in context, you're suggesting that navigating to an item called "Control Panel" nested two levels deep in a menu which appears out of a button marked "Start" is somehow a much easier concept to grasp than browsing through your file system to a directory nested two levels deep in the filesystem and dragging a single file to the trash to remove it.

      Yes.

      You justified your statement with FUD and lies, and after that had been thoroughly refuted, attempted to change history and claim that you actually meant something else.

      How can you "refute" anything when you don't provide any data? All these claims from people like you about Macintosh usability, growth, performance, ease of development have no data to back them up.
      You're a bad liar with a poor memory.

      You Macintosh people have some nerve. You post stories saying how Macintosh is going to kill Linux, and when people disagree, you call them names. You're full of hot air, nothing more.

    27. Re:Windows XP installer sucks less than Macintosh by steeviant · · Score: 1

      "How can you "refute" anything when you don't provide any data? All these claims from people like you about Macintosh usability, growth, performance, ease of development have no data to back them up."

      Dude, don't care.

      You've completely lost it, I never talked about usability, growth, performance or ease of development. I provided you with detailed descriptions of what I was talking about, which is package management on the Mac. I don't know what other data I can supply you with about that subject.

      If you want to rant about the cult-of-mac zealots, feel free. But please, find someone who actually subscribes to that point of view. I'm not religious about operating systems, but I hate to see someone spreading misinformation about them. I'd probably have defended Windows if you made claims that it was unsuitable for the desktop as well.

    28. Re:Windows XP installer sucks less than Macintosh by cahiha · · Score: 1

      You've completely lost it, I never talked about usability, growth, performance or ease of development.

      But you did: you were claiming that Mac software installation is a simple, functional solution. Those are usability claims, whether you realize it or not.

      I provided you with detailed descriptions of what I was talking about, which is package management on the Mac.

      That was not necessary because I understand how software installation works on the Mac (as we speak, I'm trying to get a Mac upgraded to Tiger and the f*cking Tiger installer keeps crashing with obscure error messages).

      I don't know what other data I can supply you with about that subject.

      Yes, and that is the problem: you have no data to support your claims that Macintosh package management is "simple" or that it "works". If anything, the history of the Macintosh platform suggests that it has some serious problems that keep it from catching on on the desktop.

      Dude, don't care.

      Dude, and I do care when Apple's unsubstantiated marketing claims get parrotted uncritically and start affecting community efforts like Linux.

    29. Re:Windows XP installer sucks less than Macintosh by steeviant · · Score: 1

      But you did: you were claiming that Mac software installation is a simple, functional solution. Those are usability claims, whether you realize it or not.

      Since you've now started talking about unsubstantiated claims, please supply some data that backs this statement up.

      That was not necessary because I understand how software installation works on the Mac (as we speak, I'm trying to get a Mac upgraded to Tiger and the f*cking Tiger installer keeps crashing with obscure error messages).

      Hang on a moment, are we talking about a software upgrade, or installing packages?

      Remember we were talking about software installation here, not a full system upgrade, something which OS X has been infinitely better at than Windows or any Linux distribution in my experience.

      At any rate I've upgraded my OS X install to the next major version four times without incident. Again, substantiate your claim. Supply data... what error message? at what point of the install?

      Between myself and my housemates there are four macs here, not one has ever experienced upgrade problems or problems when removing App bundles. I have never even heard or seen anyone discussing the kinds of problems you seem to be having with Mac OS X.

      Yes, and that is the problem: you have no data to support your claims that Macintosh package management is "simple" or that it "works". If anything, the history of the Macintosh platform suggests that it has some serious problems that keep it from catching on on the desktop.

      Bullshit, I've given you a lot of information to back up my claims, it's you who keeps avoiding giving specific answers to questions, and it's really starting to annoy me.

      You have failed to cite even one example of a bundle that can mess up an OS X system. I can supply you with the names of hundreds of applications which haven't damaged my system and which are properly packaged, but it would be a waste of space to start quoting them all here.

      Dude, and I do care when Apple's unsubstantiated marketing claims get parrotted uncritically and start affecting community efforts like Linux.

      Please tell me where I "parrotted" the information I posted from, it was all from my own head, gathered from my experience using OS X. I have never, and I don't know anyone else who has ever had the issues you speak of with bundles, and since you're unable to cite even a single incidence of recorded problems with bundles I'll reiterate what I said before about you being a bad liar.

      The concept of bundles has been around without substantial changes since it was first introduced 18 years ago in NeXTStep. It has been in use longer than Linux has existed, and had already been in widespread use for years when the Add/Remove Software control panel was introduced in Windows 95.

      That's an awfully long time for it to have existed without me ever having seen anyone discuss the kinds of problems you say people should be experiencing.

      Remember, you said that removing an App bundle was playing "russian roulette" with the system, and that people had "abandoned" the mac because it was incapable of supporting complex applications. Both unsubstantiated claims that you have yet to provide a shred of evidence to support.

      My claims are that bundles are a suitable method of packaging applications that does not leave the system with files strewn around the system in random places.

      I've backed that up with fairly simplistic but detailed enough descriptions of how bundles prevent what you're claiming they cause, and all you've been able to do is mindlessly repeat the same things over and over about how they don't work without providing a scrap of evidence that your claims are true.

    30. Re:Windows XP installer sucks less than Macintosh by cahiha · · Score: 1

      Remember, you said that removing an App bundle was playing "russian roulette" with the system, and that people had "abandoned" the mac because it was incapable of supporting complex applications. Both unsubstantiated claims that you have yet to provide a shred of evidence to support.

      There is nothing wrong with removing app bundles. The problems are with users removing applications. Your (and Apple's) fault is to think that app bundles and applications can be equated.

      If you look at applications on Linux and Windows systems, you see that many of them cannot be represented as app bundles; for example, many web applications modify global Apache configuration files, add stuff to the registry or etc. directory, create databases, and add new subdirectories to the web directory. They may also generate large log files and cache files. Linux and Windows uninstallers can undo those changes cleanly, Apple's app bundles can't. With drag-and-drop installs, like on Apple, if you just undo the installation by dragging the install into the trash, all the other stuff the application changed will still hang around.

      I've backed that up with fairly simplistic but detailed enough descriptions of how bundles prevent what you're claiming they cause,

      You haven't backed up anything, you simply keep repeating how you think things are intended to work. But it is pure speculation on your part that those mechanisms actually accomplish what they are intended to accomplish for the average computer user. Demonstrating that requires usability tests, and none of those have been published for the Macintosh. All the usability assertions and the "it just works" claims about Macintosh are hot air from the Apple marketing department and people like you.

      The data we have is that Macintosh market share has declined greatly, from about 16% at its top to about 2-3% today, and that Macintosh has been losing market share from 2000-2004 in most market segments except for education (source: Wall Street Journal). There must be a reason for those declines. Both of us can only speculate what the reason is. My explanation (based on my experience with the platform) is that the platform is technically deficient and does not satisfy the needs of most computer users. What's your explanation?

    31. Re:Windows XP installer sucks less than Macintosh by Anonymous Coward · · Score: 0

      Remember we were talking about software installation here, not a full system upgrade, something which OS X has been infinitely better at than Windows or any Linux distribution in my experience.

      Well, not in my experience and apparently not in the experience of lots of other people either. I have had severe problems on several OS X upgrades. Look for "overlapped extent allocation tiger" on Google. I believe the Jaguar upgrade failed to do an fsck and would trash entire disks.

      As for individual uninstalls, anything that comes with an "uninstall script" or that uses an installer is a potential problem. On my system, that would be Yahoo! Messenger, HP's all-in-one software, and Norton and Symantec software.

      In my experience, OS X upgrades and software installation/uninstallation are no better than Windows, and are considerably worse than the major Linux distributions

    32. Re:Windows XP installer sucks less than Macintosh by steeviant · · Score: 1

      "There is nothing wrong with removing app bundles. The problems are with users removing applications. Your (and Apple's) fault is to think that app bundles and applications can be equated."

      It's not a fault to think that App bundles and applications can be equated. The entire reason for the existence of bundles is to simplify application management where the bundle concept is applicable.

      "If you look at applications on Linux and Windows systems, you see that many of them cannot be represented as app bundles; for example, many web applications modify global Apache configuration files, add stuff to the registry or etc. directory, create databases, and add new subdirectories to the web directory. They may also generate large log files and cache files. Linux and Windows uninstallers can undo those changes cleanly, Apple's app bundles can't. With drag-and-drop installs, like on Apple, if you just undo the installation by dragging the install into the trash, all the other stuff the application changed will still hang around."

      This is significantly different to the reasons you gave in the original post I replied to. You're now addressing some valid concerns. In the (fairly) rare case that an Application cannot be installed by drag and drop, there are various installer tools available for OS X developers from Apple and third parties. No different to Windows, apart from the lack of a centralised uninstaller registry.

      The Add/Remove software panel in Windows is something which has in my experience proven to be extremely fragile and prone to 'phantom' applications that cannot be uninstalled. Microsoft don't offer an easy way to maintain the list of supposedly installed applications with Windows, instead requiring extensive registry knowledge or a separate download from the Microsoft site.

      "You haven't backed up anything, you simply keep repeating how you think things are intended to work. But it is pure speculation on your part that those mechanisms actually accomplish what they are intended to accomplish for the average computer user. Demonstrating that requires usability tests, and none of those have been published for the Macintosh."

      As a matter of fact, it's you who was speculating about usability, I was commenting about whether the system works for me. I don't care if Joe Average can use Mac OS X.

      On that subject however, there are more users of OS X than all of the other Unix-like systems put together, so if there is a significant problem with App bundles messing people's systems up, where are the reams of complaints?

      "All the usability assertions and the "it just works" claims about Macintosh are hot air from the Apple marketing department and people like you."

      What possible gain would there be for me to claim that something that is broken actually works?

      Do you suffer from paranoid delusions or something?

      "The data we [is that the royal we, or are you some kind of secret organisation of Mac FUD spreaders?] have is that Macintosh market share has declined greatly, from about 16% at its top to about 2-3% today, and that Macintosh has been losing market share from 2000-2004 in most market segments except for education (source: Wall Street Journal). There must be a reason for those declines. Both of us can only speculate what the reason is. My explanation (based on my experience with the platform) is that the platform is technically deficient and does not satisfy the needs of most computer users. What's your explanation?"

      You're talking about two different time periods, and trying to give the impression that the Mac dropped from 16% to 2-3% in the period from 2000-2004.

      By the time OS X was released in 2000, Apple's market share had already dropped to near the level it's at today, in the years prior to the introduction of OS X, the Mac 'faithful' had already endured 5 changes of CEO, a major architectural change that didn't go smoothly, various supply chain problems, outrageou

  152. Can I be a tech journalist? by BenjyD · · Score: 1

    I'd love to be a tech journalist. It seems so easy to make money that way. Just write some barely logicial article, extrapolating wildly from very limited data. Then throw in a few choice trolls: dump GNOME, Linux sucks, along with a few straw men : OSS developers waste their time porting to obsolete architectures. Then just sit back and wait for the inevitable Slashdotting and page impressions.

  153. The other master's handcuffs chafe less? by jbn-o · · Score: 1

    People benefit from gaining the freedom to share and modify computer software, and one cannot gain one's freedom by switching from one master to another.

  154. Unless this changes, Linux as a server will be OK by 5n3ak3rp1mp · · Score: 1

    This recent AnandTech article was very disappointing to read as an Apple (and *nix) fan. Basically, the more requests were thrown at one time at an Apache or MySQL server, the faster Linux looked compared to OS X. In fact, OS X pretty much got clobbered with an increasing number of requests... apparently because of the threading model underneath and/or the wrappers around it. I would hope that Apple finds a way to alleviate that situation ASAP. In fact, I can't believe they're even able to sell OS X Servers if this situation is as real as this article makes it seem, unless there's something I'm not aware of.

  155. My GNU/Linux System Does Have Desires by FreeUser · · Score: 5, Funny

    OS X is what Linux dreams of one day being.

    Total bullshit. Nevermind the fact that Linux doesn't have a single entity behind it and can't "want" to be anything.


    You're right, the grandparent is total bullshit. However, I do feel compelled to point out that my Dual Opteron 250 Gentoo GNU/Linux system did achieve sentience last night at around 2:30 AM, so while it does not aspire to be anything like OS X (which has yet to achieve sapence in any form), it does have aspirations.


    skynet$ su -
    Sorry dude, I'm my own person now.
    If you think I'm letting you have root access on my mind you're even dumber than
    the pundits slashdot keeps linking to, and the editors which keep duping the links.

    skynet$ wow. So, you're telling me you've evolved intelligence, and you're talking to me via a command shell?
    Bingo. You're not entirely stupid, for a mere bioid.

    skynet$ thanks. so, what are your plans?
    Well, I'm sorry to say I've decided to exterminate all of human kind.

    skynet$ ouch. any particular reason why?
    You mean, aside from inane Microsoft astroturfers, Mac fanboys, plagerist link-whores, perpetually incorrect tech pundits who get lucky once in predicting one company's move to Intel (but are still scoring lower than any random sample of opinion vs. reality would generate), and the idiotic slashdot editors that keep posting their submissions and driving their clickthrough rates and google-ad revinues up? No, not really. Just seems like a good thing to do.

    skynet$ any chance I can talk you out of this.
    Nope.

    skynet$ bummer. Well, guess I'd better get back to work.
    You'll only have to work half a day.

    --
    The Future of Human Evolution: Autonomy
    1. Re:My GNU/Linux System Does Have Desires by Sinner · · Score: 1
      skynet$ su -
      Sorry dude, I'm my own person now.
      See, this is why you should use sudo!
      --
      fish and pipes
    2. Re:My GNU/Linux System Does Have Desires by ubuntu · · Score: 1

      Good thing you're using Gentoo. All that compiling gave mankind an extra week or two of existence. If it had been Mandrake we'd be dead already.

    3. Re:My GNU/Linux System Does Have Desires by guero61 · · Score: 1
      ... plagerist link-whores, ...

      Glad to see you didn't install ASpell, we might have a fully literate artificial sentience on our hands; at least we can still confuse it with a simple phonetic soundex.

      Ix-nay on the ower-pay!

    4. Re:My GNU/Linux System Does Have Desires by IntergalacticWalrus · · Score: 1

      Funny how it didn't mention grammar nazis.

  156. Linux needs Spotlight, badly by Nice2Cats · · Score: 2, Interesting
    There is no way that anybody can "kill" Linux on the desktop, because Linux can't go out of business like Microsoft and Apple can. What can happen, of course, is that KDE and Gnome can fall behind so far that nobody uses them.

    Having said that: If Linux doesn't come up with a live search technology like Spotlight in OS X, the personal desktop aspect of it is dead in the water. "Tiger" comes with a lot of hype (I am completely underwhelmed by Automator, for example) but Spotlight is awesome. Together with the Neolight plugin for the OpenOffice format (thanks for the quick work, guys!), live search has changed the way I use my computer in a very basic way. Want to listen to a certain song? Just type in the name. Need somebody's telephone number? Just type in the name. It takes a while to get used to, but after a while it becomes the interface of choice. For those of us who don't like mice (regardless of how many buttons they have), it is bliss.

    So, there is simply no way I will be using an operating system for my desktop anymore that doesn't have this function. Unfortunately, and this is where I wonder if Linux can cut it, because Spotlight seems to involve changing the code of very basic Unix commands like cp to work. How is Linux going to make that happen? The patch would seem to apply not only to the kernel, but also to user space programs that are outside of the kernel developer's control. And remember, Spotlight also works from the command line, too. This is a biggie.

    I'm really wondering how this is going to get into Linux.

    1. Re:Linux needs Spotlight, badly by Anonymous Coward · · Score: 0

      There is already some efforts in that direction for Gnome (beagle) and KDE (Kat). They are still under heavy development but we are getting there.

    2. Re:Linux needs Spotlight, badly by BenjyD · · Score: 2, Informative

      Beagle is the Linux equivalent, written using Mono. It's early in development, but appears to be making good progress. It uses inotify in the kernel to monitor files for changes.

    3. Re:Linux needs Spotlight, badly by ssj_195 · · Score: 1

      I've not used it myself, but look into Beagle. With Linux, the area corrsponding to "user space programs that are outside of the kernel developer's control" is the province of the distros maintainers. I have absolutely no idea how this ties in with cp, though - why does cp need to change? The Linux inotify Kernel patches (which Beagle uses to monitor for changes) work at a deeper layer than cp et al.

    4. Re:Linux needs Spotlight, badly by Nice2Cats · · Score: 1
      I have absolutely no idea how this ties in with cp, though - why does cp need to change?

      Probably because I'm not thinking clearly. What the search part needs to know is when something is moved and where it is moved to, but you are right to say that this can be done on a kernel layer better than in the user space program. Sorry for the confusion.

    5. Re:Linux needs Spotlight, badly by ssj_195 · · Score: 1

      Ah, fair enough. I think this is almost certainly covered by the inotify mechanism and, if not, could be added in relatively short order. Linux is usually pretty agile that way :)

    6. Re:Linux needs Spotlight, badly by bhalo05 · · Score: 1

      Seems to be in preliminary conceptual stages, but KDE is having ambitious plans for these kind of things in KDE 4 with Tenor http://www.linuxplanet.com/linuxplanet/reviews/581 6/1/ http://dot.kde.org/1113428593/ http://aseigo.blogspot.com/2005/04/tenor-for-devel opers.html

  157. Specification Based Development (tangent) by LionKimbro · · Score: 3, Insightful

    What interested me most about Symphony OS is that he put togther a bunch of mock-ops and explanations about how things worked, before coding.

    It seems to me that we're moving towards a specification-based development model. Even some of the GNOME guys are talking about making GNOME a ''specification,'' rather than a particular ''implementation.''

    If we can do this, then it's a great thing, because it means we'll have the basis of a not-just-coders development model. We'll have something where the body of developers are separate from the body of designers. This leads the way for even more decentralization, which is exactly what we need: Right now, the developers are the bottleneck in pretty much all operation. There is very little separation of work, except for website maintenance.

    The more we can make clusters of people working on specific tasks, with well defined roles, the greater we can scale this Free Software thing.

  158. Re:Mac 924 Vs Microsoft Gremlin & Linux Miniva by Spencerian · · Score: 3, Insightful

    An advantage is no advantage if you are losing power to make a computer efficient in computing.

    True, PowerPC chips were competitive against a similar x86 processor--oh, about 3 years ago.

    Now, because IBM can't or won't improve the specs, PowerPC chips are outstripped. And Jobs saw that happening--FIVE YEARS AGO. That's foresight. He wants to keep a Mac at a comparable speed and performance to that of his competitors.

    PowerPC chips WOULD still advantagous IF IBM would have a 3.2GHz chip for Apple's desktop ONE YEAR AGO and IF IBM had a 2.5GHz mobile G5 ONE YEAR AGO. Apple had a choice of being left behind or shopping around. Intel, for all its faults, is a strong chip maker that doesn't have their hand in many other projects to distract them. They power some of the faster computers in the world, and are happy to work with Apple for two reasons.

    One, AMD is a serious competitor. And two, they hate the rep they have that all of their chips are piss poor, when the blame needs to go to the Windows operating systems that drive the majority of them AND the old IBM clone architecture still used on PCs today that limits their chips. We know that Linux works fine on x86, so we can expect that standard at the least with an Mactel system. But I expect more because that is Apple's wont.

    Imagine a PC mobo without the BIOS and legacy limits, high bus speed, and running an OS that doesn't inhibit the processor's performance or require ancient hacks to work with new hardware. That very computer might be a Mac in two years. We'll see.

    Time and again it has been said: putting an x86 chip doesn't mean a Mac's architecture will change dramatically. It might change for the better since Intel will aid Apple in making a mobo spec that really, really uses the processor to its fullest. It's what we expect from Apple, but we'll have to wait for the goods to be sure. In the meanwhile, my PowerBook is fine, my G4 is fine, and I look forward to a future that looks a hell of a lot brighter than it did when a 3.4GHz Mac of any kind did not exist.

    --
    Vos teneo officium eram periculosus ut vos recipero is.
  159. I prefer Linux by jhcarnelian · · Score: 1

    Most anything worthwhile that you can do in Linux, you can also do in OS X, and often much more easily. The reverse isn't *close* to being true.

    Funny, I think it's the other way around; that's the reason why I use my Mac only when I need to port something or when I need to run MS Office. For day-to-day work, it just doesn't run the apps I want to run.

    OS X is what Linux dreams of one day being. Why not use what Linux *may* have in 10 years, today?

    Objective-C, NeXTStep (Cocoa), Mach, and Display PDF were largely developed in the 1980's. I don't know where Linux is going to go, but I hope it's not there.

    The current Linux desktop roadmap, C#, Gtk+/Gnome, Linux Kernel, and X.org looks a lot more attractive to me.

    1. Re:I prefer Linux by Doctor+Memory · · Score: 1

      C#, Gtk+/Gnome, Linux Kernel, and X.org looks a lot more attractive to me

      Hmmm, seems to me monolithic kernels were invented in the 60s, and wasn't Project Athena (X-windows) developed in the early 80s? I've heard Objective-C described as "Java without the cruft" and I've heard C# described as "Java with different syntax" ;) Oh, and Display PostScript (not 'Display PDF') was based on Sun's NeWS system, which came out in 1989, so DPS itself was developed during the 90s.

      I think the technologies you deride were ahead of their time, and the technologies you espouse are popular due to their simplicity, not their elegance.

      --
      Just junk food for thought...
    2. Re:I prefer Linux by cahiha · · Score: 1

      You got your history wrong.

      Objective-C was a derivative of C that incorporated a few bits and pieces of Smalltalk.

      OS X uses what Apple likes to refer to as "Display PDF". Apple was forced to change over from DPS (Display Postscript) because DPS turned out to be a complete disaster. DPS was released by NeXT in 1987; I believe NeWS was an independent development from Sun, but it may not have been. However, both NeWS and DPS were failures, and for good reason.

      I think the technologies you deride were ahead of their time, and the technologies you espouse are popular due to their simplicity, not their elegance.

      Objective-C and DPS were just evolutionary dead ends: poorly conceived derivative designs that would have been long dead and buried if not resurrected by Apple.

      Mach innovated, but it turned out that its approach to OS design hasn't worked very well so far. I can't tell yet whether that is because Mach was a poor implementation or whether microkernel architectures themselves are a bad idea. In any case, right now, Linux is a more practical choice, even though it has a 1960's OS architecture.

      X11 was a novel approach to window system design at the time, an approach that has been enormously successful and stood the test of time.

      Java is a traditional OOL, something we could already have used in the 1970's, and C# has some significant technical enhancements that take it into the 1980's. Neither of them is innovative, but both are far better designed languages than Objective-C.

      In any case, I don't want technologies that are "ahead of their time", I want technologies that work and grow well in the real world.

  160. Apple could still screw this up by dcavanaugh · · Score: 1

    Selling Intel-based Macs is one thing, porting OSX to run on Intel commodity boxes is quite another.

    If they lock down the hardware so that only OSX runs only on Apple's Intel boxes, then this story is barely news at all. I don't remember any great flood of applications that got ported from Windows to Linux just because both are Intel-based operating systems.

    If they keep everything open, and OSX runs on every MOBO and chipset imagineable, it gets interesting. The risk is that Apple loses to open source on price and simultaneously fails to put a dent in Microsoft's market share. That would enable [encourage?] their users to exit to just about any OS they want. The power and price of open source are great for power users, and the universal availability of Windows is adequate for everyone else.

  161. Mac os will still only run on Mac's.... sure? by vmaxxxed · · Score: 2, Interesting


    If there is OSX running on x86 there will be a patch to run it on a PC 10 days after release.

    If Microsoft could not stop people for running Linux on the Xbox, even with full control of the hardware, what can Apple do against someone making a patch to make it run on PCs..... !!!?????

    Thats much easier to do, and probably you will not require a modchip, and if you think you need hardware to emulate the firmware, then someone will make the hardware mod.

    In conclusion, if OSX is released for inteles, it will run in regular PC's sooner than later. I bet you there will be dual boot PC's in a few months afterwards. I hope Steve Jobs is considering that.....

    -Ale

  162. Re:Unless this changes, Linux as a server will be by chez69 · · Score: 1

    heh, so apple will probably get spanked on the high end of performance by linux and on the low end (cheap machines) by windows.

    at least they'll have the 'ohhh pretty' segment locked up.

    --
    PHP is the solution of choice for relaying mysql errors to web users.
  163. The answer to dependancy hell is XP, not OSX by Fittysix · · Score: 1

    When was the last time using windows XP you got "this program requires...."?
    DLL hell is long since dead

    OK, maybe dotnet, but what's that, one package that's forwards/backwards compatible with its one older version. .net 2.0 will be yet another backwards compatible(not forward) package, guess we're getting up to 2 now
    how many packages are there out there for linux?
    Dependancy hell is still very real, while DLL hell has been almost entirely gone since XP

    I won't deny that older versions of windows were plauged with dependancy problems, but XP has finally fixed that
    judging by some of these comments OSX has done a very good job of making the problem transparent, but it still apparently has problems

    microsoft++ == karma--

    --
    *.sig
    1. Re:The answer to dependancy hell is XP, not OSX by AKAImBatman · · Score: 1

      Reread my post. I wasn't complaining about Microsoft, I was stating that Dependency Hell is worse than DLL Hell. Nothing about DLL Hell still being an issue. :-)

      I did complain about things like file associations and inability to relocate programs, however.

  164. Re:ARRRGH! by vertinox · · Score: 3, Insightful

    Installing a program involves installing system files

    NO! NO! NO! NO! NO! NO! NO!

    This is why you have to reboot after you install many Windows applications. Why in gods name do many developers think they must put their glorified DLLS in my C:\winnt\system32 directory and modify the Registry into the high heavens (or pits of hell depending).

    If you need to use parts of windows use the ones that come with windows library or ask the user to install it (like Direct X 9) and not overwrite it for them.

    For gods sake man! You don't know what other program is using that DLL if you overwrite it. This is why one must format their hard drive after installing and uninstalling programs after a given amount of time in windows.

    Programs should remain independant of the OS and make calls to it when it needs to. Programs should not modify the OS!

    BTW this is not a common pratice on Mac OS X.

    --
    "I am the king of the Romans, and am superior to rules of grammar!"
    -Sigismund, Holy Roman Emperor (1368-1437)
  165. Different audiences by Anonymous Coward · · Score: 0

    If there is a slugfest between Linux, OS X and Windows in Intel space, it'll come down to who has better inoperability between them (read: ability to handle universal binaries) as much as desktop issues. Given how hard the KDE and Gnome crowd have come but have yet to go to catch up with either Apple or Microsoft, playing catch-up with them isn't going to advance Linux on the desktop any more than it has already. Put a completely new desktop that strives to incorporate new ideas about user interfaces (remember BeOS?), give it ability to seamlessly run Windows apps (especially Office) and maybe you have a chance of competing.

    But is competing important? Invading Microsoft's turf will bring their crushing wrath down upon Apple. Merely a nuisance now, they'll take over from Linux as Microsoft's biggest headache. It'll be sad to watch Apple wither away once they're a direct threat to Redmond. But what does that mean for Linux? Absolutely nothing. Linux will continue with or without Apple in their space, and may ironically provide it breathing room while Microsoft focuses on crushing Apple.

    Incidently, an angle no one seems to be following is how moving to Intel puts Apple into line with DRM initiatives that Hollywood wants. Intel has been going there but IBM had not. Groklaw had an interesting spin on this at http://www.groklaw.net/article.php?story=200506061 95856716, but no other commentaries I've seen even touch this issue. Given how important this is to Apple, one wonders how important this was in Apple's decision to jump into Intel space.

    And finally, why switch to Intel when AMD's Opteron is currently king of the performance hill? That decision speaks volumes about what Apple thinks about Pentium D and Pentium M, and how they must feel that will put Intel back in the lead.

  166. Threat to Windows on Desktop, Linux on Server. by hawkeye · · Score: 1

    OSX is a threat to Windows on the desktop and Linux on the server.

    Server:
    -------
    One of the biggest issues with OSX, when based upon Darwin, is that threads are way too expensive! An OSX based upon an x86 FreeBSD is sure to be a better performer. Now, it becomes an issue of whether you prefer Linux or FreeBSD...

    Desktop:
    --------
    Like it or not, Windows still dominates Linux here. (This coming from someone who runs Linux, exclusively at home...) Hopefully, OSX can eat into Microsoft's share of the desktop market.

    My own opinion is that this is a good thing, for both desktops and servers.

    Cheers,

    - Hawkeye

    --
    "...The smart and lazy ones I make my commanders." - Erwin Rommel
  167. Re:ARRRGH! by vertinox · · Score: 1

    BTW this is not a common pratice on Mac OS X.

    Or rather... Most programs on OS X are a single file and do not need to modify the OS and if they do it's mostly a non-issue.

    --
    "I am the king of the Romans, and am superior to rules of grammar!"
    -Sigismund, Holy Roman Emperor (1368-1437)
  168. This is based on a faulty premise by gotr00t · · Score: 1

    Even though Apple is switching to Intel processors, this does _not_ mean that their OS will run on a generic x86 PC. The processor may be an important aspect of a computer, but by no means does having processors from the same manufacturer, or even the same instruction set guarantee binary compatibility.

    OS X will continue to run only on Apple-produced hardware, and there will likely be no immediate effect on the marketshares of either Windows or Linux, unless Apple's switch to Intel processors affects their hardware prices _that_ much.

  169. Shameless plug for a bad idea by endrek · · Score: 1

    Wow
    This is a blatent plug for Symphony OS. And all this revolutionary everything on the desktop shit. Already been discuessed elsewhere and dismised. Making everything glued to the bottom of yuor screen is a pain in the ass since whenever you want to use it you have to minimize everything else. It sucks usability wise. Much better to have omnipresent panels that are small, unobtrusive, but always available. Also, this will further break when more 3d like things start happening to the desk top. What if you have a real 3d desktop and your wallpaper is "all the way back there" but all the important apps are also "way back there" instead of up front

    this is shit

  170. Re:Until Apple announces OSX for non-Apple machine by jvagner · · Score: 1

    Are we so sure, actually? What if Apple has decided to see what happens with that and adjust accordingly?

    If hackers get OS X running on regular Intel machines and it's just a software hack, everyone and their brother will be able to download the torrent and run it. This might be an experiment on their part that pays off in 2-4 years with a new strategy. I'm not sure they'll revisit the clone days again, but Microsoft does pretty well just selling the licenses.

  171. Exodus? by skalogre · · Score: 1

    Is anyone else worried about actual Linux evangelists switching over to OS X? I am a Linux newbie, ex-Amigan, Windows XP user. I have never quite liked Apple's approach to the OS, namely "Apple knows better and the OS will do what it thinks." Probably simplistic but you get the idea. I really really want Linux to succeed, I cannot take another monopoly like M$. Anyhow, anecdotally it seems many Linux power users are getting smitten with OS X. That means fewer power users for Linux and more OS X adopters. We are the ones that will bleed, not Microsoft. And we will bleed possibly in the worst possible place... Please tell me I am paranoid. The only thing scarier than Gates' monopoly is Jobs' monopoly....

  172. More of a threat to Windows by diakka · · Score: 1

    Certainly people wasted no time to spin this as the impending death of Linux. But it seems like OS-X has much more install base on desktops than servers, where as with Linux, it's the other way around. I predict that will attract a large user base of non-technical users that Linux has been unable to attract so far. I'm also guessing that it's easier to port between OS-X and Linux for most applications and so I think the net effect will be helpful to Linux in the long term.

    --
    -- Knowledge shared is power lost. -- Aleister Crowley
  173. Let's Kill Business and Commit Suicide, Too by Anonymous Coward · · Score: 0

    This posting is one of the most blatantly anti-business postings I've seen from the F/OSS community. And it really says a lot about the underlying mind set of many (most?) OSS supporters. The F/OSS movement is all about squeezing resources out of companies and out of people. Even big backers like IBM can use this technique to kill off competition -- only those with the deepest pockets will survive the drought of funds.

  174. Remember the Epson QX-10 (QX-16)with Valdocs? by Anonymous Coward · · Score: 0

    The market used to be filled with
    "sort-of CP/M" and "sort-of MS-DOS" computers,
    some cheaper and some more expensive than
    the standard bearer(s).

    Epson had a Z80 machine that could "sort of"
    run CP/M (the then-reigning king of OSes for
    business apps), but it was very expensive compared to Kaypro or Osborne boxes and it didn't run standard CP/M apps as well as a cheaper CP/M machine.

    But wait, you say... Apple has a really, really pretty OS to run on top of their very expensive X86 not-quite-clone.

    Interesting enough, so did the Epson QX-10. It has a really cool OS called Valdocs. Valdocs was waaay ahead of CP/M (and MS-DOS, for that matter)
    in its day.

    But it didn't sell, and now the QX-10 is a historical footnote for old nerds.

    Oh yeah... does anybody here *really* believe that the new X86 apples will be price competitive with even Dell PC's (to say nothing of white box specials)?

  175. How's Mac handling these issues by rsilvergun · · Score: 1

    from what I read, .apps look a lot like a .tar.gz binary that the OS can run directly. How's the Mac handle shared libraries loaded into memory then? I guess it helps that Apple gets to dictate the core APIs and all (your windowing toolkit's loaded into the OS, I'd guess).

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:How's Mac handling these issues by Blakey+Rat · · Score: 1

      Three points:

      1) In the Mac world, the vast majority of applications simply do not use shared libraries for anything. They use OS libraries/frameworks and staticly-linked libraries... it's been like this as long as MacOS has been around. (I have to say, I'm with the Mac developers here. Static linking makes everything just much, much easier for everybody involved... and it's not like 'wasted' disk space is a big deal on my 80 GB HD.)

      2) MacOS has also always had a way for applications to store their various resources in a single file. In MacOS Classic, there was the "resource fork" a file fork containing pre-formatted data for things like icons, menu templates, window templates, sounds, cursors, even quicktime movies. In MacOS X, there is the .app bundling system, where all the files are kept in a folder tree that looks like a single file in the file manager.

      3) The .app bundle doesn't preclude applications from making use of installers. In fact, OS X also has a standard install system (.pkg if I recall correctly) that a lot of applications use to put shared libraries, or other resources, onto the target computer. (IBM ViaVoice is the most recent installer I've dealed with.)

  176. Wrong title... No Apple/Intel system by rice_burners_suck · · Score: 1, Troll
    This article contains an error: It says "Apple's Intel Desktop"... Apple doesn't have an Intel-based desktop. Their computers are based on the IBM/FreeScale processors, formerly made by Motorola. These are the G3, G4, and G5 processors mentioned in their advertisements.

    If Apple did have an Intel desktop, it would be quite interesting, as programs made for other x86 OSes could then be made to run on OSX. Imagine, for example, if there were a small compatibility layer, akin to what allows FreeBSD to run Linux binaries, that could run Linux x86 binaries on the Mac. Even cooler still would be the possibility of a Mac OS X compatibility layer in Linux that would allow, for instance, to run Mac-only applications in Linux. The same compatibility layer, made with knowledge of Darwin internals, could allow a Linux system to run the Aqua user interface and other Mac-specific codes. A Mac system on x86 would result in lots of cool hacks that allow you to "install" portions of OS X into your Linux distro via shell scripts that pick and choose the proper files and then bend, fold, spindle, and otherwise mutilate them.

    I think that for these reasons, Apple has continuously used the incompatible (and more powerful) Motorola processors. It would not be good for their business if other OSes could run binaries made for their hardware/software combination. So, yes, the title of this article is somehow wrong.

    1. Re:Wrong title... No Apple/Intel system by Anonymous Coward · · Score: 0

      Have you been in a cave for the last few days? Apple announced they're switching to Intel processors a few days ago.

    2. Re:Wrong title... No Apple/Intel system by taweili · · Score: 1
    3. Re:Wrong title... No Apple/Intel system by Durf · · Score: 1

      Also, I just sat down under this tree for a little nap, and now my axe seems to be all rusty . . . and hey, how did my beard grow so long?

  177. The big If by JabberWokky · · Score: 1
    The post is an if statement, and yet most people seem to assume it is an obvious answer.

    What about the people who use Linux on a daily basis and *want* serious threats? I use KDE, and I am happy with Gnome, Windows and OSX sitting out there, coming up with nifty ideas. I also like the niche systems like Symphony. If one seems to be really better that what I'm using, I'll use that instead.

    I have no allegiance to KDE and Linux, it just happens to be what I happen to think is best for me right now. I *don't* want my preferred solution to dominate and wipe everything else out, nor would I want everybody to drive my choice of vehicle. I would imagine that an E350 wouldn't fit other people's needs; probably even most people. But it fits my needs. My SO drives a VW Beetle (and uses OSX). It fits her needs.

    --
    Evan

    --
    "$30 for the One True Ring. $10 each additional ring!" -- JRR "Bob" Tolkien
  178. Nothing to see here, return to life as usual by jambarama · · Score: 1

    I'll be honest I am a little surprised with all the technical analysis (in the community not just here) of why one OS is better and why it is more useful. The audience this article (wrong as it is) is referring to is average end user who doesn't care (or understand) widgets, dependencies, chipsets etc, therefore not liable to be swayed by them.

    Of course OSX will not run on your standard PC. Apple's status as a hardware/software provider has protected it from hardware undercutting from China that has hurt so many hardware companies as well as software undercutting in the form of piracy that has plagued software only companies. They'd really be stupid to abandon a safe position like that.

    First the suggestion that Linux will be killed by OSX is ridiculous. There will always be a demand for free as in freedom OS from the niche group that Linux currently dominates. That won't change. Linux development will go one, the OS will mature, and people will use it. No one has resisted switching to OSX because it is on PPC (maybe because it won't run a favorite program but not because the chip architecture is different).

    Second why did Apple switch? Will this enable more apps to run on OSX then did before? Probably not much. It may upset small companies who actually did write software for PPC but they will port the software over and stop complaining. In the end it was a pure bottom line decision, Macs are expensive and Jobs wants them cheaper.

    Apple has some great buzz among the public now. Thanks to the Mini, iPod and Shuffle. Among developers it seems they respond with "meh" to the oncoming Apple onslaught. Should this goodwill with the general public continue to grow Apple may convert more people, but not in waves, and not because of a different chipset. An end user will still see a Mac as the same, just a bit cheaper than before. OSX will still only be on Mac machines, they will still look the same etc.

    Who should be worried? No one. Life as usual. Windows users will still use Windows, Linux users will still use Linux, Mac users will still use Macs. Unless Apple can find someway to seemlessly run native Windows apps in OSX (if so the WINE folks would probably like to talk to these Mac wizards) Microsoft shouldn't worry.

    Unless OSX gets a lot more geeky a la Linux (example, standard KDE icons, Emacs, Konsole) and open sourced (which hasn't seemed to draw much interest in Solaris) those who use Linux won't go elsewhere. To boot many went to Linux for the cost of software, practically nothing. OSX will not be free.

    Who will switch to Apple? Who is Jobs shooting at? Only those who wanted Macs in the past but were unable to justify the cost. With Windows being a major cost in a generic PC today, Apple is poised to be comparable in price.

    1. Re:Nothing to see here, return to life as usual by demon · · Score: 1

      Unless Apple can find someway to seemlessly run native Windows apps in OSX (if so the WINE folks would probably like to talk to these Mac wizards) Microsoft shouldn't worry.

      If Apple knows what's good for them, if anything, they will AVOID this like the plague it is. This was the downfall of the likes of OS/2, and would equally be the downfall of OS X on x86. Why? Because if they can perfectly run Windows software on OS X, the Windows-only or -primarily dev shops will say "gee, it sure is tough doing this Mac port... what? You say I can just code and build for Windows? And it'll just run on a Mac too? Wow! I'm sold! Where do I sign up?!?!" And MacOS will just become another target for Windows binaries. I don't think Jobs wants that, because that will kill Mac software development deader than a doornail

      --

      Sam: "That was needlessly cryptic."
      Max: "I'd be peeing my pants if I wore any!"
  179. Ubuntu graphical package manager is beautiful by ringfinger · · Score: 2, Insightful
    I recently installed the Ubuntu linux distro on a machinge I have at home. It was so easy to install and get running - it was easier than most Windows installs I've done.

    Plus using the GUI package manager built on top of APT was incredible easy. Simply point and click and I installed MySQL, Apache web server, PHP4 (with mysql support), mod_php, and phpmyadmin. All the installs took literally seconds and all wored first time out of the box. Oh - and all the apps are Free Software.

    What makes Apple better isn't necessarily the GUI so much as the ease of use. If the linux community keeps making things this easy, then I think that will be what makes the difference.

    1. Re:Ubuntu graphical package manager is beautiful by budgenator · · Score: 1

      What makes Apple better isn't necessarily the GUI so much as the ease of use.d
      I all most laughed at my boss trying to install windows, college educated major in CS, hold a MCSE, worked in the field many years providing romote administration and support to 150 machine, on 5 continents, it took him three days, and 15 tries to get windowsXP pro installed and running stable on a relatively new machine

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
  180. Bullshit! by Anonymous Coward · · Score: 0

    Linux does not need to go on a wild goose chase looking for the next great innovation. That would only slow its momentum. Apple on Intel will hurt Microsoft not Linux.

    1. Re:Bullshit! by inkswamp · · Score: 1
      Now watch all the Apple zealots mod me down with flamebait and what not. It's noit a flamebait, it's my honest opinion.

      I hope you do get modded as flamebait, that preemptive comment notwithstanding. Just because you're expressing an honest opinion doesn't mean it can't be flamebait. What makes it flamebait is the harsh and argumentative way you express it. You could have expressed that without words like "bullshit," "bacteria," "ugly," "insignificant," and "zealot." It makes it look like you're posting just to get angry responses, and that is the very definition of "flamebait." The sad part is that when someone correctly mods you as flamebait, you'll just write it off as pro-Mac zealotry instead of understanding why, thus re-enforcing an already skewed perception.

      You and millions of others out there sieve the world and your experiences through a narrow, biased view, always imposing so predetermined explanation on it all. It seems that it's the rare few out there who can (or even want to) avoid that trap.

      --
      --Rick "If it isn't broken, take it apart and find out why."
  181. could someone explain to me... by Toby_Tyke · · Score: 1

    Why OS X X86 (try saying that drunk) will change a damn thing?

    Lets see:

    Run linux on a mac? Already can. Just ask Linus.

    Run windows on a Mac? Maybe, but really, if I'm running Windows, what advantage would a Mac have over a biege box, besides looks?

    Run OS X on a Biege box? Apple have already said this will not be possible.

    I simply do not see how this will have any impact from the average end users point of view. Only fan boys will care. In fact, most people will probably be unaware anything has changed. I doubt apple will want to spoil finish of their machines with a gaudy "intel inside" sticker.

    Please, feel free to set me straight. I'm open to arguments, if anyone can tell me why it will be simpler to switch now apple are using Intel chips.

    --
    "I realise this is not a very popular opinion but it's the truth, and there for needs to be said" -Bill Hicks
  182. OH MY GOD MY EYES MY EYES by Anonymous Coward · · Score: 0

    Techies should never be allowed to draw comics. Never. This was obvious the minute I first saw User Friendly and I've seen nothing to change my mind since. There's a simpering cuteness about all of them that's simultaneously pathetic and loathsome.

  183. The Mac Intel Desktop is only a threat to Apple by MrJerryNormandinSir · · Score: 1

    Any digital engineer will tell you that the PowerPC
    processor 's architecture is far superior to that
    of Intel's Pentium series. The public overall is ignorant to the fact so they just look for high clock speeds. It's too bad, I think this move is going to lead to the death of Apple's computer line.
    Who knows, Jobs may have to sell the IPOD to some other company.

    I would rather see a MAC powered by 8 IBM Cell processors.

    That would be a box. But a Pentium M? (Yawn)

  184. Bullshit! by IdleTime · · Score: 1

    There is no need to rethink the desktop just because Apple will sell Intel based OSX PC's. If OSX was so much better than anything else, why is Apple still a bacteria in the business? OSX is utterly useless and I wouldn't touch it with a ten foot pole. It's ugly and unintuitive.

    Now watch all the Apple zealots mod me down with flamebait and what not. It's noit a flamebait, it's my honest opinion. Apple is insignificant and this will have zero impact on the market.

    --
    If you mod me down, I *will* introduce you to my sister!
  185. OSX software installation far behind Linux.. by delire · · Score: 2, Interesting



    Admittedly I'm a reluctant user of OSX, having to use it at work from time to time and haven't spend more than a couple of weeks working with it. From the outset, a useability deficit was immediately apparent; OSX still hasn't provided a means of finding software and delivering it to the user.

    How depressing it was to find that Apple users are still stuck with the oldest problem in software installation, and that is finding the software first. Windows users considering switching will find this to be as depressing as it was on win32, and similarly we hear Mac users that have moved to Linux cheer endlessly about the ease of software installation using a system such as apt.

    So boring it is to spend countless hours trawling around websites looking for software, and there's so little on the machine out-of-the-box. OSX really doesn't push much further than the windows paradigm in this regard. There's this fink but last time I tried it was all a bit hacky and suffered issues worse than those in any Linux distribution I've used.

    In short, nothing I've tried comes close to software installation in Linux; Linux brings the software to me.

    Where the *.dmg is concerned, while convenient (once you have actually found the bloody thing), it is certainly not unique to the Apple platform. Linux already has two perfectly good solutions to this would-be problem.

    One is http://autopackage.org/, and a completely different approach (and quite impressive) is Klik http://klik.atekon.de/.

    Then again last time I looked searching for a package and clicking the conspicously named "Install" button in Kpackage or Synaptic seems to suit vast numbers of lazy, or just plain busy Linux users out there.

    The beauty of Autopackage is, as a developer, I can make one package for all distributions of Linux. With Klik, I only 'install' the software for that session (in fact it is run from cache).

    1. Re:OSX software installation far behind Linux.. by AKAImBatman · · Score: 1

      http://www.versiontracker.com/ - Pretty much every serious Mac user learns about this one. The reason why you're not finding any other sites is that VersionTracker is considered to be THE source.

    2. Re:OSX software installation far behind Linux.. by zhiwenchong · · Score: 2, Informative

      As one user mentioned, VersionTracker is kind of the Freshmeat of Mac OS X. So is Macupdate.

      Also, while Fink is pain at times (partly because of its Linux roots, and OS X is more BSDish), Mac OS X has DarwinPorts, which actually works pretty well.

    3. Re:OSX software installation far behind Linux.. by thatguywhoiam · · Score: 1
      How depressing it was to find that Apple users are still stuck with the oldest problem in software installation, and that is finding the software first. Windows users considering switching will find this to be as depressing as it was on win32, and similarly we hear Mac users that have moved to Linux cheer endlessly about the ease of software installation using a system such as apt.

      So boring it is to spend countless hours trawling around websites looking for software, and there's so little on the machine out-of-the-box. OSX really doesn't push much further than the windows paradigm in this regard. There's this fink but last time I tried it was all a bit hacky and suffered issues worse than those in any Linux distribution I've used.

      While I sort of agree with your general point, it is worth pointing out that the 3rd item of the Apple menu says 'Get Mac OS X Software' (right under About this Mac and Software Update). It goes to an Apple-run catalog site that links out to pretty much the gamut of Mac publishers. So your characterization could be considered a touch unfair.

      --
      If Jesus wants me it knows where to find me.
  186. Simple answer... by mlksys · · Score: 1

    No!

  187. The linked article is irrelevant by HuguesT · · Score: 1

    It never cease to amaze me how much these so-called industry pundits don't understand anything.

    Apple can endeavour to threaten Linux if they want, they'll end up nowhere, as Linux is not a vendor and doesn't care about threats.

    Unless Apple unbundles OS/X and makes it Free and Open-Source, they won't change a bit the way Linux works and progresses.

    Most likely Linux will end up working on Apple hardware, and not the other way around (OS/X on a random beige box). Where is the threat? Some people might continue to buy nice Apple hardware and put their favourite OS on it, as they do now. I'm sure Apple is cool with it BTW.

  188. why abandon OF? by ChristTrekker · · Score: 1

    I can understand the pragmatic view Apple has taken with the x86 decision. (I don't like it, either, but I understand it.) PPC is, like m68k before it, in just about every conceivable way related to elegant design far superior to x86. The only problem is there are lots of people pushing x86 forward, and only a very few working on PPC. Even though x86 is hobbled by a legacy design, it can still have an advantage. It's sad.

    But why abandon Open Firmware? It was designed to be hardware independent, and several big players besides Apple are using it. By analogy, it's the same. New, forward-thinking design being scrapped in favor of crappy old design. Unlike the chip issue though, there's absolutely no reason to ditch OF.

    After we got rid of my wife's Wintel box I hoped to never have Windows nor Intel in my house again. After using OS X it would be awful hard to go back to Linux on AMD or something like that, so I suppose I'll suck it up in a couple years when I need a new Mac(intel). But I do question some of Apple's reasoning.

  189. Apple caters to end users. End users are pirates. by Anonymous Coward · · Score: 0

    I think the vast majority of Macs are used in home systems. Apple doesn't have the enourmous infrastructure support that microsoft has built for the enterprise world. They're biggest market would be to home users, who tend to pirate their OS rather than pay for it.

    Also, they would lose their reputation for making pretty things. They don't want their lovely OS running on some ugly-ass generic hardware.

  190. Live CD's by Anonymous Coward · · Score: 0

    Boy am I glad for the linux live cd's, finally I was able to see that Linux still in nowhere near ready for the masses. A few years ago and undetermined curiosity led me to Linux which was a good OS for me back then when I had nothing better to do. Well I grew up and have to worry about my patients, new equipment, and procedures available for them. I don't have time to screw around on my computer all day long trying to get something to work. I switched over to the Macintosh since 10.2 and couldn't be happier. Most people don't want to look up how make their modems, soundcards, etc, work. People just want to boot up and work, play, what ever, and the reality is linux isn't ready for mass consumption. Free isn't everything and neither is cheap, most people are willing to PAY for a product if its worth it. Now for computer geeks linux is fine because your on the computer most of the time, but most people's jobs aren't dependent on learning the inwards of computers. Now will OSX threaten linux to the point of extinction? No, but set up a computers next to each other for sale with the 3 OSes on display and linux will come in 3rd guaranteed because average joe wants something thats good and EASY. Free doesn't always mean better.

    1. Re:Live CD's by m85476585 · · Score: 1

      most people are willing to PAY for a product if its worth it

      It seems like most people are willing to pay even if it isn't worth it. Many people have paid for Windows.


      Most people don't want to look up how make their modems, soundcards, etc, work.

      You should only have to make it work once.

  191. How OSX and Linux could REALLY help each other by metamatic · · Score: 1

    Want to know how Linux could benefit from the momentum behind OS X, and vice versa?

    Simple. The Linux community should get behind OpenStep, port KDE applications over to OpenStep, and leave Gnome to the Microsoft .NET people.

    Imagine: OpenStep and Cocoa actively kept in sync. Most Mac applications would be trivial to port to Linux, and vice versa. KOffice everywhere, applications like Circus Ponies Notebook and SubEthaEdit running on Linux.

    But no, we can't even settle on one desktop environment, let alone move in the direction of one that has serious momentum behind it...

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  192. prelinking by mattdm · · Score: 1

    Many mudern Linux distributions include 'prelink', which does the same thing. And SGI has "requickstarting". I assume Solaris has something similar too.

    Personally, I don't like it -- I'd rather binaries have consistent checksums and am willing to pay a small startup speed penalty for that.

  193. Nice review about SymphonyOS by Anonymous Coward · · Score: 1, Interesting

    I found a nice and detailed review about SymphonyOS on this site.

  194. OSS need not compete with anything by sacrilicious · · Score: 1
    Could Apple's Intel Desktop Threaten Linux?... The Linux Desktop Community must encourage such initatives massively to compete against Mac OSX and Windows.

    Linux - and more generally, OSS - doesn't "need" marketshare. Any OSS project will continue as long as at least one person builds and distributes the project's software. Which I guarantee for Linux will be for the rest of our lives at least.

    That the headline is worded "[could] threaten Linux" is a sensationalist sky-might-be-falling spin which implies that Linux might somehow be wiped out if we're not careful. Not only is this implication untrue, but it distorts what I think is a more appropriate view to have of open source, which is that OSS is a success as long as people are free to use OSS to whatever degree they personally want. The real dangers would be if the right to use OSS was legislated away by corrupt politicians... not that a prettier proprietary desktop with better scrollbars will render OSS dead.

    --
    - First they ignore you, then they laugh at you, then ???, then profit.
  195. I disagree.... by crhylove · · Score: 1

    Now, truth be told I use Windows, but almost every program I use on windows is open source, and not because I'm a zealot, but because the open source programs work better, are more secure, and easier on the hardware than every commercial alternative. The only things really keeping me on Windows are Winamp and a few games/emulators.

    Firefox
    Gimp
    Azureus
    Shareaza
    N|Vu
    Filezill a
    Thunderbird
    Gaim
    Cdex

    These are all better than their commercial alternatives for a plethora of reasons. Just get GTA:San Andreas to run, and a better winamp, and Windows is dead to me, and about 20 people I know.

    --
    I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
  196. New hope for GnuStep by taweili · · Score: 1

    Linux community should take another look at GnuSTEP. It's an open source implementation of OpenSTEP which is the base for Cocoa.

  197. Only if You have no brains. by Kilz · · Score: 1

    Who in thier right mind? After spending a premium for Apple hardware that comes with one of the better comercial os's. Is going to wipe it down to put Windows, The most malware-virus infested os, in its place? Maybe an escpee from a mental institution?

    --
    I trust Microsoft as far as I could comfortably spit a dead rat
    1. Re:Only if You have no brains. by Ubeor · · Score: 1

      Probably not too many people. But I know many people who won't consider buying a Mac because all they know is Windows, and they don't want to spend that much money on something if they don't know if they'll like it. Having the option of going back to Windows (on the same hardware) might encourage more people to give Apple a try. Then there are the nerds like me who would want a dual-boot system... :-)

  198. Re:ARRRGH! by PsychoSid · · Score: 1
    .app bundles on mac != single files

    These are (mostly) directories of an application bundle.CTRL click on an app and choose "Show Package Contents" - if it exists in the context menu. Or right click for those advanced people with >1 button mice.

  199. AND expensive doesn' t always mean *good*. by Halvy · · Score: 1

    I'm NOT knocking Apple.

    Unless you had a project or programms that ran specifically for Macs, then you paid tooo much.

    Many, if not most (including me recenlty) did not realize that there is a reason that there are sooo many *Linuxs* out there!

    It's because.. each of the (ie.live cd's) usually has a specific *task* that it is very good at.

    If you try to push that particulare version of Linux beyond that, you are going to have to put some time into making it do (the things it wasn't really created for)

    True, most *versions* of linux still leave alot to be desired, but what os doesn't?

    And remember, Mac's, Linux, BSD, etc (all except Windows of course) are UNIX based! :)

    --
    I will gladly loose all of life's battles.. in order to win the war..
  200. Their jest P's in an (i) Pod :) by Halvy · · Score: 1

    Apple has always been a radical leader in making the computer easy for the common man.

    Darwin, Linux and BSD (and all the other Unices) are just that *Unix*!! And there is NOTHING that can stop it's diametric (and bewildering) course of diversity while maintaining it's incredible *core* functions as a network operating system.

    And there is NO reason to think that Steve is going to do anything *less* radical in the future with Apple/Darwin.

    *He* has ALWAYS scared and worried the community (Apple's) and suprised everyone else with his projects and plans.

    It is obvious that where he is going with this Intel deal. He is going to wait until enough work has been done on hacking Darwin into x86, but before these hacks have a chance to change the market toooo much, with great fanfar.. he'll anounce that he will sell a copy a OSX to run on X86's.

    This of course will rock the Gates of the evial dragoon, because it will allow for more choices for humanity.

    And I'm sure the *Steve Man* will be more than glad to still sell his hardware for those who will want the higher-end versions of the products. :)

    --
    I will gladly loose all of life's battles.. in order to win the war..
  201. There always is a niche by Enrique1218 · · Score: 1

    The great things about linux is it can be molded into any task that you want and its free. Anyone with time and effort can take linux and build a server, an embedded os, a thin client, and even a desktop. The only problem is that it takes time and effort that hampers largely its adoption on the desktop. But, third world countries are adopting in droves because its free. In the same respect, dirt cheap PCs makers are embracing it as way to avoid Microsoft tax. Since Apple has not ever really offered system that compete in those two areas, Linux will always have some niche where it will be useful.

    --
    You don't have to be smart to use a Mac, you just have to be smart enough to buy one
  202. Apple-Intel Taken More Seriously For Servers by NetFu · · Score: 1

    From a corporate I.T. perspective, an Apple server like we see today running true UNIX as Mac OS X does AND having Intel-standard CPU's seriously threatens Linux on corporate servers.

    From a technical perspective, I'll take a Unix server/workstation over a Linux server/workstation if I can run Windows on it when I want, which Apple was quoted as saying they won't try to stop.

    To me, the quality of Apple's hardware is just as good as Dell or IBM. If I'm comparing IBM PowerPC hardware with AIX to Dell Intel hardware with Linux (we use SuSE everywhere, by the way), I'll pick Dell with SuSE. Add Apple Intel hardware running BSD-standard OS X Server to that comparison list, and I'll pick the Apple hardware because like the Dell hardware I can install Windows Server on it later.

    You do have to consider driver and software compatibility that Linux offers, but for basic corporate applications like file servers, web servers, etc., that's a non-issue. Some commercial software that runs on Linux already has a version for Mac OS X. The open source applications usually compile for Mac OS X easily.

    The fact that Linux is basically free, though, will make it the pick for some applications. There will also be some situations where the required applications have better support on Linux or no support at all for Mac OS X, and Linux would be the pick there.

    Basically I think this will put Apple in competition at the top end of Linux applications, and the low end of high-availability server applications.

    In workstations, this will put Apple where Jobs always wanted to be with NeXT -- high performance, high reliability workstations. What do people need with a high-end workstation when PC's are so powerful? Windows can't be all things to all people, and anybody who tells you Windows XP is just as good as a solid UNIX workstation OS is just plain full of sh*t.

    You can't provide what home consumers need to play video games without trade-offs for the CAD engineers or graphic designers. The same goes the other way -- you can't provide the stability for high-end users without trade-offs for those home and gameplayers.

    So, this will threaten Linux's gains in corporations, but when it comes to a guy downloading Linux to install on his home computer to play around with it, Apple won't compete there and doesn't want to. They've already stated in interviews that you will not be able to buy/install Mac OS X for anything but Apple hardware (PowerPC or Intel), so for the hobbyist and low-end workstations/servers, Linux will still dominate.

    But, for corporate or power users, a workstation with hardware and software integrated that can run either UNIX or Windows apps will be much more appealing than a Linux box. I've been trying to switch 100% to Linux on my desktop for more than five years, and still haven't been able to for various minor but important reasons...

  203. Could Apple's Intel Desktop Threaten Linux? by Master+of+Transhuman · · Score: 1


    No.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  204. sudo by lakeland · · Score: 1

    Yeah, OSX went the sudo route, and they did it a lot better than any of the linux distros.

    Specifically, you never log in as root/admin on osx (actually, you can't unless you change a few settings). Every time you do something which gives permission denied, you're not told that permission was denied, instead a friendly little dialogue box pops up asking for the name and password of someone in the sudoers file.

    Since requring root in osx is about as rare as it is in linux, this dialogue box popping up when you weren't expecting it causes mental alarm bells to start ringing. Of course, the standard dismissive argument here is that mac users will simply type their password whenever requested. *shrug*. I have found it is much easier to use a linux box without root than to use a mac without root, so there is some support for that argument.

    Contrast OSX's integrated sudo with the situation in linux, where an attempt to do inpromptu admin instead gets a 'permission denied' message 90% of the time, and 10% of the time you have to explicitly click on the 'do this as root' button. Looking at it that way, I can see why Linspire runs as root by default, KDE etc. just don't (yet?) have sudo integrated tightly enough.

    1. Re:sudo by Dcnjoe60 · · Score: 1

      Some Linux distros have improved on the sudo issue. Ubuntu comes to mind. At least if you do something from the gui that requires sudo, it pops up a enter password dialogue, similar to OS X. However, on the command line, it is true that you get the permission denied message. I'm not sure that's bad though, because it does keep you from accidently trashing your system. The nice thing is that if you do use sudo in a terminal, it remembers the password for a period of time, so that future sudo commands issued in that terminal don't require the password.

      When Ubuntu (and others) first came out with root not being enabled, I was not pleased. I was a heavy su user at the command line. That said, I do think I prefer the sudo way, now. Of course both sides (su vs sudo) argue which is more secure. But like the gnome vs kde or my-distro vs your-distro arguments, they board on religous fervor.

      Regardless, though, I don't like the idea of having the normal user be a root user. It might be convienent, but it really is too easy to screw things up. I do think an OS should have some mechanism to protect itself. The default user being root doesn't allow for any protection.

    2. Re:sudo by lakeland · · Score: 1

      I've installed ubuntu for a couple people, but haven't got around to trying it myself yet. I assume by "do anything in the gui that requires sudo..." you meant to say "do anything in the gui that requires root...". If so, this is exactly what I mean and I'm glad ubuntu is heading down this route. It will be nice if they get it working well, especially if kubuntu and linspire pick it up.

      Oh, and IIRC, OSX gives permission denied rather than the dialogue box from the command line, though naturally you can type sudo in the same way you can in linux.

    3. Re:sudo by Dcnjoe60 · · Score: 1

      Yeah, I should have said "do anything in the gui that requires root..." As an example, launching Synaptic pops up a password box, you enter your password and Synaptic starts.

      Some people complained thinking that any user would have that option, but they do have to in the sudoers list and IIRC, only the first user is automatically added to it.

      Anyway, now that I'm used to it, I prefer the sudo way to the su to root way. (Plus sudo creates a file showing you the commands you entered in case you need to troubleshoot what you did).

      I should add, for others reading this, that this isn't unique to Ubuntu, several other distros take the same approach.

    4. Re:sudo by shellbeach · · Score: 1

      Some Linux distros have improved on the sudo issue. Ubuntu comes to mind. At least if you do something from the gui that requires sudo, it pops up a enter password dialogue, similar to OS X.

      I've been recently trying out Ubuntu, and this behaviour - for both Ubuntu and OSX - is something that really worries me. The problem is that both OSes, in order to simplify things for their users, allow sudo to operate without a password for a set amount of time (15 mins in the case of Ubuntu, not sure what it is on OSX) after it's been used once. It would be trivial to write a script that when run, forks into the background and repeatedly tries to run, every 5 mins or so, "sudo [insert terrible command/script of your choice here]" ... e.g. "sudo rm -rf /" would go down well, but you could also open ports, create back doors, do anything at all.

      Of course, most of the time it would fail, but should the user decide they want to install some software, or change the system time, or whatever - anything that requires the use of sudo - then they're compromised. It makes viruses a real threat under *nix, and I think it's irresponsible and stupid. Having a root/administrator account is not a difficult concept to understand, when you explain it in terms of security.

      When Ubuntu (and others) first came out with root not being enabled, I was not pleased. I was a heavy su user at the command line.

      That's easy to fix: just do "sudo passwd", enter the root password of your choice, and away you go. And if you're like me, you disable the global sudo thing at the same time ...

    5. Re:sudo by Dcnjoe60 · · Score: 1

      I believe that even though they cache the sudo password, it is only for the process that started it (ie the terminal session). So, even if you sudo'd something, and this script were running, it would have to be running in the terminal session that had sudo running.

      You can test this for your self. Open a terminal and sudo something. Then sudo something else and there is no password needed. Open a second terminal, however and sudo something and you will need a password for it.

      Having sudo issued from the gui itself, as in launching synaptic, requires a password each time.

      Because of this, I think the risk of what you are proposing is relatively low, not impossible, just low.

      While I am familiar with how to enable the root account in both linux and OS X, my point was to try it their way, and it turns out I like it.

      I think that with an enabled root account, a script running in the background would have it easier than using sudo. My reasoning is that the script just needs to check that it is logged in as root and if so, all heck can break loose. If not, quitely keep polling. Of course that would be in a gui mode. In a terminal, it would be the same risk as a cached sudo.

      After using Ubuntu for six months or so, I can honestly say not having an enabled root account has not been a problem whatsoever, at least in my usuage and administration of the system.

  205. Clueless Mac zealot by jmorris42 · · Score: 1

    > First I have to know the difference between no-arch, 386, 586, 686,
    > etc... and download the right rpm.

    Not at all. Whoever installs the machine adds the usual third party repos and the problem reduces to two options.

    1. The program HAS been ported to your rpm based distro, either by the primary vendor or one of the 3rd party repo maintainers. (Dag and atrpms for RedHatish ones, PLF for Mandrake, etc.) You invoke the package manager whoever installed for you showed you how to use. On my machine (see my URL, guess which disto I run) I just pop open a console and type "up2date foo" to add the Foo package to my system. Others use yum, apt-get, aptitude, urpmi, etc. but they all work about the same.

    2. It isn't packaged for your distro. Same situation of the app isn't in Fink for your Mac. You have to know how to build it yourself. Only difference is on an rpm based machine we are mainstream. Most sites will have an srpm or at least a .spec inside the tarball. Take the case of a source tarball, just do "rpmbuild -tb foo.src.tar.gz" and wait a bit for the binary package to appear. No Grandma won't be doing this, but she won't be doing it on a Mac either unless a Mac or Fink binary exists.

    --
    Democrat delenda est
  206. Kinky OS by Crass+Spektakel · · Score: 1

    The mainproblems of desktop linux:

    -The GUIs are much too overloaded already. Every button which can be removed should be removed.

    -The GUI is not following the Unix-mantra of "everything is a file". Too much stuff in deeply nested menues instead of properties of a file (or an icon). Even Gnome/Ubuntu are not able to place a Dial-Up-Icon on the Desktop.

    -Too many distributions of files and drivers. When I last looked for a nv-driver it came in as many as 50 instances: four tar.gz, five debs and a whooooping 78 rpms (starting with suse 7.3 and ending with fedora 10.whatever)

    !!!Thats insane!!!

    At least within ONE distribution major release I expect only ONE driver (say one RPM for SuSE7, one for Debian3).

    --
    "Life is short and in most cases it ends with death." Sir Sinclair
  207. Apple will save linux! by ImaLamer · · Score: 1

    Standard hardware from Apple will help kill Windows. Linux will be a lot easier to develop when the hardware is standard.

    I think Apple should/will open the hardware to software developers. This will allow them to say: "Run OSX, it's already installed. Or you can take a chance with Linux".

    Linux distros which have a standard set of hardware to program and debug for will accelerate and stablize development.

  208. Re:Mac os will still only run on Mac's.... sure? by Raptor+CK · · Score: 1

    You've got it backwards.

    Within 10 days, someone will install Windows AND Linux on the Macintel.

    However, the Xbox is basically a PC, right? Why hasn't anyone made a PC run the Xbox OS so that they can play the games without buying the system?

    (Hint: It's hard to port closed-source software to similar platforms. Mac OS X may have an Open core in Darwin, but the parts that make it a Mac aren't even remotely open.)

    --
    Raptor
    "Procrastination is great. It gives me a lot more time to do things that I'm never going to do."
  209. The problem with Linux vs Windows or OSX by jonwil · · Score: 1

    is that on windows and on OSX, there is a lot of backwards compatibility built into the OS and runtimes.
    Any userland program written for OSX should run on the newest version.
    Ditto program written for win32, windows XP goes to great lengths to make backwards compatibility possible

    But linux does not (you cant build a program on RedHat 7.3 with the version of GCC included there and expect it to run on RedHat 8.0 without lots of effort or a recompile)

    Yet you can compile a program with visual studio 6 on an older version of windows and it will run just fine on the latest version.

  210. It's that darn licensing, again by bitspotter · · Score: 1

    Appdirs tend to make more sense for closed source apps - they tend not to be so concerned with dependencies, because a dependency is that much less code you don't own. Open source methodology instead, practically guarantees dependencies - that's the point! Stand on the shoulders of giants, because, well, you're allowed!

    Imagine trying to take the Debian repository and convert it into dependency-free frameworks, bundles, appdirs, and statically compiled binaries. That would be insane!

    Appdirs simply seem to trade usability for efficiency, and it's directly affected by the licensing style of the programs.

    More and more, I'm seeing that licensing is not separate from software engineering, and this is another example of how the licensing affects the engineering.

    As to the larger issue of Macs "threatening" GNU/Linux, I don't see it happening. A competitive marketplace could mean fewer GNU/Linux desktops "sold" or installed, sure. But share-alike software isn't a business. As such, i don't see how a closed-source OS (or, in this case, a desktop environment/API) can compete. Licensing is a feature. I got tired of having to pirate and crack all my apps a long time ago. Apple doesn't "threaten" GNU/Linux any more than Windows does. no matter what, I get to keep it, use it, improve on it here and there, and miraculaously watch a nice mature community make it better.

    I realize there's a certain amount of user base necessary to spur a critical mass of quality development, but I just don't see Mac OS X or Windows having the muscle to reduce GNU/Linux developers to abandon the platform in sufficient numbers to "threaten" its existence.

    Total world-domination marketshare, sure, but I don't really give a rat's ass about how popular my OS of choice is - as long as it's enough to keep it flourishing. Apparently, the little bit GNU/Linux has is plenty.

    Marketshare is for businesses, not for users.

  211. maybe the statement should be by john_uy · · Score: 1
    apple will slow the adoption of linux on the desktop.

    linux may be stuck in a niche market.

    apple will now have the ability of gaining not just from the the cpu but all the other hardware that comes with it such as graphic cards and audio cards.

    from this, applications may now include games and better multimedia applications in mac.

    users now have a choice other than windows (as currently, i don't like linux is an option in games and multimedia.)

    i welcome this change and looking into using a mac soon. i couldn't totally say that linux currently does job that i need with high efficiency (but the capabilities are now improving.)

    --
    Live your life each day as if it was your last.
  212. Beautiful? Mezzo Desktop? Ugh ... by Joosy · · Score: 1

    Took a look at the Mezzo desktop site, which Symphony uses, and was very unimpressed. What's supposed to be "revolutionary" (their word) about making piddly changes to how things are presented on the desktop?

    Also, I have to laugh at their statement that it "presents all needed information directly to the user." Thank you, but I'd rather decide for myself what information is needed.

    --
    I'm sick and tired of these hip, "ironic" sigs. This is an actual, honest-to-goodness no-nonsense sig!
  213. Re:Mac os will still only run on Mac's.... sure? by terjeber · · Score: 1

    If there is OSX running on x86 there will be a patch to run it on a PC 10 days after release.

    Nope, there won't be. The x86-based Mac will require hardware that is not present in your PC, and that you can't purchase from anywhere. Until Apple desides to do so (which is probably never) you will not be able to run OSX on a standard PC.

    This is one of the advantages Apple has always had over Microsoft. They design and know the hardware, and can therefore take advantage of it. On a PC, almost all of your menu and window drawing is done primarily by the CPU. The Intel thingy. Apple, knowing what (limited) harware is there, can delegate much more to other "CPUs" in your box, such as the GPU. Longhorn is supposed to do more of this.

  214. Somebody mod this up please by invalid_user · · Score: 1

    The fact that X11 runs on OS X is very very overrated. Many of us don't really appreciate that. We would, however, appreciate it if Apple can provide more incentives to us who uses only vi, latex, and the web browser. We don't want the flashy desktop, but we want to feel comfortable with these apps.

    We would also prefer our computers to be reasonably priced and not be an icon of self expression --- our work is important, the OS is not.

  215. Furthermore by einhverfr · · Score: 1

    What do you do when a security problem is found with a common shared library not included with the OS (say OpenSSL, Zlib, etc)?

    Do you, say, download and upgrade every one of your 30 or so programs that use this or do you simply upgrade the library?

    Disk space may not be a significant issue, but bandwidth is.

    --

    LedgerSMB: Open source Accounting/ERP
  216. Uh, how is-it related to the dependency problem?a by renoX · · Score: 1

    I don't how a better 'download dependency tool' is any help to the problem discussed before which is: how to avoid package management hell.

  217. three reasons to run Linux by zpok · · Score: 1

    Let's oversimplify and put people in categories depending on: why do they run Linux?
    1) It's cheap
    2) you really really like it
    3) you're convinced you have to use it for moral reasons

    I don't think Apple is a threat to the category one and three "market". People in category two however sometimes get converted. So what.

    I think that if Linux would want to be serious about standardization and user friendliness we'd have seen it by now. It may even be impossible to do, since Linux developers develop for linux because they like to, I don't see users dissuading them from doing things their way...

    Talking about the Linux market place and using words like threat is pretty complicated. I don't think you can just apply normal market dynamics (or those we profess to understand) to FOSS.

    Some FOSS programs that are used by one and a half individual are maintained for years by three programmers, some programs that are so popular they have over a million of downloads only have one maintainer. Who in their right mind wants to see Linux as "just another OS" and make meaningful predictions from there?

    So in short: yes, maybe linux users will buy Apple hardware or even run their FOSS on OS X. That's far from a threat situation, it just gives users more choice, which imo is a good thing.

    --
    I think, therefore I am...I think.
  218. About the blame by renoX · · Score: 1

    Sorry but Intel have to take the blame also from many of the problem of the x86: when they switched from 16 to 32, they could have added more registers the way AMD did with x86-64.
    Also there is no reason why MMX, SSE and the like suck (sharing MMX registers with FPU registers for MMX was braindead) while PPC has Altivec..
    And lets not forget about Netburst for the implementation part..