Slashdot Mirror


OpenDarwin Project Shutting Down

niabok writes "According to a message sent by Rob Braun to the OpenDarwin mailing lists, the OpenDarwin project will be shutting down, saying that 'OpenDarwin has failed to achieve its goals in 4 years of operation, and moves further from achieving these goals as time goes on.' The project's servers will remain online long enough to allow developers to move their various projects elsewhere."

470 comments

  1. Obligatory by patio11 · · Score: 3, Funny

    I guess they needed more intelligent design.

    1. Re:Obligatory by the_humeister · · Score: 2, Funny

      Make that OpenIntelligentDesign

    2. Re:Obligatory by FalconWarrior · · Score: 0, Redundant

      Nah, they just couldn't survive because they weren't fit enough.

    3. Re:Obligatory by Photar · · Score: 1

      OpenPunctuatedEquilbrium?

      --
      He who knows not and knows he knows not is a wise man. He who knows not and knows not he knows not is a fool.
    4. Re:Obligatory by Geoffreyerffoeg · · Score: 1

      The real obligatory here is BSD IS DYING!!!

  2. So they're changing the name to by Anonymous Coward · · Score: 0

    ClosedDarwin?

    1. Re:So they're changing the name to by dada21 · · Score: 1

      Or OpenIcthus.

  3. At least there'll be some profit by dada21 · · Score: 4, Interesting

    With a PageRank of 8 and an age of 4 years, that domain will sell to some SEO company very VERY fast. I wonder what they'll get for it.

    1. Re:At least there'll be some profit by fm6 · · Score: 1

      It's take more than a good pagerank to make a name valuable. The name itself has to mean something. There are porn folks who'll buy a popular name just to grab they extra hits, but they're not going to pay very much for it.

    2. Re:At least there'll be some profit by Megane · · Score: 2, Funny

      It's take more than a good pagerank to make a name valuable. The name itself has to mean something. There are porn folks who'll buy a popular name just to grab they extra hits, but they're not going to pay very much for it.

      Then I guess they should've named their project "Open Darwina". Oh yeah, open wide for me baby...

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    3. Re:At least there'll be some profit by kkiller · · Score: 1

      TFA states that the operators will run a DNS redirection service - so not sure if name will go to a SEO firm...

    4. Re:At least there'll be some profit by squiggleslash · · Score: 1

      Can't you, y'know, at least try to blame the government and/or "socialism" for this?

      --
      You are not alone. This is not normal. None of this is normal.
    5. Re:At least there'll be some profit by Anonymous Coward · · Score: 1, Insightful

      we didn't need another crappy wannabe Linux, we've already got BSD.

      What the hell are you talking about... BSD has been around since the 70's. If anything, Linux is a wannabe BSD.

    6. Re:At least there'll be some profit by Anonymous Coward · · Score: 0

      If a joke flies over your head and you don't hear it, does it make a sound?

  4. Quite Frankly.... by Cherita+Chen · · Score: 4, Funny
    Quite Frankly, I'm not surprised... It is well known that the OpenID project (Open Intelligent Design) is far more promising. For those who don't know, there is now a beta version dubbed "Kansas" slated to be released around Christmas.

    Stay tuned!

    --
    I'm not fat, just big boned...
    1. Re:Quite Frankly.... by BitwizeGHC · · Score: 4, Funny

      Actually I think they'll be both trumped by the project affiliated with the Flying Spaghetti Monster. Of course in some circles he is venerated as the Buoyant Spaghetti Deity; hence, OpenBSD.

      --
      N4st0r, trixx0r h0bb1tz0rz! Th3y st0l3 0ur pr3c10uzz!
    2. Re:Quite Frankly.... by fm6 · · Score: 1

      Sorry dude, someone made the ID joke 4 minutes before you did.

    3. Re:Quite Frankly.... by kfg · · Score: 3, Funny

      redundant
      adj.
      1. Taking the time to get it right.

      KFG

    4. Re:Quite Frankly.... by Anonymous Coward · · Score: 0
      I am aware of the OpenFSM project. I have been following bugtraq and have noticed that quite a few of the young men and women working on this endeavor are just not capable of handling the complex multi-threaded, multi-dimensional aspects of modeling such an entity. Remember what his highness once said, "Draw not an image of heaven nor of earth - nor anything above or below it, nor of his great noodly appendage, for this is surely blasphemy and ye must needs be smitten and brought low to the earth...

      It is quite obvious that he is more concerned with the growing number of pirates on this planet, and allowing young software engineers the opportunity to understand his noodly processes is just not a priority.

      I do wish them luck though. --CC

    5. Re:Quite Frankly.... by Anonymous Coward · · Score: 0

      fuck you buddy I'll do what I want

      KFG

    6. Re:Quite Frankly.... by DAldredge · · Score: 1

      OK

      DAldredge

    7. Re:Quite Frankly.... by russellh · · Score: 2, Funny
      Quite Frankly, I'm not surprised... It is well known that the OpenID project (Open Intelligent Design) is far more promising.
      Dude, the design phase of the ID project was done eons ago, literally, and before any implementation work was begun. It was never open. I think the requirements document must have been lost long ago though, because nobody knows wtf any of this stuff is. but EVERYONE knows that for a project this vast and complex, the only way to do it is to plan everything in advance from structures the size of galaxies to the smallest subatomic detail.
      --
      must... stay... awake...
    8. Re:Quite Frankly.... by ultranova · · Score: 1

      Actually I think they'll be both trumped by the project affiliated with the Flying Spaghetti Monster. Of course in some circles he is venerated as the Buoyant Spaghetti Deity; hence, OpenBSD.

      Hah ! The true form of the BSD mascot is well known. This proves that the Flying Spaghetti Monster is an evil plot ! Just look at the sauce for further evidence - it's clearly the color of blood, so eating spaghetti is equivalent to cannibalism !

      But the meatballs... The meatballs... That means that they are made of...

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    9. Re:Quite Frankly.... by ArAgost · · Score: 1

      Frankly, I'd stick to the classics. Is there an OpenCthulhu out there?

    10. Re:Quite Frankly.... by MrPsycho · · Score: 1

      Hey, when you have infinte time, crossing your t's and dotting your i's doesn't seem that bothersome.

    11. Re:Quite Frankly.... by fm6 · · Score: 1

      On Slashdot it seems to mean, "imagining you're the only person who can see an obvious joke".

    12. Re:Quite Frankly.... by Anonymous Coward · · Score: 0

      Yeah..F**ck him...

      KFG

    13. Re:Quite Frankly.... by Anonymous Coward · · Score: 0

      Try crystal meth... Oh wait, you already did that....

    14. Re:Quite Frankly.... by kfg · · Score: 1

      I know of at least one case where probably millions of people came up with the same joke on the same day; the introduction of mobile answering service:

      "I'm at home right now, but as soon as I go out I'll get back to you."

      But perhaps these days you need to be of a certain age to appreciate that one anyway.

      KFG

    15. Re:Quite Frankly.... by rp · · Score: 1

      Documentation?

      You must realize that for projects of this complexity, teamwork is Right Out - such a project is invariably carried out by a single genius who can overlook the entire design and implementation at once, and finds any effort to communicate with mere mortals an incredible pain. The "documentation" will be the combined work of a few bystanders who happened to catch a few words from our genius and have attempted to make sense out of them on paper. No surprise if it ends up looking like a incoherent, highly anecdotal bunch of scribblings, written in ancient Greek or worse.

    16. Re:Quite Frankly.... by Anonymous Coward · · Score: 0

      Silence, Untermench!

  5. Sad by QuantumFTL · · Score: 4, Informative

    I personally use Fink (and love it, for all of its flaws), but it's sad to me to see a good alternative source for OSS on OS X bite the dust. The only reason I'm able to enjoy a proprietary OS like OS X is because of the availability of many of the best OSS packages (if not all), and the compatability this affords me with linux-based environments. Hopefully Gentoo on OS X will go somewhere - does anyone know how it stacks up against Fink right now?

    1. Re:Sad by code+shady · · Score: 2, Informative

      I haven't tried Gentoo on OS X but I have tried DarwinPorts, the OS X version of the BSD ports system. If you are familiar at all with the ports system, then DarwinPorts will be right up your alley. I love it. It doesn't seem to have the breadth that fink does, but it's still rather nice.

      Unfortunatley, it does seem to be hosted on the OpenDarwin servers, so I wonder what the long term plans are for the maintainers of the project. I hope it can continue to exist, as I for one would miss the nice ports style installation and management on OS X.

      --
      Look out honey cause I'm usin' technology
      Ain't got time to make no apologies
    2. Re:Sad by taybin · · Score: 4, Informative

      This isn't the end of the darwinports project. That project was just hosted on the opendarwin servers.

    3. Re:Sad by QuantumFTL · · Score: 4, Insightful

      Thanks, I misunderstood the announcment. Still sad though, Apple should be giving more back to OSS - it owes much of its comeback to OSS (though not Free Software because it doesnt' seem to like GPL stuff much, like many corporations).

    4. Re:Sad by aitikin · · Score: 3, Interesting

      Extremely unfortunate for those of us who are OSS enthusiasts on OS X Gentoo on OS X is lightyears behind Fink. No GUI, very little support, and an update right now is impossible, because they have so many bugs that have to be worked out. I just tried to sync my portage tree and upgrade everything and I get errors galore! If people put effort into it, I'm sure it would be useful, but there haven't been many updates on it in forever and the forums are a major dissapointment. Gentoo has also impressed me with the community it has, but the Gentoo on OS X forum takes weeks for a response.

      --
      "Don't meddle in the affairs of a patent dragon, for thou art tasty and good with ketchup." ~ohcrapitssteve
    5. Re:Sad by Schraegstrichpunkt · · Score: 1
      though not Free Software because it doesnt' seem to like GPL stuff much, like many corporations

      You clearly don't know what "free software" means (or you're trolling, but I doubt that). See here, here, here, and .

    6. Re:Sad by timeOday · · Score: 2, Interesting

      We can argue about what "free" means all day, but OpenDarwin is a good example of why Linux adoption has left the BSDs in the dust - because the viral nature of the GPL binds all the users and contributors of Linux together (like the Borg :) I'm sure there are some days on which RedHat wishes they could fork off and go it alone, but nope, they can't.

    7. Re:Sad by hritcu · · Score: 3, Interesting

      Unfortunatley, it does seem to be hosted on the OpenDarwin servers, so I wonder what the long term plans are for the maintainers of the project. I hope it can continue to exist, as I for one would miss the nice ports style installation and management on OS X.

      OpenDarwin was just a host for DarwinPorts. They will just find another host. The interest in DarwinPorts is high enough so that you don't have to worry about them disappearing.

      --
      If you don't fail at least 90 percent of the time, you're not aiming high enough. (Alan Kay)
    8. Re:Sad by Mancat · · Score: 0, Flamebait

      Gentoo on OS X? Yuck. Please just use pkgsrc for a source-based package management system that is actually maintained by SANE developers.

      --
      hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
    9. Re:Sad by m874t232 · · Score: 3, Interesting

      though not Free Software because it doesnt' seem to like GPL stuff much, like many corporations

      Well, I agree that Apple isn't giving back enough to open source, but they have no hesitation using and shipping GPL'ed stuff. Two important examples are gcc and bash. And with gcc, for years, NeXT managed to comply with the GPL while avoiding giving anything useful back to the gcc project.

    10. Re:Sad by LizardKing · · Score: 3, Interesting

      And with gcc, for years, NeXT managed to comply with the GPL while avoiding giving anything useful back to the gcc project.

      Apart from an implementation of the Objective C frontend and runtime. But don't let facts get in the way of your ill informed ranting.

    11. Re:Sad by SnowZero · · Score: 1

      You will be assimilated. Netcraft confirms it.

    12. Re:Sad by TheRaven64 · · Score: 2, Interesting
      Apart from an implementation of the Objective C frontend and runtime

      Half right. The front-end came from NeXT. The runtime came from the GNU project. When you compile Objective-C with GCC you have the option of targeting the NeXT runtime, which is proprietary (and ships with OS X) or the GNU runtime, which is used by GNUstep and other non-NeXT Objective-C apps. Without a runtime, the front-end was completely useless.

      --
      I am TheRaven on Soylent News
    13. Re:Sad by Weedlekin · · Score: 4, Insightful

      Ah, so BSD-style licenses explain why Apache, the various Mozilla projects, and Python have been total flops that nobody uses for anything.

      Let's get real for a moment. Linux has become popular on servers for the same reason Java did, i.e. it generated a lot of press buzz, and has companies like IBM and HP pushing it to their customers (which they call "partners" to make things look cosy and pally). This means that the majority of corporate Linux setups (and by corporate, I mean any corporation, big or small) were chosen by people who don't know or care what the GPL is, have never heard of Stallman or the FSF, think a Gnu is a type of ungulate that lives in Africa, and would be happily using one of the BSDs if that was what their big "we take care of everything" hand-holding "partner" was telling them to use instead. Geeks within such companies have zero real-world input into any money based decision-making process, and use what they're told to use, hence the fact that Microsoft can sell them Windows and MS-Office for their their desktops, server-side Windows with Exchange for departmental services, Visual Studio for development, while Linux with Apache etc. live on their web server farms. If these people gave a fart about things like the GPL or what their pet geeks think is great, they wouldn't let anything from MS within a mile of their corporate buildings, and would be using open source tools to build their Linux-hosted webs instead of costly proprietary stuff like WebSphere and Tivoli, which are just incidentally supplied by those same "partners" who recommend, install, and support Linux.

      The GPL is therefore no more relevant to Linux's success than a lack of it has been to the immeasurably greater success of Microsoft's products. It is popular on servers because it works, is free as in beer, leverages existing corporate UNIX expertise, and a lot of business people have heard of it thanks to their everything-including-the-kitchen-sink IT service "partners", whereas few have heard of the various BSD variants. By the same token, it is a flop on the desktop because, for far too many non-geeks without access to a geek, it doesn't work properly with the hardware they have, fails to leverage their (albeit minimal) expertise with other operating systems and software, and most consumers either haven't heard of it, or know the name but are extremely hazy about what it is.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    14. Re:Sad by squiggleslash · · Score: 1

      That would be false on many levels.

      Apple doesn't appear to be discriminating against GPL'd software. The GCC compiler and (a snapshot of) the KHTML HTML rendering system are but two major components of Mac OS X that fall under it.

      Secondly, GPL'd software is open source, and BSD is free software, and vice-versa. The difference between open source and free software is, essentially, that open source concentrates on the ability of free software to form the basis of an open development process. Apple's development processes are far from open. It's difficult to contribute to Apple projects without forking them, and Apple has a tendency to fork other people's projects (KHTML to WebKit, GCC to Apple's version, various BSDs and Mach to Darwin, etc) rather than contribute back to them directly.

      In short, Apple has never used an open source development strategy, but it has on various occasions used free software, and released code as free software.

      --
      You are not alone. This is not normal. None of this is normal.
    15. Re:Sad by squiggleslash · · Score: 5, Informative

      This is the kind of nit-picking I hate on Slashdot. He didn't say "while avoiding giving anything back to the gcc project", he said "while avoiding giving anything useful back to the gcc project". He qualified the word "anything", and you've responded as if he didn't.

      Objective C was close to useless for the longest time in GCC, which adopted Apple's changes largely, I think, in the hope someone would make it a viable system in the future. A crude object framework consisting of just the Object class was added (note: not NSObject) and a small run-time, by independent (non-Apple) developers, but until GNUstep came along there was nothing you could really do with all of that unless you spent a few months developing a basic class library. Basic meaning pretty much "everything". No string classes, IO classes, or anything else, existed unless you chose to write it.

      --
      You are not alone. This is not normal. None of this is normal.
    16. Re:Sad by Eivind+Eklund · · Score: 2, Informative
      The GPL is not a requirement for something being classed as free software; there's numerous other licenses. I personally work with the BSD class of licenses mostly because I see GPL as unfree.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    17. Re:Sad by Anonymous Coward · · Score: 0

      Oh, really fanboi? And who finds Objective C useful besides Apple? Talk to me when you get your head out of Steve Jobs' ass.

    18. Re:Sad by sydb · · Score: 2, Insightful

      Of course the GPL is relevant to Linux's success; it comes with a political / philosophical movement behind it. Whether or not that matters to end users is not so important, but a lot of hackers seem to be motivated by the philosophy. Without the hackers, there would be no Linux.

      --
      Yours Sincerely, Michael.
    19. Re:Sad by Anonymous Coward · · Score: 0

      I'm pretty sure the estimated 25 million Mac OS X users find Objective-C very useful indeed.

      (Get it? Users ... useful?)

    20. Re:Sad by bill_mcgonigle · · Score: 2, Informative

      Apple was also a contributor to the SSA project for GCC, which I believe improves all frontends. IIRC, their interest was in using the SSA tree for autovectorization work.

      So (and somebody correct me if I'm wrong), if you're using gcc to compile c++ on linux, you're using Apple code.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    21. Re:Sad by dominator · · Score: 3, Informative

      Speaking of history lessons and facts, let's not forget that RMS needed to due everything short of suing NeXt to open the Objective C compiler's and runtime's sources:

      http://www.fsf.org/licensing/essays/pragmatic.html

      NeXt didn't want to contribute their code back to the Free Software movement. They even had some sneaky attempts (shipping just the .o files) to keep it proprietary. Only when lawyers got involved, did NeXt release their changes. They gave something back to the gcc community only when a gun was to their head.

    22. Re:Sad by Anonymous Coward · · Score: 1, Informative

      It's a shame the comment was about NeXT when they were NeXT, not Apple.

    23. Re:Sad by Weedlekin · · Score: 1

      I severely doubt that Linux would have ceased to exist (or be still-born) without the GPL, because the sheer number of thriving open source projects with much more liberal licenses indicates that there are a lot of hackers who don't like the FSF or anyone else telling them what they can do with stuff they write. Would it have been as successful under a different license? Nobody can really say for sure, but not being GPL hasn't stood in the way of Apache becoming the most popular web server, and Apple have managed to put at least as many primarily BSD-based UNIX-like systems on desktops as all the Linux distros put together. Note also that Linux as a system rather than merely a kernel originally lifted a lot of BSD code, so BSD also played a significant role in its genesis (and portions of it are still there), as did Minix, which Linus used to write and test Linux in the early days (but did not, as some primarily MS-paid shills have claimed, copy any Minix code).

      The creation, subsequent amplification, and promotion of Linux is therefore rather more complex in licensing terms than certain GPL advocates like to pretend, especially nowadays, when Linus Torvalds is telling us that most of the significant contributions to the Linux kernel come from paid programmers working in companies such as IBM, RedHat, and Novell/Suse, most of whom would work under any license that had a pay-check on the end of it.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    24. Re:Sad by timeOday · · Score: 1
      Let's get real for a moment. Linux has become popular on servers for the same reason Java did, i.e. it generated a lot of press buzz, and has companies like IBM and HP pushing it to their customers (which they call "partners" to make things look cosy and pally).
      More specifically, because both IBM and HP push it - the same code base - instead of both making it into incompatible proprietary products, as happened to the BSD variants. All of your reasons, i.e. "everybody has heard of it," are compatible with that theory, if you look just one level deeper. Stop spending all your effort arguing against what nobody claimed - that Linux is more popular because people are emotionally attached to the GPL.
    25. Re:Sad by be-fan · · Score: 3, Insightful

      I think you're really missing the point. Consider the reasons why Open Darwin failed as a project. They couldn't generate the community interest and involvement necessary to further the project. This in itself is surprising, because OS X has a relatively large userbase, and is different enough from other *NIXs to be interesting.

      So why was nobody interested in Open Darwin? Because it's Apple's product. There is no sense of community ownership, or community involvement, working on Open Darwin amounts do doing free R&D for Apple. Moreover, Apple won't even release the really interesting parts of OS X, and can, at any time (as they've demonstrated with the x86 release), withhold code if it is convenient for them to do so.

      It's naive to believe that GPL vs BSD has nothing to do with the failure of Open Darwin. If the BSD code had been GPL'ed, Open Darwin could be a true community project. Apple wouldn't be able to withhold code at any time, it would have to release interesting kernel drivers, and they couldn't take peoples' changes and close them back up later. Of course, that is not to say that just GPL by itself would've compensated for the complete lack of tact with which Apple approaches its open source projects, or that this occurrance is necessarily the fate of all BSD licensed projects, but rather that this event is a textbook demonstration of one of the shortcomings of the BSD license.

      --
      A deep unwavering belief is a sure sign you're missing something...
    26. Re:Sad by LizardKing · · Score: 1

      The default object is useful - I've personally coded a number of applications that didn't need the functionality or overhead of a full Foundation like framework and derived its classes from Object. An example of the kind of applications I am talking about is a web server, where having OO support in the implementation language was useful, but where things like dynamic string handling weren't.

    27. Re:Sad by squiggleslash · · Score: 1

      In a sense, this was NeXT's most significant contribution to Free Software. They pretty much confirmed that the GPL wasn't a joke license, and that you can't get around it simply by distributing your binary components separately, or other similar tricks.

      ATI and other makers of binary or non-GPL'd kernel modules (non-GPL'd in ATI's fglrx case), please note.

      --
      You are not alone. This is not normal. None of this is normal.
    28. Re:Sad by LizardKing · · Score: 1

      The first two runtimes came from the GNU project (Stallman himself wrote the second one, and deprecated the #import preprocessor directive which is why I still had Makefiles with -Wno-import aliased as RMS_ME_HARDER). The third one came from a Norwegian guy who worked at NeXT.

    29. Re:Sad by squiggleslash · · Score: 2, Informative
      Ah, so BSD-style licenses explain why Apache, the various Mozilla projects, and Python have been total flops that nobody uses for anything.

      None of the examples you cite are developed under the BSD license.

      Further, Mozilla is GPL'd (the MPL is also available, which is also copyleft), Apache is also under a copyleft license (see 4. Redistribution) which is effectively viral as any licensing must not conflict with the APL. Only Python has a non-copyleft license.

      --
      You are not alone. This is not normal. None of this is normal.
    30. Re:Sad by supabeast! · · Score: 1

      "...Apple should be giving more back to OSS - it owes much of its comeback to OSS..."

      Apple doesn't owe anything to OSS! OSS authors give their code away, and in the case of BSD licensed works, aren't asking for, or expecting, anything back in return. If they wanted to get something back, they would have (or should have) been selling the code for profit in the first place. The point of releasing software under free or OSS licenses is to better civilization in one form or another - not to expect other people to help one with the code, or hope corporate users will rain funding and other laurels on the coders in a display of thanks.

    31. Re:Sad by mstone · · Score: 1

      The difference between Open Source and Free Software is that Free Software is designed to be 'embrace and extend'-proof, while Open Source is not.

      I don't mean that as a criticism of either license. Both have a legitimate place in the market. Open Source licenses like the BSD license are very good at getting technology established as a standard. Windows does or has used the BSD TCP/IP stack, if memory serves me.

      The GPL exists to keep companies from doing what Microsoft did to Kerberos: taking an established technology, bolting on a few proprietary extensions, pushing the new product into the market until it gets a foothold, then making the proprietary extensions 'necessary' to interact with other popular software.

      We need both tools. TCP/IP would never have become the default standard if it had been released under the GPL. Meanwhile, Free Software gives the F/OSS community a way to fence its established technologies off from corporate encroachment, thus guaranteeing the continued openness of that technology.

      Bottom line: OS X was built using technology from FreeBSD. It could never have been built on Linux.. not for technological reasons, but for licensing reasons.

    32. Re:Sad by squiggleslash · · Score: 1

      Nope. That's complete nonsense. Free Software is purely about freedom. Open Source is a the marketing of Free Software as a development methodology. OpenBSD is Free Software, and Theo would not take kindly to you arguing that it isn't, and likewise he'd not take kindly to you claiming that he's in favour of "embrace and extend".

      That's it, pure and simple. The BSD license is a recognized Free Software license and does not do any "embrace and extend" or any other nonsense. The GPL is a recognized, and popular, Open Source license, as is the MPL which is, like the GPL, copyleft. If you take a look at both the FSF and OSI's lists of licenses, you'll see they're more or less the same, with an even mixture of copyleft and non-copyleft licenses alike.

      If you don't like it, tough. That's the way things are. If you want to make some point about copyleft vs non-copyleft, make it, but don't make unsubstantiatable claims about "what open source is" and "what free software is" that are demonstrably, provably, false.

      --
      You are not alone. This is not normal. None of this is normal.
    33. Re:Sad by MikeTheC · · Score: 1

      I agree: It's sad to hear about OpenDarwin, but I have to wonder how much of a difference it's going to make now that Apple's firmly entrenched in the x86 platform. BTW, not sure about Gentoo, but I recently nuked my PB and dual-booted with Ubuntu. I'm lovin' every minute of it!

    34. Re:Sad by rjstanford · · Score: 2, Insightful

      If the BSD code had been GPL'ed, Open Darwin could be a true community project. Apple wouldn't be able to withhold code at any time, it would have to release interesting kernel drivers, and they couldn't take peoples' changes and close them back up later.

      Actually, if the BSD code had been GLPd, Apple wouldn't have used it as a starting point.

      --
      You're special forces then? That's great! I just love your olympics!
    35. Re:Sad by sydb · · Score: 1

      That's OK, I didn't say it would not have existed without the GPL. I said I think GPL licensing had a significant positive factor in it's rapid growth.

      Above and beyond developers' passion, it's worth noting that - as you know - GNU existed before Linux, and having Linux GPLed means that they are very easy bedfellows. This must have helped, and I think still helps. GNU has vocal proponents in the shape of Stallman and the FSF, while the BSD arena doesn't seem to have a similar counterpart.

      --
      Yours Sincerely, Michael.
    36. Re:Sad by mstone · · Score: 1

      The BSD license is a recognized Free Software license

      Correction on my part: The original BSD license. Check the FSF for details. And you have read the FSF discussion of the difference between 'Free Software' and 'Open Source', haven't you? Included in that text is:

      The focus of their business is on developing proprietary add-ons (software or manuals) to sell to the users of this free software. They ask us to regard this as legitimate, as part of our community, because some of the money is donated to free software development.

      which sounds like the FSF doesn't cotton to embrace-and-extend tactics to me.

      and likewise he'd not take kindly to you claiming that he's in favour of "embrace and extend".

      I understand there are a lot of things Theo doesn't take kindly. That's just part of his charm. The modified BSD license is not a copyleft license, thougn, or at least the FSF says it isn't:

      If you want a simple, permissive non-copyleft free software license, the modified BSD license is a reasonable choice.

      The FSF recognizes it as being compatible with the principles of Free Software, but the lack of copyleft keeps it from being an embrace-and-extend-proof license.

      Theo is a smart guy, and I'm sure he knows that.

    37. Re:Sad by aichpvee · · Score: 1
      The creation, subsequent amplification, and promotion of Linux is therefore rather more complex in licensing terms than certain GPL advocates like to pretend, especially nowadays, when Linus Torvalds is telling us that most of the significant contributions to the Linux kernel come from paid programmers working in companies such as IBM, RedHat, and Novell/Suse, most of whom would work under any license that had a pay-check on the end of it.

      Which is almost definitely true that they would work under whatever license they were paid to. The difference is that most of the code they wrote to get those paychecks would have stayed locked up as has happened with OSX.

      As for there being any chance that Linux would have been as successful under another license, that's kind of a no brainer. There's almost no way it could have been. Just look at what has happened to the BSDs. Sure they're around and people work on them and use them, but they're not nearly as big a deal as Linux and most of their corporate "partners" just take the code and run like apple has.

      Maybe someone should release a GPL'd BSD and see how well it does, though it's kind of late in the game to start that up now.
      --
      The Farewell Tour II
    38. Re:Sad by be-fan · · Score: 1

      Right, because big companies like IBM, Novell, and even Apple don't use GPL'ed code as a basis for their products...

      In any case, if Apple had not used said BSD code, what would be different? Apple gives almost nothing back to the BSD community as it is. How would the community have benefited from Apple's use of the code?

      --
      A deep unwavering belief is a sure sign you're missing something...
    39. Re:Sad by QuantumFTL · · Score: 1

      What liscenses are "free software" other than GPL/LGPL? As I understand it, BSD does nothing to ensure many of these rights, and plenty of creative commons, or anti-government/anti-corporate/anti-military clauses also restrict these fundamental "rights."

    40. Re:Sad by QuantumFTL · · Score: 1

      Well they are very careful with the viral (yes, I feel it's appropriate) nature of the GPL, and are careful to never put GPL stuff (at least that we know of) anywhere inside the OS directly, where it would be linked with something proprietary. So GPL utilities are fine for them, but not drivers or other kernel goodies, unfortunately.

      Sometimes I wonder, no matter what its intentions, if GPL is actually helping the masses much (vs BSD liscensed software, etc), or mostly idealists/software purists and those whose situation affords the effective running of Linux-based OSes.

    41. Re:Sad by QuantumFTL · · Score: 1

      Firstly, KHTML is LGPL, which is a very different beast from GPL, being non-viral, among other things, allowing its use in proprietary software.

      Secondly, I looked on the FSF site and BSD is "free software", but seems to be far less "free" (according to Stallman, with whom I disagree vigorously) than the GPL.

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

      Apart from an implementation of the Objective C frontend and runtime. But don't let facts get in the way of your ill informed ranting.

      But he said "useful"... or did you miss that part?

    43. Re:Sad by wkcole · · Score: 1
      I personally use Fink (and love it, for all of its flaws), but it's sad to me to see a good alternative source for OSS on OS X bite the dust.

      That points out why it is shutting down. Not much of anyone outside of a handful of core developers ever cared to understand what OpenDarwin was intended to be. DarwinPorts (e.g. the Fink alternative) was not it. Apple doesn't really want an independent developer community hacking on Darwin and defining what Darwin is. So now, they won't even have anyone trying to do that.

    44. Re:Sad by QuantumFTL · · Score: 1

      Nice link, but too bad it was couched in such inflamatory language...

    45. Re:Sad by QuantumFTL · · Score: 1

      Apple should be promoting OSS as an "outsourced" development house - I'm sure even just having one full-time guy working with fink could help OS X compete better with linux for software development and even server stuff. I'm not saying Apple should do anything against its best interests - I'm saying their best interests are served by keeping the "gravy train" coming.

    46. Re:Sad by m874t232 · · Score: 1

      Apart from an implementation of the Objective C frontend and runtime. But don't let facts get in the way of your ill informed ranting.

      As I was saying: NeXT complied with the letter of the GPL by dumping a hacked version of gcc on the world, but that wasn't useful for the gcc project, at least not for a long time.

      Whether they did this out of laziness or whether it was a deliberate strategy, I don't know. But I think they hurt themselves big time with it. If they had worked harder to make sure that the official gcc compiler releases had a useful Objective C implementation in them, Objective C would probably be a widely used, mainstream language today.

    47. Re:Sad by Anonymous Coward · · Score: 0

      I venture to say that, except for Apple's i-Apps, most OS X software in widepsread use is not written in Objective C. In fact, I suspect it's not even written using Cocoa (at least not directly).

    48. Re:Sad by Schraegstrichpunkt · · Score: 1

      Look at the last link I posted. The FSF maintains a list.

    49. Re:Sad by m874t232 · · Score: 2, Insightful

      Well they are very careful with the viral (yes, I feel it's appropriate) nature of the GPL, and are careful to never put GPL stuff (at least that we know of) anywhere inside the OS directly,

      Aren't you listening? NeXT had no trouble using gcc, no matter how "viral" you think the GPL may be. What they weren't doing is satisfying their requirements under the GPL, and once they were forced to, their contributions were nearly useless.

      Sometimes I wonder, no matter what its intentions, if GPL is actually helping the masses much (vs BSD liscensed software, etc), or mostly idealists/software purists and those whose situation affords the effective running of Linux-based OSes.

      Most of what Apple is shipping as "OS X" is based on open source software: the kernel, the compiler, the command line environment, and many of the libraries. I wouldn't be surprised if the total contribution of Apple developers to OS X is less than 10%. And for many of those open source software packages, Apple has had no problems in choosing software under the GPL license. Apple doesn't mind getting software for free, they just don't like having to comply with the licenses.

      Is Apple "idealist" when they demand that I pay for their software? I don't think so. And neither are GPL software developers when they demand that Apple comply with the GPL. If Apple doesn't like the GPL, they can buy all the software they need commercially, or choose BSD equivalents.

    50. Re:Sad by nuzak · · Score: 1

      > ATI and other makers of binary or non-GPL'd kernel modules (non-GPL'd in ATI's fglrx case), please note.

      Linux specifically exempts kernel modules from the GPL.

      --
      Done with slashdot, done with nerds, getting a life.
    51. Re:Sad by QuantumFTL · · Score: 1

      gcc is not part of the OS. In fact, most people run OS X without gcc being installed on their computer and wouldn't know it if it was installed.

    52. Re:Sad by SteeldrivingJon · · Score: 1


      "As I was saying: NeXT complied with the letter of the GPL by dumping a hacked version of gcc on the world, but that wasn't useful for the gcc project, at least not for a long time."

      I don't recall "utility to the gcc project" as being a requirement of the license. NeXT's needs were orthogonal to those of the typical gcc user. Big deal.

      --
      September 2011: Looking for Cocoa/iOS work in Boston area Cocoa Programmer Quincy, MA
    53. Re:Sad by Mancat · · Score: 1

      I just can't help myself!

      --
      hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
    54. Re:Sad by Anonymous Coward · · Score: 0
      Er, let's see, the first statement was:

      And with gcc, for years, NeXT managed to comply with the GPL while avoiding giving anything useful back to the gcc project.


      The reply to that was:

      Apart from an implementation of the Objective C frontend and runtime. But don't let facts get in the way of your ill informed ranting.


      The response to that was:

      As I was saying: NeXT complied with the letter of the GPL by dumping a hacked version of gcc on the world, but that wasn't useful for the gcc project, at least not for a long time
      .

      So, the fact that they complied with the license was a given, the dispute is over whether they did anything useful. And your contribution is ten:

      I don't recall "utility to the gcc project" as being a requirement of the license.


      See, that should have been phrased, "I agree it wasn't useful, and NeXT merely complied with the requirements of the license." Because you were agreeing with him.

      Now, your next bit:

      NeXT's needs were orthogonal to those of the typical gcc user.


      is not true. NeXT needed Foundation or some equivalent for an Objective C compiler to be more than a toy, and needed gcc as a compiler. The typical gcc user needed Foundation or some equivalent for Objective C support to be more than a toy, and needed gcc as a compiler. The needs weren't orthogonal, they were identical. It's merely that NeXT decided not to hand over anything they weren't forced to by the GPL -- and even then only did so after they were threatened for violating the GPL.

      And the result is that because you could only write useful Objective C for NeXT, while you could write useful C++ for any platform, it was idiotic to spend effort on Objective C, and NeXT doomed itself by its choice to release as little as legally possible.

      The only reason NeXT managed to avoid dying is that Apple lacked the basic competence shown by Microsoft, IBM, Be Inc., Sun, and others (including the unpaid volunteers of GNU/Linux, *BSD, and MiNT), and had to buy someone else's protected mode, preemptive-multitasking operating system. (If Apple had just had the sense to take 4.4BSD-Lite in June 1994, got it running on PowerPC, and ported over the A/UX Finder . . . )
    55. Re:Sad by rjstanford · · Score: 1

      How would the community have benefited from Apple's use of the code?

      The same way that the rest of us have - with the addition of another viable Windows competitor with serious commercial backing, marketing, retail presence, et cetera.

      --
      You're special forces then? That's great! I just love your olympics!
    56. Re:Sad by m874t232 · · Score: 1

      gcc is not part of the OS. In fact, most people run OS X without gcc being installed on their computer and wouldn't know it if it was installed.

      What does any of that have to do with anything? My original claim was that NeXT/Apple has no trouble using GPL'ed software, but they are trying to avoid giving back to the community.

      Your attempts to talk about what and what isn't part of the "OS" are an attempt to distract from how sleazy NeXT and Apple have behaved in the past. Mac zealots like you have no business pointing fingers at open source developers: you are far worse in your zealotry, and you just take and don't give back.

    57. Re:Sad by QuantumFTL · · Score: 1

      Yes i'm such an Apple zealot, which is why I wrote this post and this post, and run Gentoo on my server.

    58. Re:Sad by cthulhu11 · · Score: 1

      Darwinports has the same fundamental problem that Fink does: someone will slap in an initial version of package. They'll set it up badly, and never update it.

    59. Re:Sad by hritcu · · Score: 1

      I'm using Fink and I'm pretty happy with the quality of the packages. And well ... there is little alternative anyway ... so it's better with DarwinPorts on the scene than it would be without them.

      --
      If you don't fail at least 90 percent of the time, you're not aiming high enough. (Alan Kay)
    60. Re:Sad by byolinux · · Score: 1

      Curious... why do you disagree so much with RMS?

    61. Re:Sad by QuantumFTL · · Score: 1

      That's a good question. I do thank the FSF for so much of what they've done, as I do very much enjoy GNU, but I guess I see computer programs as being nothing more than large strings of integers put into a computer. I understand why we, as a society, allow the copyright of quantities of information like that, but I fail to see where the FSF's supposed fundamental human right to have a human-readable "recipe" for those integers made available to everyone in a compulsary fashion (and, on top of that, calling that freedom). The DMCA is a travesty, but so is telling me what I can and cannot distribute, and if the FSF had their way, *all* software would be GPL.

      I believe that the GPL has slowed the development of much OSS, and its use in industry (unlike the LGPL which I absolutely love and think is rather fair). Look how far BSD has gotten, without any of the viral "use even just a bit of our code, and you have to expose the guts of whatever you used it in to all of your competitors, and allow others to give it away for free." I don't live in some magical accademic fairy land where everything is paid for by government grants, and my views on proper software rights (with respect to corporations and individuals) reflect that.

      It's always possible I've got it totally wrong, but I think the fight against software patents, "trusted computing", DRM and DMCA is much, much, much more important than the fight against software without source code provided. Maybe some day someone will tell me why I magically deserve to see the source code to any binary program I happen to be given.

    62. Re:Sad by Weedlekin · · Score: 1

      "I think you're really missing the point. Consider the reasons why Open Darwin failed as a project."

      Indeed. But as you'll see in a moment, it is you who is missing the point.

      "So why was nobody interested in Open Darwin? Because it's Apple's product."

      Open Darwin had nothing to do with Apple -- It was an entirely third party effort at making a fork of Apple's Darwin. The rest of your comments about sense of community etc. do not therefore require answering, because they are entirely based on your own misconceptions about Open Darwin.

      "It's naive to believe that GPL vs BSD has nothing to do with the failure of Open Darwin"

      Not as naive as failing to read the article, and thus assuming that Open Darwin and Apple Darwin are one and the same. Again, the rest of your comments are irrelevant, because they address points that are not pertinent to any issue surrounding Open Darwin's closure.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    63. Re:Sad by Weedlekin · · Score: 1

      "None of the examples you cite are developed under the BSD license."

      Where did I say they were? I stated that they are available under _less restrictive_ licenses than the GPL, period.

      "Mozilla is GPL'd (the MPL is also available, which is also copyleft)".

      You are correct -- I was wrong in this case.

      "Apache is also under a copyleft license (see 4. Redistribution) which is effectively viral as any licensing must not conflict with the APL"

      BSD code cannot be used in ways that conflict with the BSD license either, so by your definition it is also viral, and so are all other licenses apart from those of public domain works. And when one considers that the entirety of the APL basically states that compliance is a matter of leaving any copyright notices in source code (which does not have to be made available to others in any shape or form), and distributing a text file containing this copyright information to end-users, it begins to look very much like the BSD license indeed, where one is also required to maintain the original copyright info in source files that don't have to be made available to anyone else, and tell end-users about said copyrights.

      Thus, while I was wrong about the MPL, you are also wrong about the APL, which is as close to a BSD license as it is possible to get without being a BSD license: score 1-1.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    64. Re:Sad by Weedlekin · · Score: 1

      "I didn't say it would not have existed without the GPL. I said I think GPL licensing had a significant positive factor in it's rapid growth."

      If you said "was a significant factor in its rapid development", I would be in full agreement.

      "Above and beyond developers' passion, it's worth noting that - as you know - GNU existed before Linux, and having Linux GPLed means that they are very easy bedfellows."

      It did indeed, although it should be noted that GNU tools have also been used for a wide variety of non-GPL projects over the years, mainly due to the fact that they capable of targeting a wide variety of platforms and architectures (which is of course due to their profoundly open nature).

      "GNU has vocal proponents in the shape of Stallman and the FSF, while the BSD arena doesn't seem to have a similar counterpart."

      This is very true. However, most non-Geeks haven't heard of the FSF or RMS, and a good many of those who have regard RMS in particular as being a fringe loony with a cabal of social misfits who worship him and therefore believe everything he says. Linus Torvalds is far more famous outside geekdom (and indeed inside it), and has I think done far more for Linux in particular than RMS because he presents it as something that has concrete benefits rather than part of a social movement consisting of what the public at large thinks of as people who get nosebleeds arguing about Star Trek and whether Spiderman could beat the Green Lantern.

      So perhaps it would be more accurate to say that what the BSDs lack is an equivalent for Linus, i.e. a person who is not only quite well known by both geeks and non-geeks, but also respected by both groups because he can talk to each of them in terms they understand without pissing many people off.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    65. Re:Sad by Richy_T · · Score: 1

      A big part of the success? Linux uses nearly the same letters as Unix. Quite clearly it is supposed to be like Unix. Therefore it inherits a lot of the Unix cache. BSD, OpenBSD, FreeBSD... The names don't evoke anything familiar. And what does BSD even stand for? Something fairly long and complex to remember, especially for C[EFA]Os... Linux is simply "Linus's Unix". It's all about the branding...

      BSD needs to rename itself. Something with an X and an U in it. Ubix or something...

      Rich

    66. Re:Sad by Anonymous Coward · · Score: 0

      Well, sorry, I thought you were an Apple zealot, but I see now that your problem has nothing to do with that; you just like to argue for argument's sake, with no goal, purpose, or coherency.

    67. Re:Sad by Richy_T · · Score: 1

      Note that this is also why "Linux" and not "GNU-Linux" or other encumberances.

      Rich

    68. Re:Sad by Richy_T · · Score: 2, Funny
      whether Spiderman could beat the Green Lantern.


      OK, now you're trolling...


      Rich

    69. Re:Sad by byolinux · · Score: 1

      When you say the GPL has slowed the development of free software, do you mean by volume, or specific pieces of free software?

      You speak of the 'viral' aspect of the GPL - do you have a better way of allowing people to use code, whilst preventing anyone from taking away freedoms?

    70. Re:Sad by QuantumFTL · · Score: 1

      I do not recognize ownership of source code of any binary you have been given as some kind of fundamental right, but RMS does. It's rather difficult to argue about what should be a fundamental right - hundreds of years ago, many rights we now consider fundamental would be the subject of much laughter or scorn.

    71. Re:Sad by byolinux · · Score: 1

      I wouldn't say he thinks of it as a fundamental right.. maybe he does. Maybe it's a language thing.

      To me, RMS is saying that all the software you use should offer you freedom.

      Freedom in software comes down to four things.

      Freedom to run the program, for any purpose
      Freedom to study and change the program
      Freedom to copy the program and give a copy to your friend
      Freedom to distribute modified versions of the program

      All free software offers that. The main difference is that some software licenses allow these freedoms to be taken away from you, and others don't.

      I believe they shouldn't be taken away from people. The GNU GPL achieves that.

    72. Re:Sad by Weedlekin · · Score: 1

      "Which is almost definitely true that they would work under whatever license they were paid to. The difference is that most of the code they wrote to get those paychecks would have stayed locked up as has happened with OSX."

      Whether or not it would have stayed locked up has no bearing on the assertion that the GPL is important to Linux's success. All that matters to those paid developers is that _they_ have access to the source code, and source code to just about anything can be obtained legally by the likes of IBM, for whom a few million in licensing fees is chump-change.

      "As for there being any chance that Linux would have been as successful under another license, that's kind of a no brainer. There's almost no way it could have been. Just look at what has happened to the BSDs. Sure they're around and people work on them and use them, but they're not nearly as big a deal as Linux "

      And Linux is not nearly as big a deal as Windows, so by your logic, Windows must have a license that is far superior to the GPL, and Apple's iTunes store owes its success to licenses that are that are just a bit nicer than those of the competition.

      Ballmer: "it's about licenses, licenses, licenses!".

      Jobs: "The next thing I'm going to show you is a new license that we've been working on for quite a while. You're going to love this...".

      --
      I'm not going to change your sheets again, Mr. Hastings.
    73. Re:Sad by Weedlekin · · Score: 1

      "It's all about the branding..."

      And publicity, which Linux got in huge amounts during the Internet bubble of the late 1990s, when everybody was raving about anything that had young, hip people using the Internet to do stuff. Almost everyday, the media had various articles about pairs of 19 year-olds who'd become instant billionaires from people rushing to invest huge sums in their brilliant idea of using "The Internet!" to sell sandwiches at a loss. After all, so the reasoning went, young people understand "the Internet!" in diverse ways, so ideas that would have been laughed at in a more conventional setting were taken very seriously when accompanied by the magic words "young" and "Internet!".

      Thus enter Linux, which was started by somebody young on "The Internet!", subsequently developed by a community of mostly young people over "The Internet!", and run by the young who used "The Internet!" to download it for free, after which they would do the kind of mysterious, magical things that the young did on "The Internet!". Given all those magical ingredients, it just had to be something great, so a bunch of startups run by hip, young people appeared to "make money" off something people could legally obtain for nothing, to the customary media fanfare that surrounded anything containing "young" and "The Internet!". Customers of the old IT giants thus started to ask about this Linux thing that they'd seen in Newsweek, and after being badly burned by their prior failure to foresee the collapse of the minicomputer market, they were determined not to lose those customers to some startup run by hip young people selling something that everyone, including the IT giants, could download complete with source code for free, and also get free help in adapting it to their own systems.

      By contrast with all the hip youth and "Internetyness" surrounding Linux, the BSDs came from a time before the web existed (and the web was what most people meant when they said "The Internet!"), and tended to be maintained and used by crusty academics and fat middle-aged guys with beards and kaftans, both of whom were the very antithesis of youth and hipness. Linux mostly ran on young peoples' PCs who were happy to be filmed, photographed, and interviewed, whereas the BSDs tended to live on servers and multiuser systems crewed by alpha-geeks to whom the press were "suits" who must be avoided at all costs; Linux had a rebel culture that just begged to be described in terms like "exciting", "fast moving", and "grass-roots", and could produce eye-catching headlines such as "Could This Be Microsoft's Nemesis?", whereas BSD advocates droned on about maturity, stability, up-times, and other such (to the press) dull trivia, and thought Microsoft was "that company who made BASIC for CP/M. Are they still around? Haven't seen anything from them in years".

      I thus think that changing the name of the BSDs would have no effect, because the nature of the culture surrounding them means that even if we could go back to those bubble years with a snappy new name, they would still be a pre-Internet(!) technology that lacks a young Linux Torvalds to act as a poster-child for the way that a combination of youth and "The Internet!" were going to build a world where huge wads of money fell from the skies without the need for dull, pre-Internet things like viable business plans. And while Linus never claimed that Linux would make any money at all for anyone (including himself), headlines such as "Creator of Linux says "It's kind of OK now, and will probably get better"" would inevitably accompanied by stories where interviewed CEOs of IT companies told us about all the money they were investing in it, and how the huge losses it was making now would become equally huge profits...

      --
      I'm not going to change your sheets again, Mr. Hastings.
    74. Re:Sad by IntergalacticWalrus · · Score: 1

      Gentoo on OS X (actually "Portage on OS X" is a more appropriate name, because it's not a full Gentoo system, just the package manager) is pretty much dead, sadly. I think there are still a few devs working on it, but at this point it's still not quite usable. A shame, really.

      OTOH the Gentoo on FreeBSD effort appears to be making significant progress. Doesn't seem as exciting though, at least for me.

      There was also talk of a Gentoo on Cygwin, which would've been similar the OS X project but for Windows, but I don't think it ever got past early planning stages.

    75. Re:Sad by Anonymous Coward · · Score: 0
      You speak of the 'viral' aspect of the GPL - do you have a better way of allowing people to use code, whilst preventing anyone from taking away freedoms?
      Yes. The BSD, MIT, Apache and essentially all the other free licenses. They all keep what was free free. What they don't do is expand the amount of free software. If I make changes to BSD, etc. licensed code, the original code is still out there and free. I didn't somehow make it non-free. What you don't free is my changes But even the GPL doesn't give you access to my changes. I can make all kinds of changes to GPL code and not be forced to make one line of it available to anybody -- as long as I don't distribute the program. Heck, even if the software is distributed, I can still charge for the program, I can still not include the changes, I just have to include an offer for the code -- TO THE PEOPLE THAT BOUGHT MY VERSION -- I don't have to give diddly poop to any Joe Schmoe that wants the code. Then I can still charge $200 per copy of the code (Blank DVD costs, overnight shipping costs and my typical rate of $120/hour to burn, package and ship the DVD) -- it doesn't even need to be in a format that makes it easy for the upstream folks to incorporate my changes into their code base. The only things the GPL gets you here, is that I'd have to provide the files and that I can't place any restrictions on what you do with the code after you get it.
    76. Re:Sad by Anonymous Coward · · Score: 0
      I believe they shouldn't be taken away from people. The GNU GPL achieves that.
      So do the other free licenses. What aspect of the BSD, MIT, Apache, AFSL, etc. Licenses allow anybody to make code that was free non-free? Under these licenses, how can anybody say, "OK, the old 1.1 version is no longer free, you need to stop using it."? You can't.

      How does the GPL force anybody to share their changes? It doesn't; unless the code is distributed.
      How does the GPL prevent anybody from charging for their new version? It doesn't.
      How does the GPL prevent anybody from charging to see the source code? It doesn't.
      How does the GPL prevent anybody from refusing to provide the source code to anybody that hasn't purchased the modified version? It doesn't.

      What the GPL does that the other free licenses don't do is:

      1. Force people to give-up their IP and increase the amount for GPL'ed code.
      2. Allow people that legally obtained (NOTE: The program may not have been free $-wise) modified binaries do what they want with the binaries (even resell it).
      3. Allow people that legally obtained modified binaries request the source code (NOTE: The source may not have been free $-wise) and do what they want with the source.
      What the GPL doesn't do:
      1. Keep existing source any more free than any other free license.
      2. Keep software free $-wise.
      3. Keep source code free $-wise.
      4. Force any developer to share their changes with the upstream maintainers in any "useful" format.
    77. Re:Sad by Anonymous Coward · · Score: 0

      IBM still sells AIX, NetWare still comprises a significant portion of Novell's revenue, and Apple specifically did not choose as a basis a more mature Linux kernel than retrofitting a decade's worth of work on the BSDs into NeXT's previous Mach work. If the BSD releases were under the GPL the CMU Mach guys would never taken their work to Steve Jobs and NeXT's operating system would have been written from scratch. Apple then would have bought the BeOS or NeXT's operating system, depending on price. It's not like you ever know much about what you babble about here, but way to divine the future from IBM's service business or Apple's use of GCC.

  6. Sorry, but... by megaditto · · Score: 5, Interesting

    Too bad their dreams did not work out, but frankly, they will not be missed.

    Sure, they ported fink and some libs to Darwin, but that's pretty much it. ODP has been dorman for years, since 2002, pretty much.

    Is Apple to blame for their luck of support? I do not think so; since they do have a neat thing going with http://developer.apple.com/opensource/

    --
    Obama likes poor people so much, he wants to make more of them.
    1. Re:Sorry, but... by babbling · · Score: 2, Insightful

      The reason for this project failing is simple. MacOS is an "alternative operating system". If people value Free Software, it does not make sense to go from Windows to another proprietary operating system like MacOS. People who value Free Software either use Windows (because they have to or are pressured into doing so), or they use a Free Software operating system like Linux.

      The only people who use MacOS are those who want an alternative operating system and don't care about whether it is Free Software or not.

    2. Re:Sorry, but... by Anonymous Coward · · Score: 0

      Not entirely true. I use os x and value free software, I like the idea of being able to change the source and being able to download and install cvs versions but am never going to write kernel drivers so that aspect does not concern me as much. I still use linux daily but when on os x i want to be able to use all the software I already know and enjoy using.

      I tend to think of os x as a unix system with a different desktop on top of it. I still use the terminal heavily and use wget, screen, vim and all the other goodies that I am used to using.

    3. Re:Sorry, but... by NadNad · · Score: 2, Informative

      Fink was actually custom written on and for OS X by...well, by the authors of Fink. OpenDarwin is an entirely unrelated project.

    4. Re:Sorry, but... by Anonymous Coward · · Score: 0

      they do have a neat thing going with http://developer.apple.com/opensource/

      Yeah, the "neat thing" is leeching off of open source projects like KHTML. It was not until Apple was humilated to do so that they provided KHTML developers the proper documentation for code changes. This is why the GPL is important, no one can be a leech and pretend to be a friend of open source. If you change the source, you must give back - its human nature and it works!!

    5. Re:Sorry, but... by jcr · · Score: 5, Interesting

      Too bad their dreams did not work out, but frankly, they will not be missed.

      They really missed the point. Darwin was never intended to be yet another open-source UNIX derivative like Linux or the BSDs. Its whole purpose was to make life a bit easier for people writing drivers for Mac OS X, so when they started beating their chests about how Apple was oppressing them, those of us in the Mac community bascially said: "Umm, who the fuck are you anyway, and why aren't you just using Mac OS X or Linux like a normal person would?"

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    6. Re:Sorry, but... by babbling · · Score: 1

      Not entirely true. I use os x and value free software, I like the idea of being able to change the source and being able to download and install cvs versions but am never going to write kernel drivers so that aspect does not concern me as much. I still use linux daily but when on os x i want to be able to use all the software I already know and enjoy using.

      Yeah, okay, you like Free Software. Who doesn't? I think you misunderstood me when I mentioned valuing Free Software, though. Not just the ability to use the source code whenever you want, but also the freedom to share the software with whoever you want without breaking the law, and the freedom to see how any part of the system works.

      You like Free Software, but you do not value it, otherwise you would not be so willing to discard your freedom and use yet another "alternative" proprietary operating system.

    7. Re:Sorry, but... by soft_guy · · Score: 1

      How about those of us who switched to it because it was the only GUI available and have never found a good reason to leave these past 22 years?

      --
      Avoid Missing Ball for High Score
    8. Re:Sorry, but... by landonf · · Score: 1

      You're kidding, right? Did you not even read the article? Here, let me quote for you:
            "OpenDarwin was meant to be a development community and a proving ground for fixes and features for Mac OS X and Darwin, which could be picked up by Apple for inclusion in the canonical sources."

      OpenDarwin was started with Apple's assistance, by Apple engineers, for the above purpose.

      --
      http://plausible.coop
    9. Re:Sorry, but... by babbling · · Score: 1

      In that case you don't particularly value Free Software, do you? If you did, then that would be reason enough to switch away from it.

    10. Re:Sorry, but... by Anonymous Coward · · Score: 0

      megaditto: if brains were shit you'd have no shit.

      moderators: exactly what the F is interesting about this post?

      The Rest of You: I presume you've read Rob Braun's piece on how stupid Slashdotters and especially Slashdot mods are?

    11. Re:Sorry, but... by Anonymous Coward · · Score: 0

      Drive-by moderators, hehe.

      He got +5 cause of Rash Limbo trolling

    12. Re:Sorry, but... by Richard_at_work · · Score: 1

      I value free software, but I dont value it enough to switch because it doesnt do the job for me as well as nonfree software in the general realm of complete OS with GUI. Thats why I use OSX. Free software is not the holy grail, the fix of fixes, the end of the universe - its a means to an end.

    13. Re:Sorry, but... by jcr · · Score: 1

      Yes, I read TFA, and the first sentence proves my point: OpenDarwin was originally created with the goal of providing a development environment for building and developing Mac OS X sources as well as developing a standalone Darwin OS derivative.

      That last part shows that they didn't get it.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    14. Re:Sorry, but... by Anonymous Coward · · Score: 0

      Are you fucking stupid? John C. Randolph was an engineer at Apple, you fool! Not only that, he also worked at NeXT! For fuck sakes, he's not a man you should be arguing with about over this topic. Unlike you, he actually was directly involved, and again unlike you, he actually has some idea about what did happen.

    15. Re:Sorry, but... by Daniel+Dvorkin · · Score: 1

      You like Free Software, but you do not value it, otherwise you would not be so willing to discard your freedom and use yet another "alternative" proprietary operating system.

      In the real world, people can value many different things at once, and they have to make decisions based on the relative values of all these different things (which can change over time, sometimes very quickly.) You seem to be unwilling to admit that someone can value something without exalting it over all else.

      --
      The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    16. Re:Sorry, but... by John+Nowak · · Score: 1

      Mildly off topic, but have you tried Gnome (2.14) lately? It's more Mac-like than OS X in many ways I think. It'll bring back fond OS 9 memories. I use OS X at the moment... waiting to see if WWDC will give me a reason to stick with the platform.

    17. Re:Sorry, but... by babbling · · Score: 1

      No, I'm suggesting that there are practicality reasons for using Windows, but MacOS and Free operating systems like Ubuntu are very similar in terms of what they can do and how easy they are to use, so there is no reason why someone who values Free Software would use MacOS.

    18. Re:Sorry, but... by Daniel+Dvorkin · · Score: 1

      MacOS and Free operating systems like Ubuntu are very similar in terms of what they can do and how easy they are to use

      [shrug] In your experience, maybe. In mine, and in many other OS X users', not so much. OS X still has a slickness about it that no desktop Linux I've ever seen has been able to match (largely because they're all chasing the Windows chimera.) A lot of techies sneer at valuing aesthetic considerations at the same level as technical or ideological ones, but personally, spending as much time at my computer as I do, I find that enjoying the experience means a hell of a lot.

      --
      The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    19. Re:Sorry, but... by TomorrowPlusX · · Score: 1
      The only people who use MacOS are those who want an alternative operating system and don't care about whether it is Free Software or not.

      Uh... plenty of people use Mac OS X not because they want an alternative system but rather because they prefer it. It's not like Mac users are (all) a bunch of elitist assholes who're using it just to be different. Some are, sure, but not everybody.

      Frankly, lots of people don't give a fig if the OS is open, or "alternative" ( what does that mean? To me, Windows is an "alternative" ). They want what works for them.

      --

      lorem ipsum, dolor sit amet
    20. Re:Sorry, but... by Richard_at_work · · Score: 1

      I routinely try all the various WMs around on my 'play' box, and I routinely find myself disappointed. Dont get me wrong, they all work fine but its the little things that disappoint me - the redraw problems, stuff not laid out in sensible manners, windows not large enough for contents. Its the little things that take the sense of professionalism away.

    21. Re:Sorry, but... by Anonymous Coward · · Score: 0

      Sorry, but the GP cited sources, whereas JCR may have once worked as a teaboy in Apple's PR department*, but he's proved to be an insufferable jackass since he left repeatedly issuing demonstrably moronic statements about what Apple's doing, without so much as an ounce of substantiation.

      When Apple announced Darwin, it most certainly wasn't as some resource for creating device drivers. It was announced as a major open source operating system that would be one component of the next version of Mac OS. They had ESR involved in the publicity. They have, ever since, put that stupid "Come in, it's open!" badge on their Mac OS X website publicity.

      JCR is spouting bullshit as usual, as is his wont.

      * Yes, I know that wasn't his job. But unless you're telling me JCR was Steve Job's assistant throughout the entire iCEO/CEO period, there's no way he could possibly have been in on the strategic decisions made by EVERY FUCKING DEPARTMENT inside Apple. Maybe one department did think "Hey, releasing the source code to Darwin would help developers write device drivers", but that thinking would have been reserved for one or two departments, not the entire strategic direction of Apple. And the fact is, if that was their logic, then it makes zero sense. Only certain types of device driver are actually included in the open source part of Darwin (notably absent are the display drivers - binary only, and CD/DVD burners; there's probably a lot more), and releasing source for the kernel (as opposed to the drivers) encourages developers to ignore published APIs, of the type that are critical to driver development. There is absolutely not a chance in hell Apple used this as their logic for releasing Darwin.

    22. Re:Sorry, but... by shawnce · · Score: 2, Informative

      Darwin was made available by Apple... basically to address licensing requirements of source that they used and to provide Apple source to external parties to help in their development work on KEXT, etc. It was never meant, from Apple's point of view, to be a alternate "free" operating system distribution but they did allow for that possibility (via licensing and refinements of that license) but they never really had strong plans to spend a lot of resources on making such a thing happen.

      OpenDarwin was started as a result of dreams of a handful of Apple employees and external individuals to see if they could build a more vibrant community, one that would lead to a distribution while also acting as a source of fixes and improvements from external parties. Apple helped to get it going, likely to see what would happen but they never had strong plans to change how they did things internally to make life easier for OpenDarwin folks (for one Apple has a strong desire to keep future products/capabilities secret so as a result they had to be selective on when and how they release source outside the company).

      The reality is they had what they needed to build a community and a small one started but never really matured into anything. Lots of folks took with little give to the community effort. It would have been interesting to see it grow into something more (like WebKit appears to be doing now) but the main issue was trying to take something beyond what Apple really had envisioned... hard to do that without a stronger community.

    23. Re:Sorry, but... by soft_guy · · Score: 1

      In that case you don't particularly value Free Software, do you?

      As some kind of "principle"? Hell no. However:

      I use the Gimp because it is a nice piece of software that does the job.

      I have written software that I have released under an OpenSource license because I was tired of writing the same piece of software for multiple clients.

      If I can use some cool free thing in my programs, I often do. (I am writing something that uses PortAudio right now.)

      --
      Avoid Missing Ball for High Score
    24. Re:Sorry, but... by King+tweak · · Score: 1

      Darwin I'm running Mac OSX

    25. Re:Sorry, but... by Anonymous Coward · · Score: 0

      You seem to have trouble understanding that it is impossible to value contradictory things. You consequently have trouble communicating with people above your level of ignorance.

    26. Re:Sorry, but... by landonf · · Score: 1

      Didn't get what? That Apple wasn't interested in community contributions/support for Darwin?
      No, I think we did "get it", and thus this announcement. What bothers me about your post is the disdain you have for the effort -- the notion that even trying deserves derision.

      Apple advertised -- and still advertises -- Darwin as the open source core of Mac OS X. OpenDarwin was based on the notion of building a community around what *could* be contributed to -- Darwin. Perhaps this was ultimately folly, but your ridicule is unwarranted. An independently buildable standalone Darwin would have allowed us to work directly with and contribute changes back to Darwin, independent of Mac OS X and its secrecy, release schedules, etc.

      Instead, Apple moved to make Darwin source "not live", now doing a source drop with every release. While their perogative, it makes it incredibly difficult to contribute any fixes or changes back to Mac OS X -- by the time one does, the code you're working with is far out of date, and chances are good your changes won't be accepted.

      As someone who started with Mac OS X by tracking the live Darwin sources, submitting changes, and getting code accepted, I have been disappointed to see this model for community involvement disappear. You may not care at all, but I see absolutely no reason to mock those that do.

      --
      http://plausible.coop
    27. Re:Sorry, but... by John+Nowak · · Score: 1

      > the redraw problems,

      This is from using it on a computer without working hardware graphics acceleration. OS X would be the same on such a computer. If you look at some of the videos that make use of hardware acceleration, you'll see it isn't an issue.

      > stuff not laid out in sensible manners,

      Gnome 2.14 is all quite sensible to me. Some of the apps may not be there yet, but it is the same on OS X.

      > windows not large enough for contents.

      I've only had this issue on Kubuntu, which is a Kubuntu-specific problem and not to do with KDE if I recall correctly. Still, it is insane that they released it like that...

    28. Re:Sorry, but... by jcr · · Score: 1

      Didn't get what? That Apple wasn't interested in community contributions/support for Darwin?

      Reading comprehension really isn't your long suit, isn't it? Go back and read that part that I marked with bold text.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    29. Re:Sorry, but... by Anonymous Coward · · Score: 0

      I think the POV depends on wether or not you have been on the inside of Apple and OpenDarwin or on the outside.

      You are definatly in the latter camp.

      Apple made it increasingly difficult for OpenDarwin to survive, at one time there was a full CVS, but as we only got code from Apple at release time, it became impossible to maintain. Apple themselves had a live CVS back in the day, but they quickly put a stop to that. Now we cannot even build full versions of Darwin from scratch, only bits and pieces.

      What is left of OpenDarwin were a number of small open source projects, some of which are really good ( eg. xar, ) but unfortunatly it isn't an operating system you can build yourself any more and thus their is no reason for the project to continue.

  7. Sad but not unexpected by caseih · · Score: 3, Interesting

    Apple never supported the open source version of darwin in any way beyond lip services, some server space, and releasing source packages in mostly unbuildable form. They took from many open source projects but returned precious little to the community. At the end of the day Apple does what immediately benefits Apple. It's sad, but it's likely the threat of hacking OS X to run on white box computers likely is the greatest reason for Apple to not release vital parts of the latest OS X source code. Yet this will still happen. In the meantime, Linux continues to grow and become better all the time. There just was no need for OpenDarwin without Aqua. If all you want is a unix-like OS to run servers, Linux suits the bill just fine.

    1. Re:Sad but not unexpected by dominique_cimafranca · · Score: 4, Funny

      Ah, so there's the problem. There were several missing link libraries.

    2. Re:Sad but not unexpected by Anonymous Coward · · Score: 0

      But things like that don't matter. Apple never supported Linux and that has become the best OS in the world. OSS is superior to closed source because all the bugs are shallow to a thousand eyes.

      I just don't understand how this could happen.

    3. Re:Sad but not unexpected by Anonymous Coward · · Score: 0

      Apple never supported it becuase no one really needed it. Lets face it, Darwin was a solution in search of a mission.

    4. Re:Sad but not unexpected by dr.badass · · Score: 1

      Apple never supported the open source version of darwin in any way...

      OpenDarwin is a fork of Apple's Darwin. Are you saying they should have supported a branch of Darwin other than the one they actually use? If so, when did you stop taking your medication?

      They took from many open source projects but returned precious little to the community.

      Maybe the community should ask for more than that when they license their code if that's what they want.

      --
      Don't become a regular here -- you will become retarded.
    5. Re:Sad but not unexpected by beren12 · · Score: 1
      Apple never supported the open source version of darwin in any way beyond lip services, some server space, and releasing source packages in mostly unbuildable form. They took from many open source projects but returned precious little to the community. At the end of the day Apple does what immediately benefits Apple.

      Well, yes. Any company does what benefits them, and if they don't, they can be sued by the shareholders.

      Apple has done many things to improve OSS. Ever hear of GCC? Apple has more devs working on gcc than anywhere else, last I heard. They have made great improvements to many projects. It's not always given back in the easiest to understand form, but it's given back. We at fink have taken many of apple's patches and cleaned them up for things like xorg, and they made a lot of patches to fix it that would have taken the community forever to do on its own.

    6. Re:Sad but not unexpected by Blakey+Rat · · Score: 2, Insightful

      They took from many open source projects but returned precious little to the community.

      Are they in violation of any software license? No? Then Apple has absolutely no obligation to give anything to anybody. If "the community" wants more than "precious little," they should put that in the license terms, eh?

      That's like getting a plumber bill for $150, paying $150, then having the plumber come and complain that you didn't give him a massage, too.

    7. Re:Sad but not unexpected by IntergalacticWalrus · · Score: 1

      Has the original poster complained that Apple didn't give back much? No. He was just stating facts, and explaining that this is unfortunate. He even said "At the end of the day Apple does what immediately benefits Apple". No need for that idiotic plumber analogy. Don't defend Apple when there's nothing to defend it against. Please shut up, zealot.

    8. Re:Sad but not unexpected by Blakey+Rat · · Score: 1

      The part I'm contesting is that it's "unfortunate." How is it "unfortunate" exactly?

  8. Sometimes I wish I weren't such a sux programmer. by dosius · · Score: 1

    If I were a better programmer, I could make the project I've wanted: an update of GNUstep to be more library-compatible with OSX, and an OS using it with Darwin.

    -uso.

    --
    What you hear in the ear, preach from the rooftop Matthew 10.27b
  9. Re:GNAA by Anonymous Coward · · Score: 0

    you loose.

  10. .... Apple is NOT open-source, by any means. by feranick · · Score: 2, Insightful

    Well, I don't really get how much "open source" there is in Apple's effort. To me it looks more like "open-source compatible". In other words, with tools provided you can compile your open-source software (read: linux code) for Darwin. However I don't really see a full open-source effort. To me open-source means that you have to release the source one way or another, and Apple doesn't release any piece of source code. It's not enough to be based on FreeBSD to acquire the status of "Open-Source".

    Sorry, this is another of those marketing schemes of Apple's. In fact it's one of the main reason I am staying away from it.

    P.S. What is Microsoft did the same?

    1. Re:.... Apple is NOT open-source, by any means. by megaditto · · Score: 3, Informative

      All of Darwin's source is 'open' in the sense that you are free to view, modify, and recompile it at will (unless you refuse to their fairly liberal license). All of it will work in OS X. With 10.3, you may rebuild Darwin from source, then 'drag&drop' the propriatory junk on top, and it will work! It is no longer possible to do that with 10.4_x86 since the TPM-related stuff is not released.

      An example of open-source compatible OS would be OpenVMS in my mind, which is, of course, closed-source, but very programmer-friendly. Darwin is definitely more open than that.

      Sure, there must be ulterior motives for the 'openness', but right now it's pretty convenient, and sure as hell beats programming for Windows. I mean, how much of Windows' kernel source would someone like me get to see without shelling out some serious cash?

      --
      Obama likes poor people so much, he wants to make more of them.
    2. Re:.... Apple is NOT open-source, by any means. by feranick · · Score: 1

      Thanks for the clarification. However, being able to recompile Darwin, although possible (up to now at least) is a minimal part in the open-source effort. Would you still consider linux really open-source if the kernel were to be the only open source part of the OS, the rest being proprietary? What is the point of recompile a kernel, which anyway is locked into an hardware platform and has a proprietary desktop environment on top? Really I still think it's just a marketing scheme. Apple knows that using "open-source" brand is cool. But they are acting to keep their code as close as they can. Opening it would mean open the road for white box running OSX.

    3. Re:.... Apple is NOT open-source, by any means. by linuxpyro · · Score: 2, Insightful

      If I'm not mistaken, I believe that the proprietary stuff in OS X consists of the GUI mainly, and I suppose other things like CoreAudio. (If someone knows this a little more in depth, I'd be interested.) The stuff like Darwin is thus under their open source license. In other words, what makes it OS X and not just Open Darwin is proprietary.

      Frankly, if Apple had decided to bas OS X on the Linux kernel, I'd probably be a Mac user now. At the moment, many of their products don't appeal to me enough for me to consider buying a Mac; this is just a personal preference. However, it would be cool to have true compatibility with other Linux distros, while still being able to run things like Photoshop seemlessly.

      I suppose vendors like Adobe would not like this, as it would in theory make things easier for people wanting to run say Photoshop on other distros, but software like that would rely on Aqua anyway, so I don't know if it would be a big deal.

      Oh well, just a thought.

      --
      Saying "I'll probably get modded down for this" in a post is the best way to get it modded up.
    4. Re:.... Apple is NOT open-source, by any means. by EelcoV · · Score: 2, Informative
      Well, I don't really get how much "open source" there is in Apple's effort.

      Apart from the kernel itself, you mean?

      • samba, for filesharing with Windows computers. Quite essential.
      • printing, with cups.
      • apache and php, for web serving.
      • postfix, your email MTA.
      • lots and lots of Gnu software (just about all lower-level software development tools are Gnu).
      On the Server version of OS X there will be many more.

      I think that if you removed all open source software from OS X and rebooted, your machine would not make it to the login display.

    5. Re:.... Apple is NOT open-source, by any means. by snuf23 · · Score: 1

      Uh, these are open source components that Apple incorporates into there closed OS. So I'm not sure there is any real benefit to open source that Apple is granting by using this. Does the BSD code in some of Microsoft Windows networking components help open source?
      Apple's current OS is relies on it's open source code base, but the world of open source software would be pretty much exactly the same without Apple.

      --
      Sometimes my arms bend back.
    6. Re:.... Apple is NOT open-source, by any means. by Anonymous Coward · · Score: 0

      The bootloader is Open Source, so that machine would fail to boot: a broken apple icon :)

    7. Re:.... Apple is NOT open-source, by any means. by I'm+Don+Giovanni · · Score: 3, Informative

      You're correct that that which makes OSX OSX is closed source, but it's not just the GUI. The whole Cocoa and Carbon API is closed. It's like Microsoft opensourcing the NT kernel and keeping Win32, DirectX, COM, .NET*, etc closed. It's fairly meaningless. OSX is "proprietary", period.

      * The CLR part of .NET is open as the Rotor code; I refer to the closed parts of .NET (WinForms, WinFX, etc).

      --
      -- "I never gave these stories much credence." - HAL 9000
    8. Re:.... Apple is NOT open-source, by any means. by kosmosik · · Score: 1

      > Apple doesn't release any piece of source code.

      Just what the fuck you are talking about? They do. mDNSresponder for example.

    9. Re:.... Apple is NOT open-source, by any means. by 99BottlesOfBeerInMyF · · Score: 1

      It's like Microsoft opensourcing the NT kernel and keeping Win32, DirectX, COM, .NET*, etc closed. It's fairly meaningless.

      Maybe having a large part of the OS open sourced is useless to you, but certainly not to everyone. I know a number of people who would be using OpenBSD if they did not have the ability to make modifications to the open parts of OS X. The mix of open and closed source software in OS X makes it much less useful for some tasks (like re-implementing the OS) but still provides useful functionality to people who need to know exactly how something works in the OS X implementation or is looking to make certain kinds of modifications. It is also useful when tracking down bugs.

    10. Re:.... Apple is NOT open-source, by any means. by HiThere · · Score: 1

      Make that *some* Apple fans...though I suspect that the number that remain Apple fans is decreasing as Linux improves.

      Yes, it's nice that Apple "just works". But the same is nearly true of Ubuntu and, if reputation is accurate, of Xandros and Linspire. Possibly also PCLinux. There's just a few little tweaks here and there still neededd. Now due to licensing, Ubuntu may never get there with a free edition (note that the others that I mentioned were commercial) because of things like licensed codecs...but it can get close. And, if rumor is correct, there's talk of a commercial edition that WILL contain the proprietary stuff.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    11. Re:.... Apple is NOT open-source, by any means. by Anonymous Coward · · Score: 0

      Actually, Rotor is a complete second implementation of .NET; it's not the "real" CLR.

    12. Re:.... Apple is NOT open-source, by any means. by Elektroschock · · Score: 1

      You know, my post was modded down, for Apple fans it is perhaps a flamebait. But Apple is a Hardware plattform with an operating system. Very good and high quality. Apple has not to solve the shit Microsoft faces. Its operating system does not have to run everywhere and interoperate with Crap Associated hardware solutions provider and its driver programming hell department. We expect Windows to work with any hardware and Linux to get to the same point. Difference: Linux should support it without external driver components, out of the box. Apple has a limited plattform. They even had some safeguards that you do not tinker and use other hardware. They don't want you to run your copy of Tiger on Intel PCs. This is proprietary+. The IBM PC was the "open" plattform in the 80th. The PC survived, good for Intel and Microsoft. Microsoft does not force you to use a Microsoft mouse. Microsoft does not sell real computers. Linux could do the same. Imagine a distribution, lets call it IBMUX which works on IBM PCs only and works on any IBM PC. Regressions are made, hardware from IBM PCs will be supported. When you take a Dell, you will get into trouble. It is no big deal to optimze your operating system for a limited set of hardware. Then you can fully concentrate on user experience. IBM PCs are probably no big deal. Hardware support is always a matter of time.

    13. Re:.... Apple is NOT open-source, by any means. by HiThere · · Score: 1

      Well, NO, I don't expect MSWind to work on "any platform". I know better. I expect, instead, that the platforms it doesn't work on will stop being sold. For now.

      I think MUCH more highly of Apple than of MS, and it does do a good job of hardware integration. I Have my wife on a Mac, because Linux doesn't have the applications that she needs. (This might actually be "because I can't tell that Linux has the applications that she needs". I'm talking about musical score editors and animation packages. And it might well be that my system doesn't support the things which are working on other systems [I'm rather certain my midi card is broken]).

      But I've been considering how difficult Linux is to use, and I've decided that it's actually easier than the Mac. (And, of course, easier than MSWind.) True there is some maintenance that should be done occasionally...but that's gotten quite easy, and, additionally, I'm the person that needs to do it even on her Mac, so that's no argument.

      The problem it solely applications. And not many of them.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    14. Re:.... Apple is NOT open-source, by any means. by Elektroschock · · Score: 1

      Hmm, Rosegarden? Lmms?

    15. Re:.... Apple is NOT open-source, by any means. by Elektroschock · · Score: 1

      Windows works on all new Intel PCs which are shipped with windows. Of course drivers are needed but they are shipped by your hardware vendor, no problem. And if hardware does not work you will regard it as a problem of your hardware vendor, not of Microsoft.

      Microsoft has the support hell. Users expect to run almost everything. Windows has to provide interfaces for third party drivers, most of them as always poorly written and a usability hell.

    16. Re:.... Apple is NOT open-source, by any means. by HiThere · · Score: 1

      Rosegarden aparently doesn't work on my computer. Possibly, as I mentioned, a bad midi card.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  11. Re:Sometimes I wish I weren't such a sux programme by QuantumG · · Score: 1

    I sometimes wonder why this isn't an ongoing project like Wine. I think it's two things: 1) Few developers are interested in both Macs and asm. 2) It's such a narrow target. I mean, what Mac apps would you want to run on Linux that you can't find a windows version to run on Wine or some windows emulator.

    --
    How we know is more important than what we know.
  12. DarwinPorts by Distinguished+Hero · · Score: 2, Interesting

    I wonder what will happen to DarwinPorts.

    --
    Uttering logically derived and empirically supported truths to the disciples of the orthodox establishment.
    1. Re:DarwinPorts by Anonymous Coward · · Score: 0
    2. Re:DarwinPorts by Anonymous Coward · · Score: 0

      Darwinports will remain alive. There's a message to this effect on the mailing list.

  13. Apple has been pissing me off by nukem996 · · Score: 1, Flamebait

    I work with a lot of users and all they talk about is how great it is but when I mention Linux they respond with "But OS X is Linux" I try to tell them that OS X actually uses the BSD kernel with some parts of open source projects(mostly KDE) but they say "same thing" it really pisses me off(especially as a Linux user). I cannt imagine what the BSD developers/users feel. Anyway I always though the Apple commitment to open source was half-ass/shady. blah I just hope more Apple users smarten up and switch to Linux or a real BSD system.

    1. Re:Apple has been pissing me off by Anonymous Coward · · Score: 1, Informative

      I'd imagine the BSD developers get annoyed that you don't know the difference between a kernel and userland.

      OSX uses Mach as its kernel (sort of), BSD as the source of much of its userland and some libraries, and a ton of proprietary code.

    2. Re:Apple has been pissing me off by nukem996 · · Score: 1

      I guess I was over simplifying things. I was just trying to state that most users think the hole system is Linux with an Apple GUI. When its not even close to that and the open source parts are from the BSD kernel, not the Linux kernel, as well as various open source projects.

    3. Re:Apple has been pissing me off by exp(pi*sqrt(163)) · · Score: 5, Insightful
      blah I just hope more Apple users smarten up and switch to Linux or a real BSD system.
      And I hope more users get over the whole macho thing and give up using an OS where every trivial little task becomes some monumental quest where you have to prove yourself worthy by constructing scripts, .rc files and kernel configurations, and switch from BSD and Linux to MacOSX. But that's just my opinion.
      --
      Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
    4. Re:Apple has been pissing me off by nukem996 · · Score: 1

      I installed Fedora Core 5 on my grandparents computer added a user from them and me then turned on automatic updates and havnt had to do a thing since. I dont know when the last time you used Linux but distros like Redhat/Fedora, SUSE, and Mandrake make everything brainless.

    5. Re:Apple has been pissing me off by nukem996 · · Score: 0, Flamebait

      You forgot the hardware is exspensive as hell and the warrenties suck.

    6. Re:Apple has been pissing me off by Anonymous Coward · · Score: 0

      I never made an .rc file in linux. Havn't bothered with kernel configs, the stock compiled ones work fine.

      I make scripts in osx too.

    7. Re:Apple has been pissing me off by bsartist · · Score: 1
      I work with a lot of [non-geek] users and all they talk about is how great it is but when I mention Linux they respond with "But OS X is Linux" I try to tell them that OS X actually uses [geeky technobabble] but they say "same thing"
      I've added a few things to the above. My additions are in brackets and bolded - they might help explain the disconnect you're seeing. To the end users you're talking to, Unix means "it doesn't lock up twice a day like %*$#@ MacOS 9 did". The rest is just boring technobabble they don't understand and don't want to.
      --
      Lost: Sig, white with black letters. No collar. Reward if found!
    8. Re:Apple has been pissing me off by nukem996 · · Score: 1

      Well whats said is they may not be geeky but there computer teachers and one was going for a PHD in comp sci, so its not like they know nothing about computers. But still I get the same response from them as I do with non-geeks.

    9. Re:Apple has been pissing me off by nick.ian.k · · Score: 1

      I'm eager to see your camp drop the sehr-macho dickwaving and try a modern distro on hardware that's known to be compatible. You'll be astonished at how little hoop-jumping is necessary on Linux these days. Things are known to work for other people and work well, your own experiences be damned.

      The evangelism's been going on since '84. Some people don't *need* to be saved. Deal with it.

    10. Re:Apple has been pissing me off by Al+Dimond · · Score: 1

      The point of your parent comment is that OS X uses nothing from the Linux or BSD *kernels*. It uses some BSD userspace code.

      The kernel is the lowest-level part of an operating system, which provides abstractions between programs that users see and the hardware. Some of the most important of these abstractions are virtualization of limited physical resources such as CPU and memory, so that programs don't have to worry about sharing them. Userspace programs that are generally considered part of the OS include standard libraries, command shells and basic utilities.

    11. Re:Apple has been pissing me off by nukem996 · · Score: 1

      Its still using user space BSD code and not the Linux kernel. People think its using the Linux kernel.

    12. Re:Apple has been pissing me off by geminidomino · · Score: 1

      but they say "same thing" it really pisses me off

      Don't let it get to you. These are the same sort of people who call a PC the "modem", the 3.5" floppy the "hard drive" and the monitor the "computer."

      They don't care enough to know why they're wrong, so you shouldn't care enough to be annoyed by them.

    13. Re:Apple has been pissing me off by LorfOfHugs · · Score: 1

      Apple marketing has irritated me forever. From back in the days with the snail for a Pentium - at a time when their hardware was never actually faster than Intel's (except for that bogus Photoshop benchmark that everyone cited). Now the the current dork vs. the hip youth that speaks Japanese. Apple has never impressed me with any actual accomplishment - it survives via marketing that makes it's consumers feel superior to the rest of the world (this means you Slashdot). They're purely a branding company that lives on this site because they're not Microsoft. Way to go Apple!

    14. Re:Apple has been pissing me off by Anonymous Coward · · Score: 0

      You're confused: we're using ELF, you OS X guys are the ones using mach-o. :-p

    15. Re:Apple has been pissing me off by geminidomino · · Score: 1

      I'm eager to see your camp drop the sehr-macho dickwaving

      You know, when I see "Apple" I think a lot of things, most of them less than complementary. One word that never comes to my mind, though, is "macho."

      Quite the opposite. I'm always half-expecting a flying finger-snap.

    16. Re:Apple has been pissing me off by nukem996 · · Score: 1

      Its not something I obsesse on just something that gets annoying when im talking to them.

    17. Re:Apple has been pissing me off by Anonymous Coward · · Score: 0

      Maybe you should hang out with English teachers instead of "computer teachers", although from your flaming posts, it appears you need the help of both.

    18. Re:Apple has been pissing me off by soft_guy · · Score: 1

      By "smarten up", I think you mean, "become insane maniacs who want to purposely make our lives harder for no reason".

      --
      Avoid Missing Ball for High Score
    19. Re:Apple has been pissing me off by Magic5Ball · · Score: 1

      As has been suggested, it's all about context. For the vast majority of Linux, OS X and even Windows users, the operating system is just a toolset and perhaps an environment to accomplish a task. And in the perfect world, all of a user's time should be spent using, not necessarily understanding or maintaining the tools.

      When I need an application server, I don't care if the stack is built on Linux or OS X because I do not directly interact with the kernel, device drivers, or how memory ports are handled. For the purposes of the task at hand, my OS X MBP is functionally identical to my RHEL workstation, so treating both containers for FOSS stuff as "Linux" is fine.

      When I need to do visual design, I don't care if the stack is built on Windows or OS X because, again, my purpose is not to directly interact with the GUI widgets or anything close to the hardware. For the purposes of the task at hand, my OS X MBP is functionally identical to my Windows workstation, so ignoring microkernel-something or HAL-whatever aren't problems.

      When all I need is information from the Internet, perhaps to troubleshoot a piece of hardware, anything that runs a browser is equally functional, and nothing outside the browser's environment (window) really makes a difference to the experience, so OS X, RHEL and Windows are all just ways to get to Firefox.

      And surprisingly, the world hasn't exploded because of these technically inaccurate conceptual shortcuts.

      --
      There are 1.1... kinds of people.
    20. Re:Apple has been pissing me off by BrianCarlstrom · · Score: 2, Informative

      As the other reply said, Apple does not take anything from the BSD kernel, they take stuff from the BSD userland as well as the GNU project, amongst others.

      The Mac OS X kernel is based on the Mach "microkernel", which itself used to rely on BSD code to fill in the gaps to make a fully functional Unix-like operating system. The Mach system is a direct decendant of what NeXT ran on its computers and came to Apple through the NeXT acquisition.

    21. Re:Apple has been pissing me off by cheesygrapes · · Score: 2, Insightful

      The reason apple is popular isn't because they have lot's of shiny ads. Okay, maybe that's one reason but microsoft has lots of shiny ads too. The reason apple is popular is because it is EASIER TO USE. Slashdotters often seem to forget that most of the world are not geeks and don't want to have to deal with making things work. With windows you actually have to solve your own problems and do work to get your computer to do what you want it to do. Macs just work, do a lot of your work for you, allow you to be lazy, and allow you to have almost no knowledge of computers. Macs may be slower, they may be uglier, they may be more expensive, but they don't make a non-geek's life a living hell the way a windows box does. Since the majority of the world consists of non-geeks, it is likely that most people would use macs if everything wasn't so currently entrenched in Microsoft's monopoly.

    22. Re:Apple has been pissing me off by djradon · · Score: 1

      Yeah, i used to keep an Apple Ads scrapbook as a kid in the 80's back when a GUI was rare and exciting.

      When I saw that hipster-computer-talks-to-Japanese-camera ad tonight, I thought to myself, "It's not only a lie, it's pretentious and lame." The ad where the PC keeps hanging is at least funny, but it's a big lie too. I would almost go Mac for it's Unix-ness, but the UI is horrible. Fix the friggin finder, and give me keyboard shortcuts for everything. If you need a mouse to use a GUI, it's not an environment I want to spend my time in.

    23. Re:Apple has been pissing me off by Guy+Harris · · Score: 2, Interesting
      As the other reply said, Apple does not take anything from the BSD kernel

      Wrong. Try looking at the bsd subdirectory of the xnu source tree; it's not "just BSD" - it implements processes/threads atop Mach tasks/threads, and has IOKit for drivers - but it's recognizably based on BSD kernel code."

      The Mac OS X kernel is based on the Mach "microkernel", which itself used to rely on BSD code to fill in the gaps to make a fully functional Unix-like operating system.

      It still uses BSD code for that.

    24. Re:Apple has been pissing me off by BrianCarlstrom · · Score: 1

      Ah, I see, just like Mach 3.0 from CMU I guess. But in any case, I was trying to correct the rampant misconception that Mac OS X is running a FreeBSD kernel that I see so many places. The Mac OS X kernel is more Mach than BSD.

    25. Re:Apple has been pissing me off by ickoonite · · Score: 2, Insightful

      You'll be astonished at how little hoop-jumping is necessary on Linux these days.

      That there is still any hoop-jumping is a problem. And that there is now little hoop-jumping should not be cause for astonishment. I know the Linux user mindset - the kind of macho need to hack around in the terminal just to do something trivial like getting wireless working, converting WEP keys to hex with my bare hands - because I have been there myself, but now I just want to get on with my work (and my life) - Linux wastes too much of my time. Now, I should say that Ubuntu is making real progress and demonstrating that there is a recognition that 95% of the computer-using population see a computer likewise - as a tool to get things done - but it's not there yet. And for those of us that don't want to wait (because, again, we actually have stuff to get on with, or, say, want to use software that other people use, like Photoshop, Office, Dreamweaver), Mac OS X is the better choice.

      Don't even get me started on Windows, mind...

      iqu :|

    26. Re:Apple has been pissing me off by Vo0k · · Score: 1

      Primary market of OS X: Graphicians. Photoshop support aside, even assuming GIMP lives up to the expectations, there is no Linux distro that would support a digitizer tablet out of the box without need to manually edit xorg.conf or XF86Config.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    27. Re:Apple has been pissing me off by Vo0k · · Score: 2, Interesting

      Yes, don't do it the hard way - you might learn something.

      I thought so too, for good 5 years when I was supporting Linux without any doubts.
      Then there came several harder weeks, when I just had to get my job done quickly and efficiently. And as different problems started popping up, I would spend 5-6 hours a time seeking a solution, fixing them, getting no actual work done. Sure I was learning a lot of new things, but things at hand were delayed.

      Now typing this from WinXP. Because the Ubuntu I have installed has several usablity problems I just cannot get myself to solve, to dig deep enough in config files and docs, to spend another 2 days or so reconfiguring the system to get it to work like -I- want it, to learn the keyboard shortcuts to all the essentials etc. First, that's 2 days when I'm not doing things I want to do, but ones I'm forced to do. Second, in 3-4 years another desktop manager will come, or the one I'm using will get "updated" so much that I'll drop it, and all I learn will become useless again.

      I've been using AfterStep on Linux for 5 years or so, it was cool, comfortable, very customizable and above all, ultra-fast. After some time, the project "maturing" added lots of hard-to-disable clutter (comfort gone), became rather slow (and my style of usage required it to be ultra-fast!) and stability from acceptable went to poor. About a week of exploring and intense learning of the configsm customizablity and such, becoming an expert of the desktop manager, went straight to hell when I decided enough is enough and simply dropped it. With Afterstep 2.x it died for me. I haven't found a desktop manager I'd like since then, and I tried really lots.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    28. Re:Apple has been pissing me off by Jaxoreth · · Score: 1
      blah I just hope more Apple users smarten up and switch to Linux or a real BSD system.
      And I hope more users get over the whole macho thing

      I'd love to get over Mach-O, which is why I'm switching to Linux. :-D

      and give up using an OS where every trivial little task becomes some monumental quest where you have to prove yourself worthy by constructing scripts, .rc files and kernel configurations, and switch from BSD and Linux to MacOSX. But that's just my opinion.

      Oh, you've got me all wrong. Linux still has rough edges that infuriate me. But Linux's stupidities can be fixed, unlike OS X's (or OS 9's) which can't. Or at least won't.

      Mac OS X is a clear winner in looks and usability. And by looks I don't mean Aqua (which I dislike), I mean subtler things like fonts and anti-aliasing. And my personal favorite, mouse acceleration. The same physical distance covered quickly should move the mouse cursor further on-screen than the same distance covered slowly. Apple got this right from day one, and X11 still hasn't.

      On the other hand, Mac OS X's performance just plain sucks compared to OS 9's. It's roughly an order of magnitude more demanding in memory, processor speed, and disk space. I loved my clamshell iBook until I installed OS X on it. A while ago the Airport software got corrupted, so the system hanged when I tried to power up the card (but it still worked booting OS 9). If this happened to OS 9 or a dpkg-managed system, I could fix it myself, but with OS X I was facing a reinstall. So I backed up the drive, reformatted, and installed dual Debian etch / OS 9. (My primary machine still runs OS X.)

      Thus I begin my switch to Linux. It will probably end when Linux feels more like a Mac to me than OS X does.

      --
      In general, it is safe and legal to kill your children. -- POSIX Programmer's Guide
    29. Re:Apple has been pissing me off by Ed+Avis · · Score: 1
      The same physical distance covered quickly should move the mouse cursor further on-screen than the same distance covered slowly.
      Burn the infidel!
      --
      -- Ed Avis ed@membled.com
    30. Re:Apple has been pissing me off by nukem996 · · Score: 1

      Havnt use one in a long time but I know there is support for wacom. Dont remember what I had to do years ago.

    31. Re:Apple has been pissing me off by John+Nowak · · Score: 1

      I've never encountered any such people.

    32. Re:Apple has been pissing me off by John+Nowak · · Score: 1

      Thus I begin my switch to Linux. It will probably end when Linux feels more like a Mac to me than OS X does.

      Same here. OS X has precious little to do with "the Mac" nowadays. Perhaps in 10.5 they'll fix the fucking finder, fix the dock, polish the applications, unify the UI, etc... Right now, Gnome feels more Mac-like to me. I still occasionally miss my OS 8 days... and that's saying something!

    33. Re:Apple has been pissing me off by Anonymous Coward · · Score: 0
      Yes, don't do it the hard way - you might learn something. Then you would be disqualified from ever owning a Mac. It's also completely un-American and will get you put on a number of watch lists.


      Oh God forbid we recognize that the computer is a tool that we use to get work done. Your ass-backwards retarded attitude cracks me up. I myself use (on a professional basis) use Windows, Linux, *BSD, and Solaris. My users are Mac and Windows folks. The right tool for the job is the key phrase here. Some people are willing to pay money to get a machine that just works, and while it's not my mainstay operating system I have to admit that OS X is as close as it gets.

      And forget about the sense of personal achievement you might get from doing something hard. Buying a product from Apple is a major achievement that instantly makes you better than 97% of the population.


      Oh yes and being an open source zealot instantly makes you a pasty-faced pencil dick who can't get dates, right?

      Pot, meet kettle.

      If you want achievement go volunteer your time to a charity or hit the books for a graduate degree, because in the long run nobody gives a fuck that you figured out how automake works or that you're master of ALSA.
    34. Re:Apple has been pissing me off by Frumious+Wombat · · Score: 1

      Actually, having gone the other way (Linux On The Desktop, (LOTD) 10 years to OSX), I'd be happy if the GUI/App people in the Linux community took a page from OSX, and actually spent some time worrying about polish, internal consistency, and interoperability. I've run (recently) RHEL 4.1, Ubuntu (which is a long way to making this rant irrelevant), SuSE (If you knew SuSE, like I knew SuSE...), and while they're much better than they were when I started, a little polish could still be applied. Surely some of you have graphic-arts oriented friends you could hand a six-pack of something decent to and say, "make these icons look pretty". Surely someone could agree, "you know, a hidden save dialogue activated with a right-mouse click, in addition to the identical one at the top of the window is just silly". An agreement that little buttons with pop-up menus that look like Win95/2K isn't the best interface to copy.

      As for the rest, I write script files on my OSX system, run IBM's Fortran and C compilers to create command-line applications, and end up hand-twiddling my rc files to set things like SHMMAX which is just too small out of the box for real work. The entire difference to me is in the user-land experience. The Mac is just Clean, in a way that's hard to appreciate unless you come to it from too many years of CDE and CDE clones. The beauty is that I can do all that manual work if I want to (find mixed with grep is still often faster for me than Spotlight), but I don't have to. Voluntary complexity is a wonderful thing.

      As one of my colleagues in High-Energy Physics put it, "A Mac is a Unix box that runs iTunes."

      --
      the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
    35. Re:Apple has been pissing me off by Vo0k · · Score: 1

      Yes, it is. Add some 4-5 lines to xorg.conf or XF86Config. Quite easy if you know how. If you don't, it's about 1 hour of googling. There's NO GUI tool to add them.

      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    36. Re:Apple has been pissing me off by nick.ian.k · · Score: 1

      Your example is a piss-poor one. Wireless *isn't* that hard any longer. Pick a wireless card that's got a native, compatible driver and a distro that has said driver available in its package repositories. A card based on the Atheros chipset is a good choice, because the MadWifi packages work *great*. Then install the driver and a configuration frontend of your choice via your distro's GUI package manager. The package manager should get all the command line tools that run behind the frontend, but you don't have to touch them unless you want to; that's what the frontend is for. Then run the configuration frontend, pick your ESSID from a drop-down list and set your WEP key (in ASCII or hex; both are options and there's no conversion required on your behalf). When you need access in a different location, load the front end and change your settings. It's *that* easy. It's done and that's all of five minutes work, at most. Maybe that's a scant pube longer than it takes on your OS of choice, but it must not matter too much: despite your claim of having a life to lead and work to get done, you've still got plenty of time to get on Slashdot and bitch about someone else's OS and go on at length about how yours is oh-so-much better. I use Linux because it meets my needs and I don't have to deal with issues like worrying about subsidizing a company which engages in practices with which I disagree. It's an *ethical thing*. You use the Mac because it meets your needs and you apparently don't have a problem with Apple's doings. That's fine: I strongly disagree with your choice, but your choice is your choice and has little bearing on my life. Use your machine to your heart's content. Once again: get over yourself and stop evangelising. It's old.

    37. Re:Apple has been pissing me off by exp(pi*sqrt(163)) · · Score: 1
      polish, internal consistency, and interoperability
      Polish would be nice, but I can live without it.

      Consistency seems like a far off dream under Linux. Not only do different applications use quite different keys, for example, but they use different "meta" keys too with some applications using ctrl and others using alt. Even after 18 months of being forced to use Linux after work I haven't trained myself to remember which to use because I keep being 'trained' and 'untrained' every time I switch from one application to the next. It's like having an OS that is deliberately designed to make me inefficient. And that's barely touching the surface of this subject.

      And interoperability seems a long way off too. It never ceases to amaze me how complicated it is to cut and paste between apps under Linux. Different applications have completely different ways of implementing it. In some you can indicate what you want to copy by using ctrl- (or alt-)C, say. In others you just mark with the mouse. In the later case you're likely to lose what you have marked when the mouse changes focus (how braindead can you get?). Half of Linux applications use one cut-and-paste buffer and half use another (X has at least two cut-and-paste mechanisms) so you simply can't cut and paste between certain pairs of applications. Sometimes cut-and-paste kinda works, but only sometimes. And sometimes I can cut and paste from A to B only by pasting to an intermediary application first (eg. gedit) and then recopying-and-pasting. Under Linux I can barely copy-and-paste text, under MacOSX I can copy-and-paste full-featured PDF.

      --
      Doesn't it make you feel good to know that our freedoms are protected by politicans, lawyers and journalists.
    38. Re:Apple has been pissing me off by 99BottlesOfBeerInMyF · · Score: 1

      Oh, you've got me all wrong. Linux still has rough edges that infuriate me. But Linux's stupidities can be fixed, unlike OS X's (or OS 9's) which can't. Or at least won't.

      I use Linux every day, but not as my primary workstation. The reason for this is that Linux's stupidities are not fixed, at least not the ones I care about and not as many of them as on OS X.

      I'd much rather my workstation OS were fully open source and more customizable, but the functionality and application availability is just not there. I spend less time maintaining my OS X workstation than I do some of my servers, who just serve a couple simple tasks that have not changed in years. Linux still does not have most applications available as easily portable folders with all the resources laid out neatly inside. Linux still does not have system services that let me use my spell checker and german translator in all my programs. Linux still cannot let me see previews of my photoshop files, or even run photoshop well. Moving all my files, programs, settings, certs, etc. from an old laptop to a new one under Linux is a huge pain compared to OS X. Linux is quite simply not there and I have a theory as to why. Most of the people that care about these features and want/need a workstation that just works out of the box have moved to OS X. They might like to have those features on their server, but not enough to put in the time when they can just use OS X.

      Now OS X is behind in some areas. Some of the cutting edge features you can use on certain Linux distros are the way of the future. The problem is, they are still unpolished enough that they are not worth using much of the time anyway and when they are, they will probably already have been pulled into OS X.

      Basically, the reason I'm using OS X is the same as why you're using Linux. The broken things and missing things in Linux are not being fixed and I want or need them to be.

    39. Re:Apple has been pissing me off by jeremyp · · Score: 1

      The VFS and networking portions of the kernel originally came from BSD.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    40. Re:Apple has been pissing me off by jeremyp · · Score: 1

      Actually they took both the VFS and networking subsystems from BSD.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    41. Re:Apple has been pissing me off by GaryPatterson · · Score: 1

      I've got an idea for you - how about the *programmers* do the hard work to make it easier for their *users*?

      Buying an Apple is no achievement whatsoever, but neither is spending your time getting Linux to do exactly what you want. I don't want to learn more useless crap about computers. I want to use them to do stuff and then get back to my life.

      What am I going to use knowledge about arcane methods of getting a graphics tablet to work for, when I could be enjoying time with my wife instead? I know where my time's infinitely better spent.

      It seems a lot of Linux advocates want users to suffer on their path to Nirvana. Why is that?

      Using the right tool for the job, whatever it happens to be, is the achievement. Linux may be that tool, but then so can a Mac, Windows or a piece of paper.

    42. Re:Apple has been pissing me off by Frumious+Wombat · · Score: 1

      Thank you for the cut-and-paste reminder. While seemingly efficient (highlight then middle click), make one bump while moving the mouse and you have to do it over. I'd forgotten that one.

      It's amazing how quickly you get used to not having to deal with such issues. Now let's hope His Steveness can keep it all on track a few more years.

      --
      the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
    43. Re:Apple has been pissing me off by argent · · Score: 1

      With Afterstep 2.x it died for me. I haven't found a desktop manager I'd like since then, and I tried really lots.

      Windowmaker?

      I jumped from Afterstep to Windowmaker as soon as it jelled anough to be usable, and it's been totally stable for me since.

    44. Re:Apple has been pissing me off by argent · · Score: 1

      I'd imagine the BSD developers get annoyed that you don't know the difference between a kernel and userland.

      No, I get annoyed that you don't know the difference between a BSD Single Server system like OS X and the kind of academic (pseudo)microkernel like Hurd that you think OS X is.

    45. Re:Apple has been pissing me off by argent · · Score: 1

      Apple does not take anything from the BSD kernel [...] The Mac OS X kernel is based on the Mach "microkernel"

      and it uses a trimmed down BSD kernel running as a server to provide almost all OS services beyond memory management, IPC, and scheduling, and many modern BSDs (including FreeBSD, last I checked) use Mach's VM under a monolithic kernel. Even most Carbon apps go through BSD to get to the file system, the few legacy apps that haven't been ported all the way from Mac OS 9 (like Finder... god I wish we had the NeXT file manager back) are the exceptions.

      The division between "what's Mach" and "what's BSD" is awful fuzzy, Mach grew up with BSD and almost all real Mach-based systems depended heavily on BSD right from the start. Claiming that any Mach-based system (even Hurd, one of the few exceptions to the normal approach to building a Mach-based system) "didn't take anything from BSD" is silly.

    46. Re:Apple has been pissing me off by IntergalacticWalrus · · Score: 1

      Haha, I keep hearing that "OS X is based on Linux" nonsense too. It also used to annoy me, but then I realized that people make that mistake because Linux is now THE most significant Unix clone in the world. They don't know about Unix, and use the term "Linux" like we geeks use the term "Unix" to refer to that vague category of operating systems that are either forked from or inspired by the original AT&T Unix.

      Makes you think about how well Linux is going these days, doesn't it?

  14. That was the best slashdot gag in a while... by iendedi · · Score: 1

    I guess I am just dense, but I actually googled around for a bit before realizing that I had been had.

    I tip my hat to you on that one, even though it should have been obvious, ya got me....

    --

    It is your personal duty to fight for what is right on a daily basis. Ignoring injustice is identical to approving
  15. Why blame Apple... by 2nd+Post! · · Score: 1

    When it is the uninformed user who keeps upsetting your equilibrium? All Apple has done is release source, adopted open source products internally, and contribute to other open source projects.

    If Apple users smarten up, it in no way changes what Apple has done and continues to do: use open source when beneficial.

    1. Re:Why blame Apple... by nukem996 · · Score: 1

      Well thats what really pisses me off. Apple uses and abuses open source. This is why GPL is a much better license. (warning: over simplifying) Companies can use the software but any changes they made must be put back. Apple had a chance to be a really good open source company but blew it.

    2. Re:Why blame Apple... by Angostura · · Score: 1

      What pisses me off is people who use the words 'open source' as if it is a synonym for 'free' and then get upset when companies abide by the open source licenses and not the free license that the speaker 'wished' they used.

  16. I wonder by Bartmoss · · Score: 2, Interesting

    I wonder if they're afraid that people would try to use the opendarwin kernel with mac os x for intel to run the whole thing on any machine.

    1. Re:I wonder by mi · · Score: 2, Interesting

      This might be it... Or even better — porting the neccessary bits and pieces to have, say, MS Office for MacOS X (Intel) to run natively on FreeBSD (Intel), may turn out to be simpler, than getting WINE above alpha-quality...

      --
      In Soviet Washington the swamp drains you.
    2. Re:I wonder by Bruce+Perens · · Score: 3, Interesting
      Yep. As soon as Intel Macs came out, they stopped updating the open version of their kernel. Goals? I don't think goals had much to do with it.

      Bruce

    3. Re:I wonder by beren12 · · Score: 1

      You guys really have no clue. Sad.

      --Burn, Karma Burn!

    4. Re:I wonder by flithm · · Score: 1

      You realize of course that you can already run OSX on any SSE3 capable intel machine. Just do a search on your favorite torrent site for "OSX JaS patched" or something like that. Opendarwin or not, OSX intel will always run on any machine. Always has been able to, always will.

    5. Re:I wonder by mi · · Score: 1
      You guys really have no clue. Sad.

      Don't lament — enlighten us and improve your karma...

      --
      In Soviet Washington the swamp drains you.
  17. Sad News by Balial · · Score: 0, Interesting

    As a Darbat (L4/Darwin) developer this is sad, and will be a bit of a set-back. We were hoping to try and become involved with the OpenDarwin community. I'm really sorry to see that this really handy resource will be going.

  18. Re:Sometimes I wish I weren't such a sux programme by Anonymous Coward · · Score: 0

    3) and you can get more binaries to run with wine than sources to recompile with gnustep...

  19. Too bad it wasn't gnu-darwin shut down by NaCh0 · · Score: 0

    Advogato readers will know the true shame is that opendarwin is closing and not gnu-darwin.

  20. Linux (zealots) have been pissing me off by cloricus · · Score: 2, Insightful

    Smarten up...A real unix system...Linux/BSD is the only way...

    As a Linux user of four years who has recently bought their first, personal, mac laptop I wish to call bullshit. I'd like to point out that OSX still plays a very important part in Linux development (less so in BSD) - specifically in regards to new features. Take for example xgl/compiz and xcompmgr which will be in full deployment for when Vista ships to compete with the M$ eye candy...Sure it only came into the lime light when Vistas beta's started shipping and the glory project status moved to them though without earlier projects like luminocity (etc) which was an attempt to add mac grade eye candy to Linux there wouldn't have been the ground work or the test case for this. And even now look at xcompmgr with transett or compiz - they just basically fashion themselves after inbuilt mac effects or 3rd party add ins that have existed for awhile under OSX.

    On top of that mac make computers end users like and OSX Just Works(tm) which for a Linux user is really handy some days when Debian sid decides it wants to blow the heads off all the toys. It also interconnects flawlessly with my other Linux boxes through ssh, samba, nfs, vnc and everything I need (I use Fink for random unix tools I need).

    Lastly OSX shows every day users that there are Real! alternatives to Windows that don't have the stigma of To Hard attached that they can try and enjoy. So really outside the RM ethos of everything should be open (to which, hypocritically in context of the above, I subscribe) there isn't really much reason for a mac user to smarten up and switch, try maybe, to Linux (and a mac user wouldn't touch BSD).

    --
    I ate your fish.
    1. Re:Linux (zealots) have been pissing me off by nukem996 · · Score: 1

      Apple has done some very good things to heaten up competition but im talking technically Apple has done some bad things. For the (it just works) Ive also had the pleasure of fixing Macs that wont install GIMP or connect to our Novell network. I really dont think any OS can be an "It just works" environment. It is great that Apple is showing alternatives to Windows although since parallels came out many of them have been putting that on(ive install it on a couple of machines). Many Apple will help open people up to trying new things but still people want a multibillion dollar company to support it(even if they dont use the support)

    2. Re:Linux (zealots) have been pissing me off by cloricus · · Score: 1

      Agreed. Apple is no angel. Personally I think Jobs is a prat.

      Though on the other topic you raised - I don't see dual OS use lasting very long, the hype has been huge, the level of annoyance in the process has been only slightly removed, and the case for every day use hasn't been made. Virtualisation will probably only ever be used on servers that are doing many tasks and could really take advantage of sandboxing. When it all dies down we will be left with Vista which is a poorly implemented version of the OS X gui on the NT kernel, Linux which will have left Vista in the dirt (mmm no DRM, mac eye candy, legacy support for everything Vista breaks etc) but have no where to really go itself, and OS X which (while still having every day hassles) will still be pushing a head with new features and ideas having already surpassed Vista in feature set and usability (hell 95 beats Vista in usability - the fucking 'You are a newb and you are about to change a minor system setting, press okay to continue'x5 dialogues are enough to send any user mad).

      So really I do believe Linux needs mac and its users at the end of the day, how ever evil and closed apple are, so it has some thing to catch up to and one up else it will just be sitting twiddling its thumbs making sure it can install GIMP without a problem until the next Windows version and even god doesn't know when that will be.

      --
      I ate your fish.
    3. Re:Linux (zealots) have been pissing me off by Anonymous Coward · · Score: 0

      OS X development has indeed shown us some nice stuff, but zealotry is showing through in your reply to the zealot. I see "just works" in there (never heard that from an Ubuntu user, eh?), I see the "why would a Mac user use Linux/BSD" in there (when we've seen a few prominent Mac users switch in the last few months), and of course the "everybody copies OS X" stuff.

      Just because you're ticked off at some troll doesn't mean you have to bring out the aged, rusty, Mac user artillery. That stuff's old, man.

    4. Re:Linux (zealots) have been pissing me off by cloricus · · Score: 1

      Hello AC... So you are a zealot replying to a zealot who is in turn replying to a zealot? Maybe there are some definition issues here?

      Either way to make it public knowledge in this thread I am a GNU/Linux (Debian) fanboy, and rather vocal about it, above all else who has a mac and avoids Windows every where except for my job. Draw what conclusions you wish.

      --
      I ate your fish.
    5. Re:Linux (zealots) have been pissing me off by Anonymous Coward · · Score: 0

      Look, you used "just works" in your post, and it was about a Mac. I'm just sayin'.

      Nobody at Slashdot should fall for "just works" anymore. Look, I can turn on my laptop and open Photoshop. It just worked! I can plug in a printer, and it just works! I can plug in my camera...and it JUST WORKS!!!!

      Seriously, watching that myth get shattered into pieces by the Monday morning support call from a sobbing Mac fan must be one of the most satisfying experiences known to man. And all because this freaking "JUST WORKS" crap won't die. Normally I would just shrug and say, "all computers suck," but now Macs have put this added touch of irony in there.

      Now, of course, Ubuntu users have latched on and suddenly Linux "just works." GOTO 10, I guess.

    6. Re:Linux (zealots) have been pissing me off by cloricus · · Score: 1

      You have to remember in userland (not geekland) mac and linux do Just Work(tm) for every day users. The term outside of its Microsoft tomfoolery really should reference an environment where the computer and software running on it perform a verity of every day tasks with little to no hassle or complication. When I use the term and add (tm) a long with capitalising it I am adding a bit of common sarcasm to the term though I am still implying a case where it will work in almost all cases. This just works state is all but obtainable for a geek...We break things, it's what we do.

      So seriously, grab a nice warm cup of java, sit down on a comfy couch, and join the club of people who are sick of FUD/spin doctors and just want a normal world with terms never make it into the realms of marketing departments.

      --
      I ate your fish.
    7. Re:Linux (zealots) have been pissing me off by Anonymous Coward · · Score: 0

      Unfortunately, OSX appears to be missing a spelling and grammar checker.

    8. Re:Linux (zealots) have been pissing me off by 99BottlesOfBeerInMyF · · Score: 1

      For the (it just works) Ive also had the pleasure of fixing Macs that wont install GIMP or connect to our Novell network.

      Macs just work, if you are doing things the recommended way. For example, if GIMP used the native UI and installed as a .app folder like most programs, there would be no problem. Since it installs in basically a Linux compatibility environment using a window server that is not even on the system by default, well that is a different story, just like getting Photoshop for Windows to install on a Linux box by installing WINE. I'm not sure what your Novell issue is, but I think OS X's networking in general needs some work, although their zeroconf is head and shoulders above everyone else's.

      Apple has done some very good things to heaten up competition but im talking technically Apple has done some bad things.

      I don't know about this. Apple has introduced features which were then copied by Windows and Linux, but more and more often Linux does not provide those features. I think this is because so many Linux desktop users and developers moved to OS X and no longer have an itch to scratch. I don't see Linux catching up anytime soon.

  21. Re:Sometimes I wish I weren't such a sux programme by jcr · · Score: 2, Interesting

    [Re: GNUStep]

    I sometimes wonder why this isn't an ongoing project like Wine.

    Well, basically, it's like this: the people who know enough to work on it are, for the most part just using Mac OS X, and most of the Linux crowd can't really tell the difference between GNUStep and Gnome (ie, they actually believe Gnome is good enough).

    The upshot is that the contributors to GNUStep are a very small number indeed, and it's amazing how far they've gotten with so few people working on it.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  22. BSD users feel the same as always. by Anonymous Coward · · Score: 1, Insightful

    We feel "who cares what other people are running?". I feel the same about OSX users as I do about windows users, I don't care at all. Linux users on the other hand do bug us, since they do such stupid shit to their servers, and then when we take over when they get fired, it takes forever to clean up the mess.

    1. Re:BSD users feel the same as always. by Anonymous Coward · · Score: 0

      and everyone feels that BSD users just pout how great BSD and get pissed off that BSD users tend to try to shit all over everyone while there really nothing special.

  23. Don't fret. by gklinger · · Score: 5, Informative

    I started out using Fink but it never felt quite right. Then I tried DarwinPorts and I've been happy ever since. As a result, when I saw this story my first thought was, "What will happen to DarinPorts?" I checked the Darwinports Mailing List Archive and found this comforting post. To summarize, DarwinPorts is alive and well and will continue. Time to start using www.darwinports.org rather than www.opendarwin.org.

    1. Re:Don't fret. by Rimbo · · Score: 2, Interesting

      Thanks for looking that up, and for the link. I, too, became a DarwinPorts fan after being disappointed with Fink. Fink has the better name, but DarwinPorts -works- better for me. I've never had problems with a DP package installing correctly; whereas I had all kinds of troubles with Fink.

      DP's "it just works" capabilities means I get more work done.

    2. Re:Don't fret. by Anonymous Coward · · Score: 0

      Exactly my experience. Good to hear they aren't going down.

      For a minute I thought "shoot, which package system do I have to start using now?"

  24. Netcraft confirms it by pchan- · · Score: 1

    OpenDarwin is dying. Another crippling bombshell hit the beleaguered OpenDarwin community, dot dot dot

    Listen, it's been over twenty minutes since this story was posted, and I haven't seen a Netcraft confirmation post yet. How do I know it's really dying? C'mon, people, get on the ball.

  25. Re:Apple Rapidly Losing Its Cool by paulmer2003 · · Score: 4, Funny

    No need for amarok, just do this. ls * > ./playlist && mplayer -shuffle -playlist ./playlist Or ls */*.mp3 > ./playlist && mplayer -shuffle -playlist ./playlist :) mplayer for life, bitches.

  26. Sorry, nice try. by mh101 · · Score: 1

    Linked site says "Page Not Found"


    --
    Duct tape is like the Force. It has a light side, a dark side, and it holds the universe together.
    1. Re:Sorry, nice try. by mjeppsen · · Score: 1

      Linked site says "Page Not Found"

      Yet that won't stop posters from commenting on it...
      You must be new here. :-)

  27. Re:Sometimes I wish I weren't such a sux programme by QuantumG · · Score: 1

    Most of the linux crowd don't know why gtk+ Qt because they believe C > C++. What's funny is that I've heard of Python users who believe this. Last time I looked the PyQt bindings were way cleaner than the PyGtk bindings. Blah, whatever.

    Personally, I have no idea why people want to run any proprietary software on their Linux box, except maybe games and "shit you can't live without". Maybe no-one who uses a Mac ever migrates to Linux. :)

    --
    How we know is more important than what we know.
  28. now is the time... by Anonymous Coward · · Score: 1, Informative

    to switch to GNU Darwin (http://www.gnu-darwin.org/)
    I haven't used it myself, but it seems to be more of a full system (with GNOME and WindowMaker) and more actively developed than OpenDarwin ever was.

  29. What a surprise... by evilviper · · Score: 0, Troll

    Gee... You mean lifting large chunks of code from other free operating systems to create a slow and very limited OS, and then imposing restrictive license terms on that free code, somehow doesn't automatically lead to an OSS project everyone wants to jump on???

    I'm SHOCKED! Shocked I say!

    Somehow I don't think the end of OpenDarwin is going to mean Apple will stop lifting code from the BSDs.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    1. Re:What a surprise... by jeffbax · · Score: 1

      Nevermind that Apple employs many people responsible for FreeBSD Development too...

    2. Re:What a surprise... by Shrithe · · Score: 5, Insightful

      Somehow I don't think the end of OpenDarwin is going to mean Apple will stop lifting code from the BSDs. Why should it? BSD is not and never has been about creating a world seperate from commercial software. They're not "lifting" the code, they're using it according to it's liscence, which is something nearly every vendor, commerical or not, does, if only for OpenBSD's ssh implementation.

    3. Re:What a surprise... by Anonymous Coward · · Score: 1, Insightful

      Somehow I don't think the end of OpenDarwin is going to mean Apple will stop lifting code from the BSDs.

      If the BSD developers cared about their code getting "lifted," they wouldn't have released it under the BSD license, which was designed to permit exactly that. That's sweet that you're offended for them, but you don't have to be.

      Also, to clarify, OpenDarwin was the community-driven fork of Darwin. Darwin itself is still open-source (which the BSD license does not require).

    4. Re:What a surprise... by evilviper · · Score: 3, Insightful
      They're not "lifting" the code, they're using it according to it's liscence,

      That wasn't the point at all. The point is that Apple has been saying what great OSS supporters they are, and now they are even discontinuing the tiny bit of code sharing they have done.

      There's nothing illegal or really wrong here... just more of Apple's slimy marketing tactics.

      But hey, who can argue with the company who came out with the first 64-bit computer?!
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    5. Re:What a surprise... by Halo1 · · Score: 5, Insightful

      The point is that Apple has been saying what great OSS supporters they are, and now they are even discontinuing the tiny bit of code sharing they have done.

      No, they are not. Apple's code sharing has always happened via its own website. OpenDarwin was not run by Apple, although several Apple engineers supported and actively participated in its various projects.

      That doesn't mean that it's sad that Apple has not been able to create a satisfactory policy which allowed external developers work directly on Darwin and contribute to it. It's not like they can't do it in general, as in case of the WebKit project some external developers even got direct commit access (which is more than what the OpenDarwin people wanted, afaik they just wanted their fixes to be incorporated by Apple).

      I guess in case of XNU, things conflict(ed) too much with Apple's product secrecy policy...

      --
      Donate free food here
    6. Re:What a surprise... by Eivind+Eklund · · Score: 2, Insightful
      That wasn't the point at all. The point is that Apple has been saying what great OSS supporters they are, and now they are even discontinuing the tiny bit of code sharing they have done.

      (A) OpenDarwin wasn't run by Apple.

      (B) Apple is sharing code both by distributing it directly and (occasionally) by having Mac OS engineers commit it directly into the FreeBSD tree. The latter means that people from Apple are doing all the adaption work to actually make the code directly usable by the upstream.

      While I wish there was even more of (B), I blame the low level on inadequate tools - the version control systems in use make this a pain to do. That's also the reason for much of the divergence of Free/Net/OpenBSD.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    7. Re:What a surprise... by daveschroeder · · Score: 1

      OpenDarwin has nothing to do with Darwin. OpenDarwin was not run or hosted by Apple. It was a completely separate, third-party project (though some folks from Apple participated).

      Apple's open source code sharing happens here, on Apple's own site. Everything in Darwin source that's ever been open still is open, on PowerPC *and* Intel, with *one* exception: the kernel (xnu) on the Intel platform. And here's the facts on xnu on Intel.

      Might there not be, oh, I don't know, a huge Apple developer conference coming up in less than two weeks where we might find out more information on this?

    8. Re:What a surprise... by daveschroeder · · Score: 1

      How do you know xnu will remain closed? Other than the fact there hasn't been a xnu release *yet* on Intel in the 10.4.x Intel tree, this is what Apple has officially said on the topic. I'll agree wholeheartedly that xnu on Intel is closed *now*, but every other traditionally open source Darwin component is still open on PowerPC and Intel, including xnu on PowerPC. Since Leopard will be Universal (i.e., won't have two trees like 10.4.x does), might we not wait for the huge developer conference that's happening in less than two weeks time to see what's going on?

    9. Re:What a surprise... by Halo1 · · Score: 1

      How do you know xnu will remain closed?

      I didn't say anything about the fact that the full Intel kernel source hasn't been released yet, nor about what Apple will do (or not) in the future.

      When I said "I guess in case of XNU, things conflict(ed) too much with Apple's product secrecy policy...", I was referring to the fact that for external people it's very hard to do any fundamental work at all on XNU, since they don't know what Apple is doing in parallel and it's quite possible that by the next major Mac OS X release the part they worked on doesn't exist anymore in a matter of speaking (or is completely rewritten by Apple).

      I contrasted this with the WebKit development, whose development can be followed live by pretty much everyone out there, and to which several external people have gotten commit access already.

      I doubt the XNU secrecy policy of Apple will change any time soon, this is how they have always worked and it's an inherent part of their marketing strategy (opening up XNU development in the way they did with WebKit would either lay open their future hardware plans or at least increase the risks of "leakage", as well as possibly other surprises Steve jobs may want to announce at WWDC or MacWorld).

      --
      Donate free food here
  30. Even Fink is struggling by jdbartlett · · Score: 1

    I try to use Fink when I can, but I like to stay on the bleeding edge. Everything in Fink seems so out of date. Ruby is still version 1.8.2, for example. That's the version that ships with Tiger in the first place!

    I don't like to complain, though. Fink is still a wonderful concept. I just wish its admins didn't already have so many things they need to dedicate their time to.

    In the meantime, though I do my development work and some testing on my Powerbook, my stable test server is an Ubuntu box. It's just easier to keep up-to-date, what with apt-get and all.

    1. Re:Even Fink is struggling by b17bmbr · · Score: 1

      just get the source. it compiles fine. I put it in /usr/local/bin while OSX puts their version in /usr/bin. other than that, most OSS packages should compile with minor tweaks. even the latest python conpiles perfectly. again, I put the latest version in /usr/local/bin so that OSX's default is not touched. some OSS apps come compiled into OS X bundles like gimp-app. sure it's more work, but it's not impossible. for what it's worth, Apple knows that it's bread and butter is not with FOSS, but that all the *nix and FOSS are simply a value added for those in the know. plus, it gives them a great platform to sell for web development, with apache, etc., already built in. it would be nice if Apple was more OSS friendly, but it serves them very little. they've been less than helpful and open with the core OS and perhaps that is the reason opendarwin is closing. Apple has alot of license issues and many things, like wireless, won't work with darwin alone. so, to get a truly working system, you need OS X, not just darwin.

      --
      My problem? I was perfectly gruntled, until some numbnuts came by and dissed me.
    2. Re:Even Fink is struggling by jdbartlett · · Score: 1

      Yeah, that's what I ended up doing with Ruby in the end. Fortunately, Ruby couldn't be any easier to compile and build manually. I put mine in /usr/local/bin/, too (and then altered my PATH in ~/.profile, of course!) I think it's what the readme recommended, as well.

    3. Re:Even Fink is struggling by King_TJ · · Score: 1

      I felt the same way. I really liked Fink (and even the FinkCommander GUI front-end for it), but it always feels like I'm getting "stale" software using it. I got to the point where I quit playing around with it for now.

      I think the fact is, this sort of development in OS X is always going to be of "niche" interest only - since so many Mac users will never care about tinkering with open source software and the X environment.

      Instead of multiple projects, I'd rather see everyone interested in this get behind Fink and help make one up-to-date, respectable system.

    4. Re:Even Fink is struggling by jdbartlett · · Score: 1
      alistair's advice worked well for me:
      To configure Fink to use unstable, edit /sw/etc/fink.conf, add unstable/main and unstable/crypto to the Trees: line, and then run fink selfupdate; fink index; fink scanpackages.
      Now I have a lot more packages more up-to-date.
    5. Re:Even Fink is struggling by b17bmbr · · Score: 1

      my only concern with future OS X versions is that Apple veers from a UNIX core. As long as I can get AMP, python, etc., identical to linux, then I'm not going to get religious or anything. for me it's more practical. I don't know enough about the core internals of a UNIX system, but I imagine it is possible that Apple breaks compatibility in the future. it's not like they haven't done that already, many times over. I can't say that I don't care taht Apple has basically abandoned its true open source venture, but they still pimp open source to a degree. I guess if they feel that there is little value in that as a sales pitch, they'll walk away. their market is rapidly expanding, and it's not coming from linux/unix geeks. it's coming from people fed up with windows and wouldn't know (or care about) a command line from a traut line.

      --
      My problem? I was perfectly gruntled, until some numbnuts came by and dissed me.
    6. Re:Even Fink is struggling by jdbartlett · · Score: 1

      If Apple breaks away from its Unix-like core, my primary OS will become Linux. In practical terms, the only reason I stick with OS X rather than going all Linux is to use commercial apps like Photoshop and Flash natively. To me, that's nowhere near as important as proper support for scripting languages and tools like emacs, vi, subversion, etc.

  31. oh the irony by Anonymous Coward · · Score: 0

    Natural selection at its finest!

  32. Merely the latest in a long run of OSS failures by Anonymous Coward · · Score: 1, Interesting
    OpenDarwin was originally created with the goal of providing a development environment for building and developing Mac OS X sources as well as developing a standalone Darwin OS derivative. OpenDarwin was meant to be a development community and a proving ground for fixes and features for Mac OS X and Darwin, which could be picked up by Apple for inclusion in the canonical sources. OpenDarwin has failed to achieve its goals in 4 years of operation, and moves further from achieving these goals as time goes on. For this reason, OpenDarwin will be shutting down.

    Over the past few years, OpenDarwin has become a mere hosting facility for Mac OS X related projects. The original notions of developing the Mac OS X and Darwin sources has not panned out. Availability of sources, interaction with Apple representatives, difficulty building and tracking sources, and a lack of interest from the community have all contributed to this. Administering a system to host other people's projects is not what the remaining OpenDarwin contributors had signed up for and have been doing this thankless task far longer than they expected. It is time for OpenDarwin to go dark.


    So much for OSS "community" stepping up to the plate. What, is it only if you're taking on Microsoft that you guys give a damn about a project? And it's not a shock that many of you OSS devs were mooching off of OpenDarwin's servers to host your insignificant little projects, while contributing nothing to the OpenDarwin project itself.
  33. Re:Sometimes I wish I weren't such a sux programme by QuantumG · · Score: 1

    The idea of improving GnuStep so it is binary compatible with the OS-X api is so you can run OS-X binaries.

    The fact that I can't think of a single OS-X binary I'd want to run for which there isn't a corresponding windows binary might has something to do with why no-one wants to improve GnuStep in this way.

    --
    How we know is more important than what we know.
  34. BSD's fault. by mactari · · Score: 1, Insightful

    Look, not to get too preachy, but that's the problem with FreeBSD and projects with other, equally open licenses, like MIT, etc. As I said in my not-so-tongue-in-cheek blog to the audienceless ether years ago...

    These licenses [X11, BSD, MIT] don't do enough to protect the contributions of the people that made the code -- they essentially enable legalized plagiarism. It's certainly one's right to make code that's this unregulated, but these licenses are from nearly overly altruistic motavations.

    I'm using OS X right now. I'm happy FreeBSD enabled its creation. I'm posting from Safari. I'm happy Konq's code helped Apple build this very fast, mature browser. Without totally free and open licenses like the ones I wrote about, above, we wouldn't have this OS X.

    Yet at the same time, this happiness doesn't change that I wish Apple would have partnered with GNU/Linux. We'd see a very different OS X and a very different collaboration (some would argue a "collaboration" would be a new thing, and I believe I agree) between Apple and the GNU hacker community today. Linux has not yet come close to hitting the tipping point on the desktop for the typical semi-technical user. With Apple's help, it would be much closer. With BSD's sabotage -- the license -- that help and the FreeBSD code has been thrown into the closed system of consumerist capitalism.

    --

    It's all 0s and 1s. Or it's not.
    1. Re:BSD's fault. by PCM2 · · Score: 4, Informative
      These licenses [X11, BSD, MIT] don't do enough to protect the contributions of the people that made the code -- they essentially enable legalized plagiarism.

      Proponents of said licenses would question just what it is the contributors want to protect. Did they turn over the code for public use or didn't they? You can't plagiarize something that was offered to you as a gift -- and that's sort of the point of open source, isn't it? That your work becomes part of the commons?

      I question the motives of open source developers who use the GPL because it affords them plaudits for the authorship of their code. The GPL doesn't really care about any developers' desire to receive credit and accolades for their efforts. The only real reason the GPL requires that works derived from GPL-licensed works must also be GPL-licensed is political. The GNU Foundation wants to spread the political cause of Free Software. The GPL is one way to do this.

      Many other developers lack these political ambitions, however. For them, the BSD style license is perfectly fine. It protects them in various ways, like limiting the developers' liability, without the entanglements of Richard Stallman's political agenda. At the same time, it allows them to offer some code to the community, without any selfish motives of social status.

      --
      Breakfast served all day!
    2. Re:BSD's fault. by styrotech · · Score: 2, Interesting
      I'm using OS X right now. I'm happy FreeBSD enabled its creation. I'm posting from Safari. I'm happy Konq's code helped Apple build this very fast, mature browser. Without totally free and open licenses like the ones I wrote about, above, we wouldn't have this OS X.


      Are you aware that Konqueror is GPL? And that KHTML is LGPL?

      Maybe Apple chose FreeBSD for other reasons than the BSD license? I'd say that their web browser is a strategically more important component to Apple and its userbase than some unix userland utils. If Apple really was anti GPL, they could've used Gecko as the MPL is closer to BSD style licenses than the GPL is.
    3. Re:BSD's fault. by Anonymous Coward · · Score: 0

      Y'know, the thing, in my estimation, that BSD license critics don't understand is that not everybody has an agenda. The FreeBSD authors don't care that Apple can take their code and give little to nothing back, or else they wouldn't have licensed the code under such open terms. The only people who are up in arms about this are Linux users, who think of everything in terms of a war between free and proprietary software.

      Oh, and another thing that's funny to me: I use FreeBSD on my servers, and I haven't paid them a cent, contributed any code, or anything of the sort. Probably a ton of *BSD and Linux users match my profile. So it's okay for us to exploit these poor coders, but Apple is held to a different standard because why? They make (horror) money off it? They're a big company? I mean, what? It's a weird attitude to me.

      I just find it ridiculous that people are "blaming" the BSD guys for doing what they want with their own work, as if they're being irresponsible by helping the enemy of proprietary software. Like I said, not everybody has an agenda, and the ones that do, well, they have Linux.

    4. Re:BSD's fault. by evilviper · · Score: 5, Insightful
      they essentially enable legalized plagiarism.

      Plagarism is failing to credit the source, while the BSD license requires proper atribution.

      but these licenses are from nearly overly altruistic motavations.

      Any non-commercial software (including GPL'd) is written from altruistic motivations. Who are you to say how far that altruism should go? Indeed, many of the major pieces of software we use wouldn't have become standards if they were under a more restrictive license.

      With BSD's sabotage -- the license -- that help and the FreeBSD code has been thrown into the closed system of consumerist capitalism.

      Apple surely wouldn't have used Linux, even if FreeBSD wasn't there... they would have paid some company for some closed-source Unix code, or perhaps have used the NEXT code directly, rather than accepting the GPLs limitations. The fact that OS X is a better operating system for the BSD licensed code is an indirect benefit to me, and you, and everyone else, while the alternative wouldn't at all benefit the public at large.

      Frankly, it's sad to see how the more extreme Linux zealots are using the BSDs as a scapegoat for all of Linux's shortcommings.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    5. Re:BSD's fault. by mwvdlee · · Score: 1

      As somebody who primarily uses ZLib/LibPNG (Very close to BSD) for OS projects, I tend to agree.

      Especially with the "upwards-compatibility" which was default in previous versions of GPL (and, luckily, Linux removed from the license) and the new GPL3 purely political anti-DRM terms, I'm sure I don't share RMS's vision of "forced freedom".

      (L)GPL is just a major force nowadays and I think most people use it because that's all they know. I'm sure many developers would prefer licenses like Apache's and Mozilla's if they studied the topic a bit.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    6. Re:BSD's fault. by Jah-Wren+Ryel · · Score: 2, Insightful

      Frankly, it's sad to see how the more extreme Linux zealots are using the BSDs as a scapegoat for all of Linux's shortcommings.

      Huh wuh? OpenDarwin was frozen out of the information and code required to remain relevant, but what you hear are people blaming BSD for Linux's problems? I don't see anyone talking about problems with linux here, after all linux is thriving and opendarwin is, well, deceased. Doesn't sound like a shortcoming to me.

      --
      When information is power, privacy is freedom.
    7. Re:BSD's fault. by Sam+Ritchie · · Score: 4, Insightful
      ...what you hear are people blaming BSD for Linux's problems?

      GGP said:

      Linux has not yet come close to hitting the tipping point on the desktop for the typical semi-technical user. With Apple's help, it would be much closer. With BSD's sabotage -- the license -- that help and the FreeBSD code has been thrown into the closed system of consumerist capitalism.

      This does sound to me like someone blaming BSD for Linux's (perceived) problems, and I agree with GP that it's a pretty sad assertion. I don't agree it's an attitude that can be generally attributed to 'extreme [GNU/]Linux zealots' - most I know would consider any negative opinion of the Linux desktop to be heresy, and any hypothetical Apple assistance would be derided as an undesirable dumbening of self-evident UI perfection.

      --
      This sig is false.
    8. Re:BSD's fault. by cafard · · Score: 1

      I question the motives of open source developers who use the GPL because it affords them plaudits for the authorship of their code.

      I suspect you're targeting a minority. I use the GPL, but i couldn't give a s**t about the plaudits. As a lot of people, I use the GPL simply because i'm too selfish to do otherwise. I want my work to be useful to me, and to my 'community'. I make my code available, i want all its derived works to be available on the same terms, so that they may profit me or said community. The BSD license doesn't work for me, as it wouldn't bring me this guarantee.

      That said, i have nothing against anyone using BSD style licenses, and fully agree with you that it didn't 'fail' protecting the contributions of people that made the code. It's usually misinformed GPL users that lament that failure. BSD licenses are designed specifically to allow software like OSX to make use of it. It was used exactly as the authors of reused code planned. Nothing wrong here.

      --
      This post is awesome.
    9. Re:BSD's fault. by cafard · · Score: 1

      Frankly, it's sad to see how the more extreme Linux zealots are using the BSDs as a scapegoat for all of Linux's shortcommings.

      Maybe the sad thing is that you'd expect the more extreme zealots to act in a reasonable fashion.
      Or that such a comment was modded insightful...

      --
      This post is awesome.
    10. Re:BSD's fault. by kjart · · Score: 1

      Look, not to get too preachy, but that's the problem with FreeBSD and projects with other, equally open licenses, like MIT, etc. As I said in my not-so-tongue-in-cheek blog to the audienceless ether years ago...

      Oh my, what a relevant and insightful reference - and one that clearly supports your point of view. I'd just like to refer to a famous reply that I made to this comment, in which I said it was too late.

    11. Re:BSD's fault. by Anonymous Coward · · Score: 0
      It is official. Netcraft now confirms: *BSD is dying

      One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

      You don't need to be the Amazing Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.

      FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.

      Let's keep to the facts and look at the numbers.

      OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

      Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

      All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save *BSD at this point in time. For all practical purposes, *BSD is dead.

      Fact: *BSD is dying

    12. Re:BSD's fault. by Eivind+Eklund · · Score: 1
      The economics of your proposition seems quite unlikely. (As in: Corporations will use proprietary codebases they have to pay for instead of using GPLed codebases.)

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    13. Re:BSD's fault. by mactari · · Score: 2, Interesting

      >they essentially enable legalized plagiarism.

      Plagarism is failing to credit the source, while the BSD license requires proper atribution.


      That's why I said that they "essentially". How many IE users know the code is based partially on Mosaic? Yet the "proper attrbution" is right there in the About box. MS took it, and now everyone considers it theirs. I haven't heard many blame the NCSA for winning the browser wars. That's essentially plagiarism. End of story.

      >but these licenses are from nearly overly altruistic motavations.

      Any non-commercial software (including GPL'd) is written from altruistic motivations. Who are you to say how far that altruism should go? Indeed, many of the major pieces of software we use wouldn't have become standards if they were under a more restrictive license.


      Two points:

      1.) Sure GPL is altruistic. BSD is overly so, imo, because it allows itself to become exploited, as has happened with OS X. This doesn't happen with the, IMO, "less altruistic" GNU/Linux.

      2.) I won't tell you how far your altruism can go, but I will give you my opinion how far it's smart to go to prevent your contribution from becoming what some might call exploited. This thread is, in large part, about Apple not providing enough to make Darwin a viable open source OS. Why could they based their entire OS on Darwin and not passively partner with a viable community of open source hackers? B/c of BSD.

      >With BSD's sabotage -- the license -- that help and the FreeBSD code
      >has been thrown into the closed system of consumerist capitalism.


      Apple surely wouldn't have used Linux, even if FreeBSD wasn't there... they would have paid some company for some closed-source Unix code, or perhaps have used the NEXT code directly, rather than accepting the GPLs limitations. The fact that OS X is a better operating system for the BSD licensed code is an indirect benefit to me, and you, and everyone else, while the alternative wouldn't at all benefit the public at large.

      Absolutely right, to a point. I'd rather see Apple have to pay for new development than steal from open source. No, I'd rather Apple feel the ethical, if not legal, obligation to give more back to the FreeBSD community. Sites like OpenDarwin should not have to struggle to stay afloat. People should not have to complain about unbuildable packages being released by Apple. Apple should take their place in the open source community more seriously. They haven't.

      Frankly, it's sad to see how the more extreme Linux zealots are using the BSDs as a scapegoat for all of Linux's shortcommings.

      I hate Linux. ;^) There, I said it. As I implied in my first post, I use OS X first, and get this, I use Windows second. I like Visual Basic. No, love VB for some tasks. I think C# is great. I know asp inside and out. I hate using C. I hate Perl. I hate *NIX. [These are slight overstatements.]

      This is precisely why I'd prefer Apple's millions in Darwin development had been given back to the community in a fashion that would have made both better. The GPL would have done that, as would a more ethical Apple. If you've got a better way of ensuring BSD doesn't short-circuit into one-way, lossy contributions to multi-national, billion dollar corporations, I'm ready to hear it.

      --

      It's all 0s and 1s. Or it's not.
    14. Re:BSD's fault. by cbr2702 · · Score: 3, Interesting
      Proponents of said licenses would question just what it is the contributors want to protect. Did they turn over the code for public use or didn't they? You can't plagiarize something that was offered to you as a gift -- and that's sort of the point of open source, isn't it? That your work becomes part of the commons?
      Becomes part of the commons -- and stays there.

      I question the motives of open source developers who use the GPL because it affords them plaudits for the authorship of their code. The GPL doesn't really care about any developers' desire to receive credit and accolades for their efforts. The only real reason the GPL requires that works derived from GPL-licensed works must also be GPL-licensed is political. The GNU Foundation wants to spread the political cause of Free Software. The GPL is one way to do this.
      I don't know what the true motivations of the GNU Foundation are in promoting the GPL, but I do know mine. Software that I have released under the GPL has not been political. It does something I find useful and that I think others might find useful as well. At the same time, I put some work into it, and if someone makes improvements I would like to be able to use them. If I wanted instead to be sure I got credit I would use the origonal BSD liscence or one of the many other ones that require attribution.

      Many other developers lack these political ambitions, however. For them, the BSD style license is perfectly fine. It protects them in various ways, like limiting the developers' liability, without the entanglements of Richard Stallman's political agenda. At the same time, it allows them to offer some code to the community, without any selfish motives of social status.
      When you release something to the community with the intent for it to be free, is it selfish to want it to remain free?
      --


      This post written under Gentoo-linux with an SCO IP license.
    15. Re:BSD's fault. by cbr2702 · · Score: 1
      Plagarism is failing to credit the source, while the BSD license requires proper atribution.

      It does? The relavant portion seems to be:

      modification, are permitted provided that the following conditions are met:

      * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
      * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
      * Neither the name of the University of California, Berkeley nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.
      Perhaps you meant the advertising clause?

      3. All advertising materials mentioning features or use of this software
      must display the following acknowledgement:
      This product includes software developed by the University of
      California, Berkeley and its contributors.
      But this clause is usually not included in "BSD-Liscensed" projects. So it looks like there's no compulsary attribution in standard BSD.

      Any non-commercial software (including GPL'd) is written from altruistic motivations. Who are you to say how far that altruism should go? Indeed, many of the major pieces of software we use wouldn't have become standards if they were under a more restrictive license.

      Nope. I've written software that I thought would be useful to me. I then released it (GPL) with the dual motivation that someone would find it useful and that people might make improvements. The former is altruism, but if my motivations were entirely selfish I would still release software that I thought other people would find useful because that increases the chances that others will work on it. Alternately, look at IBM. They're a for-profit entity and not supposed to be altruistic. But they think work on open source projects is still in their interest because they benifit from the 'ecosystem' that arises.

      --


      This post written under Gentoo-linux with an SCO IP license.
    16. Re:BSD's fault. by Jah-Wren+Ryel · · Score: 1

      I read that as the sabotage of FreeBSD by their own license, although in hindsight I can see it the other way as well. Original author is welcome to clarify his point.

      --
      When information is power, privacy is freedom.
    17. Re:BSD's fault. by mactari · · Score: 1

      I read that as the sabotage of FreeBSD by their own license, although in hindsight I can see it the other way as well. Original author is welcome to clarify his point.

      You (Ryel) have my intent. That said, though I didn't intend it, I do see their point about my seeming to blame Apple for Linux. In an extreme sense, I suppose I'm suggesting as much, though that's hardly my intended point of emphasis. I'm blaming, as you say, BSD for FreeBSD's exploitation and, contrary to my title, blaming Apple for being, well, capitalist. I find it difficult for think the latter demands much of a reprimand, however. Apple's always been pretty clear on that point.

      Open source tries to appropriate copyright within the context of consumerist capitalism to create a subversive counterforce -- no, to create a true alternative to capitalism from within a capitalist framework; GNU/Linux is an alternative to capitalism built with capitalism. I *really* dig that. The BSD license simply doesn't do this sort of work. OpenDarwin's troubles show it. GNU/Linux is a better alternative, imo, as its [hypothetical and arguably wholly impractical] possible adoption by something like OS X would include true collaboration from the paradigm it hopes to replace [as the dominant]. I'm not, however, for GPL or against BSD. I believe there is a nice middle ground out there somewhere that's even better, as I try to detail on my blog at that earlier link. I doubt we'll find -- or at least implement -- it.

      I do wonder what the background is of the people who assume that I, Mr. "I <3 VB", am a GNU/Linux zealot. Are they Windows users? Mac users? BSD users? Linux users? And what is the purpose of FreeBSD, if its supporters get upset when Apple acts like a conventionally incorporated entity living in the US trying to make a buck, bless its heart, but these same upset FreeBSD folk want to retain the option to release code in what is, let's say, an "extremely" altruistic fashion? If FreeBSD contributors hoped that entities like Apple would, out of common courtesy, seriously enter into an active or even passive partnership with them, I believe we now know that's not so likely to happen. I, too, appreciate idealism and a positive belief in our fellow humans, but things like Apple & FreeBSD have turned me into a much more hardened, well, "realist" is the word, I suppose. I think Apple should have felt an obligation to return the favor to the FreeBSD community. Just like IE and Mosaic, it hasn't happened.

      By the way, how can I find the proper attribution that OS X uses BSD code? If I use the terminal daily and don't see it, how many semi-technical users do?

      P.S. Also sorry that I didn't properly format part of my other reply wrt the "Apple surely wouldn't have used Linux, even if FreeBSD wasn't there..." paragraph. That was obviously from the previous post, and wasn't my material. Anyhow... Should have used the Preview button again, I guess.

      --

      It's all 0s and 1s. Or it's not.
    18. Re:BSD's fault. by atani · · Score: 1

      Sites like OpenDarwin should not have to struggle to stay afloat.

      While it's dissapointing to see them go, I don't quite get this attitude. Linux has 'stayed afloat' by way of a lot of struggle, along with a lot of interest, use, and momentum. As has been noted, for an end-user what did OD offer to entice them to use it as a desktop or server OS? Why would they pick OD over Linux, {Free,Open,Net,etc}BSD, Windows, OSX, or any other system? It was a nice idea (and commendable) to try provide a development environment for Darwin/OSX projects but should Apple feel compelled to support them just because they pitched their tent at Apple's door?

      The BSD license does not compel/require/force the contribution of modifications back to the open source community which is surely one of the primary reasons NeXT/Apple picked projects that were released under that license to build off of. BSD license is akin to saying "Go forth, my child, Take my name and prosper" not "Go forth, my child, take my name and prosper and give us back some of what you do." I wouldn't make any ehtical judgement between the two, they're different approaches - best to be aware of the difference though so that you can align your expectations.

      OpenDarwin's other stated goal was to provide a standalone Darwin-based alternative. That wasn't achieved either and is that the "fault" of Apple? Another stated reason for OD's closing was, in their words, "a lack of interest from the community".

    19. Re:BSD's fault. by mpaque · · Score: 1

      You can't plagiarize something that was offered to you as a gift -- and that's sort of the point of open source, isn't it? That your work becomes part of the commons?

      Having someone edit out the original author's names and put their own in on a piece of contributed code isn't plagiarism?

      Finding something you co-authored back in 1987-1990 out there with the names filed off, and a new 1997 date and copyright attached can be annoying, and definitely calls the new 'authors' ethics into question. I'm pretty sure that I'm not the only person who has encountered this.

      Alas, they didn't get my last round of bug fixes, but I'll be damned if I'll contribute to 'their' code.

    20. Re:BSD's fault. by Secret+Rabbit · · Score: 1

      > Becomes part of the commons -- and stays there.

      *cough*sony*cough*

      > When you release something to the community with the intent
      > for it to be free, is it selfish to want it to remain free?

      How about, is it selfish to require other developers to use the
      license that you choose, NOT one that they choose.

      It's all fine and good if you want to be notified of improvments,
      but requiring others to use your choosen license is just plain
      belligerent.

      Also, what someone else does with your code else-where does
      nothing to the free nature of the code that you still possess. Or
      do you as well believe that getting your picture taken will steal
      your soul?

    21. Re:BSD's fault. by Secret+Rabbit · · Score: 1

      > Having someone edit out the original author's names > and put their own in on a piece of contributed code > isn't plagiarism? Could you let the rest of us know why this isn't possible under the GPL but possible under MIT/BSD/etc style licenses, please.

    22. Re:BSD's fault. by mpaque · · Score: 1

      Having someone edit out the original author's names and put their own in on a piece of contributed code isn't plagiarism?

      Could you let the rest of us know why this isn't possible under the GPL but possible under MIT/BSD/etc style licenses, please.

      As it turns out, it is possible to be an unethical a**hole under, or in spite of, any license. If anyone knows of a licensing scheme that can successfully prohibit this sort of behavior I'd love to hear about it.

      BTW, I am a different sort of a**hole, one of the ones that goes after the unethical a**holes described above and is willing to spend cash on bringing them down. That should get me moderated 'flamebait' around here.

    23. Re:BSD's fault. by evilviper · · Score: 1
      If you've got a better way of ensuring BSD doesn't short-circuit into one-way, lossy contributions to multi-national, billion dollar corporations, I'm ready to hear it.

      You're still basing all of this on the assumtion that is a BAD THING. It's not. The very ABILITY to not have to contribute back is why the BSDs are recieving so much funding from companies that don't support Linux development.

      There are many, many situations where, for one reason or another, a company cannot contribute code back, so GPL'd code gets dismissed, and BSD code is used, where it exists. If it didn't exist, how would that make anyone any better off?

      I'm not deprived of the code I've written when some company decides to use it in their product. There is some gain to society at large when they use publicly available and standard code (just think of the Unix wars). Nothing you can do will ever FORCE companies to use GPL'd code, even if the BSD wasn't there. That's only more of rms' insane rantings, which don't work out in the real world.

      Let companies take and use the code. We're far better off for it, because if not for the BSD-licensed OpenSSH, the world would still be stuck using telnet. NFS is still in-use because all potential replacements for NFS are GPL'd, and DOA. Interestingly enough, it seems the most likely sucessor to NFS is... yes... OpenSSH as a network filesystem.

      The GPL license is fine if you want software by Open Source developers, for Open Source projects. If you want to reach the other 98% of the world, however, and have something that reaches critical mass, and gets to be standard all-around, the GPL can't possibly do it, even if the BSD wasn't around.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    24. Re:BSD's fault. by evilviper · · Score: 1
      It does? The relavant portion seems to be:
      * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

      Emphasis added. How is that NOT perfectly clear?

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    25. Re:BSD's fault. by cbr2702 · · Score: 1

      The copyright notice says who owns the copyright, not who wrote it. And in the default case that is the Regents of the University of California.

      --


      This post written under Gentoo-linux with an SCO IP license.
    26. Re:BSD's fault. by cbr2702 · · Score: 1
      How about, is it selfish to require other developers to use the license that you choose, NOT one that they choose.

      The liscense I've chosen (GPL) is pretty close to the idea that "you're free to do whatever you want with this except deny that freedom to others". If they want to choose another liscense, it can only directly or indirectly restrict someone's freedom. Directly if they want to add additional restrictions ("this software is for non-commercial use only"; "some code written by X, if you redistribute you must include this notice), indirectly if they want to allow others to have the freedom to deny freedoms. Perhaps there are minor points they would like to change, but I don't currently know of any way to deal with this tidily. If someone wants to do something strange they should talk to me.

      It's all fine and good if you want to be notified of improvments, but requiring others to use your choosen license is just plain belligerent.

      I don't just want to be notified of them, I want to be able to use them. And I want others to be able to use them. I want my programs to get better but still remain usable by anyone who wishes.

      Also, what someone else does with your code else-where does nothing to the free nature of the code that you still possess. Or do you as well believe that getting your picture taken will steal your soul?

      If they want to privately make changes for their own use, that's allowed. I have the power to keep public distribution free, so I invoke it.

      --


      This post written under Gentoo-linux with an SCO IP license.
    27. Re:BSD's fault. by evilviper · · Score: 1
      The copyright notice says who owns the copyright, not who wrote it.

      Yes, but if you wrote it, you own the copyright, unless you explicitly sold it to someone else (in which case, you're explicitly being paid so they can take credit).

      And in the default case that is the Regents of the University of California.

      There's no such thing as a "default" copyright, or anything like it. The license is written with "the Regents" in there because they originally wrote the license. It doesn't mean anything, and nobody would be stupid enough to copy it without changing it.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    28. Re:BSD's fault. by cbr2702 · · Score: 1
      There's no such thing as a "default" copyright, or anything like it. The license is written with "the Regents" in there because they originally wrote the license. It doesn't mean anything, and nobody would be stupid enough to copy it without changing it.

      Sorry; I was unclear. I didn't mean 'default' as in 'you can optionally fill in something else for regents', but instead that the standard/original case had distinct author and copyright holder. You're not being paid for someone else to get the credit, but for them to get the results of your work. A paper written by a Berkley prof would be attributed to the prof, even though the regents would get the copyright. And the prof, not the regents, gets the credit.

      --


      This post written under Gentoo-linux with an SCO IP license.
    29. Re:BSD's fault. by PCM2 · · Score: 1
      I use the GPL, but i couldn't give a s**t about the plaudits. As a lot of people, I use the GPL simply because i'm too selfish to do otherwise. I want my work to be useful to me, and to my 'community'.

      I guess that's kind of what I meant by "plaudits" -- it smacks of "hooray for us!" It doesn't sound particularly "open" in spirit -- but this is just a personal bias. I don't think there's anything "wrong" with the way you want to do things either.

      --
      Breakfast served all day!
    30. Re:BSD's fault. by Geoffreyerffoeg · · Score: 1

      When you release something to the community with the intent for it to be free, is it selfish to want it to remain free?

      This gets into an interesting cyclical definition (in the vein of God buliding a rock too heavy to lift). What if they want their work to have the freedom to lose its freedom? If you force it to be "free", aren't you restricting a freedom of it - the freedom to incorporate it into proprietary works?

    31. Re:BSD's fault. by cbr2702 · · Score: 1
      What if they want their work to have the freedom to lose its freedom?

      I don't, so I GPL.

      --


      This post written under Gentoo-linux with an SCO IP license.
    32. Re:BSD's fault. by mikefe · · Score: 1
      What if they want their work to have the freedom to lose its freedom? If you force it to be "free", aren't you restricting a freedom of it - the freedom to incorporate it into proprietary works?


      I don't mind people using my code in proprietary works as long as their improvements to my work is released in source code to anyone who receives binaries. That is why I prefer the LGPL.

      I don't like the MPL because it is not generic. Any project that uses that license ends up creating a new license with Mozila search and replaced with the project name and sometimes other changes.
      --
      There: Something at a specific location.
      Their: Owned by someone.
      Please make sure your english compiles.
    33. Re:BSD's fault. by Secret+Rabbit · · Score: 1

      My point exactly :)

      And I certainly agree with that final statment as well (been bitten by it myself).

    34. Re:BSD's fault. by Secret+Rabbit · · Score: 1
      The liscense I've chosen (GPL) is pretty close to the idea that "you're free to do whatever you want with this except deny that freedom to others". If they want to choose another liscense, it can only directly or indirectly restrict someone's freedom. Directly if they want to add additional restrictions ("this software is for non-commercial use only"; "some code written by X, if you redistribute you must include this notice), indirectly if they want to allow others to have the freedom to deny freedoms. Perhaps there are minor points they would like to change, but I don't currently know of any way to deal with this tidily. If someone wants to do something strange they should talk to me.

      The problem is that you're denying the next developer freedom and calling that your freedom. More precisely, you're saying you want people to have as much freedom as possible, but doing that by denying freedom. This is a contradiction and one that is called hypocrisy.

      If they want to privately make changes for their own use, that's allowed. I have the power to keep public distribution free, so I invoke it.

      Yes, by keeping your source tree open. Please let me know how you are not being an a**hole by forcing people to do the same. After all, if they choose the close there copy that does not mean that you have to close yours. Basically, your tree remains open as long as you want. Why force that on others?

      For that matter, why isn't a BSD license plus the "all modifications must be sent upstream" not appropriate. For that matter, why do you need to deny other developers there right to choose there own license? What does that matter for your source tree?

    35. Re:BSD's fault. by cbr2702 · · Score: 1
      The problem is that you're denying the next developer freedom and calling that your freedom. More precisely, you're saying you want people to have as much freedom as possible, but doing that by denying freedom. This is a contradiction and one that is called hypocrisy.

      Freedoms can come into conflict. And the freedom to view and modify the source code of the programs you are using is one I value above the freedom to keep others from doing so.

      Yes, by keeping your source tree open. Please let me know how you are not being an a**hole by forcing people to do the same. After all, if they choose the close there copy that does not mean that you have to close yours. Basically, your tree remains open as long as you want. Why force that on others?

      Because I want end users to be able to have access to the source code for the programs they run.

      For that matter, why isn't a BSD license plus the "all modifications must be sent upstream" not appropriate.

      That wouldn't be too bad. Provided they had to inform their distributees that they could get source code from me. But it's also practically almost the same, especially as there's not a hardship of distribution; sourceforge.net is free. The main barrier is that the GPL is established and I want my code fully liscense compatible with it.

      --


      This post written under Gentoo-linux with an SCO IP license.
    36. Re:BSD's fault. by ben+there... · · Score: 1
      Proponents of said licenses would question just what it is the contributors want to protect. Did they turn over the code for public use or didn't they? You can't plagiarize something that was offered to you as a gift -- and that's sort of the point of open source, isn't it? That your work becomes part of the commons?

      I've contributed to a couple of GPL projects because I'm selfish. I make my changes, create a patch, submit it to the project owner, and wait while using my patched version. Usually in a couple of weeks, an improved version gets committed with the project owners own changes and I can use that instead. It's better than both the original and my patched version. So I contributed and I got something back.

      I wouldn't bother submitting the patch in the first place if I didn't expect to benefit from further improvements to the code.
  35. Obvious question... by WasterDave · · Score: 1

    So, what were it's goals?

    Dave

    --
    I write a blog now, you should be afraid.
    1. Re:Obvious question... by argent · · Score: 1

      As a bridge between OS X and other BSD-based platforms, they were doing a great job. But I guess that wasn't what they had in mind. If the goals were to create a platform compatible with OS X but independant of Apple, which is what it sounds like, they were in trouble from the start.

  36. Re:Apple Rapidly Losing Its Cool by nukem996 · · Score: 1

    You could use Linux and use wine or cross over to run the win version of iTunes.

  37. Re:Sometimes I wish I weren't such a sux programme by novus+ordo · · Score: 1

    I use gtk+ instead of Qt because the licensing. Either way there's gtkmm that uses c++ anyway so your argument there is moot.

    --
    "You're everywhere. You're omnivorous."
  38. example: OsiriX by Anonymous Coward · · Score: 1, Informative

    > I mean, what Mac apps would you want to run on Linux that you can't find a windows version to run on Wine or some windows emulator.

    OsiriX Medical Imaging Software: http://homepage.mac.com/rossetantoine/osirix/

    The code is written for MacOS X, using Cocoa I think. It is free software (GPL), but requires proprietary libraries to work.

    On the converse side, frhed, a great free (GPLed) Windows hexeditor could simply not run on Linux/BSD if it weren't for the existence of a free compatability layer (wine/winelib).

    Yes, Linux/BSD needs GNUStep to become a better compatability layer for OS X apps, if only for source compatability with the GPLed/etc OS X applications that exist. Yes, re-implementation is important for Linux/BSD - witness GNU Classpath and all that free java, witness osflash.org, witness wine/winelib, witness octave (matlab thing). Free sofware/open source *cannot* afford to ignore proprietary APIs and to some extent ABIs (mainly to bring people closer to Linux/BSD).

    For those who want to pay for MacOS X, there is always Mac-On-Linux, but obviously that still ties you to non-free software (as well as Linux).

  39. Re:Sometimes I wish I weren't such a sux programme by QuantumG · · Score: 1

    No, see, the reason why Qt owns over gtk+ is simply the fact that Qt is internally a work of art, and gtk+ is internally a dog's breakfast.

    --
    How we know is more important than what we know.
  40. Goals and an open source project by PenguinX · · Score: 1

    In my experience, the 'achievement and goals' mentality seem to stem from a corporate-culture, while open source projects generally have a vision but the vision can change over time and the 'goals' change with the community. In general what I've noticed is that projects that concern themselves with the community rather than the goals tend to stay afloat longer than those that have a directive. If opendarwin became a place where osx-focused oss projects were housed / referenced, then why call that a failure? Perhaps it wasn't what the creators of the project had in mind initially, but it seems pretty unfortunate to loose this resource in the community.

    1. Re:Goals and an open source project by anothy · · Score: 1

      i agree on a few counts: the goal focus for projects probably comes (at least in significant part) from the corporate world, and projects which focus on community rather than goals tend to stick around longer. but your conclusion from this strikes me as totally backwards. the result of a strictly community-focused group is one which sticks around, but never accomplishes anything. the OpenDarwin directors considered the state of things a failure because they didn't accomplish their goals. i'm not even sure how else you'd define "failure". it became, instead, a hosting site - which there are already plenty of, which do a perfectly fine job, run by people for whom that is their goal.

      building a community is a perfectly reasonable goal, of course. but this idea that goals are somehow "corporate" and therefore antithetical to community spirit or some nonsense like that is one of the most detrimental (and pervasive) ideas in the open source world.

      --

      i speak for myself and those who like what i say.
  41. Re:Sad - no; just inevitable by Anonymous Coward · · Score: 0

    It seems to me that this is a fundamental problem and it shows the total failure of the "Open Source" cooperate with proprietary approach over the "loony" free software people who want only to cooperate with those who share.

    Analysed from the Open Source point of view, inevitably Open Darwin and it's "bazzar" development should have quickly overtaken Apple. Soon it would have become the main source of Darwin code.

    Analysed from the Free Software point of view, Open Darwin had at it's heart a cancer of Apple's proprietry code and proprietary control. The death of the project was inevitable. Apple would always be losing control, the more code moved into the free parts of OS X. Anybody sensible could see that contributing to such a project where inclusion was controlled by could only advance Apple's agenda and would be largely used against users.

    The lesson to be drawn is that the elimination of proprietary (and I DO NOT mean commercial) influence from Free Software projects should always be the first priority.

    Think of the amount of effort that could have been spent improving Linux or OpenBSD to be better in every way as OS X and has now been lost to Darwin. Think of the extra effort that can now be made in future due to the collapse of this project. Try to apply those efforts so that the work of OpenDarwin has not been entirely in vain.

  42. Re:Sometimes I wish I weren't such a sux programme by dpetzold · · Score: 1

    Yes perhaps, but Qt does stand a chance against mono or (c# + gtk + U). The way I see it the dog has ate its breakfast and is now running past its former competition...

    Regards,

  43. Re:Sometimes I wish I weren't such a sux programme by dpetzold · · Score: 1

    Yes perhaps, but Qt does not stand a chance against mono or (c# + gtk + U). The way I see it the dog has ate its breakfast and is now running past its former competition...

    Regards,

  44. Survival.. by coralsaw · · Score: 1

    of the fittest. Darwin was right yet once more then..

    --
    <before>now</before>
  45. Fink is not out of Date! by alistair · · Score: 3, Informative
    Fink mirrors the Debian release cycle so you have stable packages whiich are generally a few versions behind current and unstable (which I have always fount to be stable) which are generally bleeding edge. The unstable release of Ruby is 1.8.4 which is current.

    To configure Fink to use unstable, edit /sw/etc/fink.conf, add unstable/main and unstable/crypto to the Trees: line, and then run fink selfupdate; fink index; fink scanpackages.


    You should now find you have more than 5000 packaes instead of 1800 to choose from and the latest version oof PERL, Ruby, KDE etc. are all there. You will have to update all your old packages to use them though, with Fink you can either choose stable or unstable, not a mixture. Having said that I have over 1000 unstable Fink packages installed on this mac aand they work fine.

    Happy finking.
    1. Re:Fink is not out of Date! by jdbartlett · · Score: 1

      Tonight, you are a god. Though I'm pretty sure Ruby 1.8.4 is stable (it's also the version apt-get install installed on my ubuntu machine).

    2. Re:Fink is not out of Date! by Anonymous Coward · · Score: 0

      Great. Except that the mechanism for contributed packages by those without access to Fink's CVS tree is woeful. They sit in a tracker and never go anywhere. It just drives developers away from the system.

    3. Re:Fink is not out of Date! by cbr2702 · · Score: 1

      Debian's idea of 'stable' is distinct from individual projects' definitions. Debian testing contains mostly projects rated 'stable' by their admins, and over time as it becomes clear that these versions really are stable they get moved into Debian stable.

      --


      This post written under Gentoo-linux with an SCO IP license.
    4. Re:Fink is not out of Date! by IpalindromeI · · Score: 1

      To expound a bit on the other reply, Debian's classification of "stable," "testing," and "unstable" refer to the entire repository's rate of change, not to the fitness of the packages. The stable tree sees very few package updates, mainly just security fixes, which is why the packages are usually so old; they don't update them so that server administrators don't have to worry about things changing. The unstable tree is where updated packages hit first, so it's changing all the time. As a repository, it's quite volatile.

      As a regular user, I run against unstable because I want updates as soon as they're available, which is how I imagine other distributions like Fedora work. It doesn't mean your system will be unstable, and actually I've never had a package upgrade break my system. I guess I could be lucky on that count, though.

      --

      --
      Promoting critical thinking since 1994.
  46. Arguing with yourself is the first sign. by kfg · · Score: 1

    Losing is the second.

    But when you do it while claiming to be someone famous they come to take you away, ho, ho, he he, ha, ha!

    KFG

  47. Re:Apple Rapidly Losing Its Cool by paulmer2003 · · Score: 1

    Whats with mod for funny - I was being serious. Its how I listen to my music :S

  48. Re:Sometimes I wish I weren't such a sux programme by QuantumG · · Score: 1

    You can wrap a turd in tin foil but you'll never make a jewel.

    --
    How we know is more important than what we know.
  49. The way it is by luketheduke · · Score: 1, Insightful

    Having used both Mac and Linux. I've come to this conclution. Linux is powerful. Mac is powerful. But lets face it guys when was the last time you had to stay up all night getting an freakin program installed on a Mac?...that wasn't open source "cough". Linux works well as a server not a desktop and even then a simple sudo yum update on a production box can blow away the config files you spent 4 days setting up don't say you've never had any "simple" problems with linux also there not even one server management package that comes close to Apple's on Linux. Here is the way i look at it say you want a barn. You have two options you can buy one that is already made and start using it the way it was designed start being productive or you can build one which you may not know exactly how to so there's alot of stuff to learn and figure out before you're ever able to use it. There's an infinite amount of ways you can build it which has its benifits and disadvantages. Main disadvantges being time and energy. Apple has its "way" of doing things, because of this it is easier to control what you are able to do. When you have control you have stability. Now some of you may say blaaaa thats why we use OSS. Everytime i've gone to do something on a mac there's hardley ever a better way to do it than their way. WHICH WORKS!! at any rate some how i'll suffer through my Quad G5 with 8gigs of ram and my 30" Cinema Display with my working NVIDIA graphics card drivers......ohh pooo i wish i could have a fancy linux box :-P Pile of wood or Amish construction!!

    1. Re:The way it is by Anonymous Coward · · Score: 0
      I've never had to stay up all night getting a program to compile on linux, even when I used to build everything myself. The problem you face is that you are not a computer user, you are a computer application user; as confirmed by your unqualified boasting. Hardware is pointless unless you are actually using it for something, what exactly are you using your "quad G5" with "8GB of RAM" for?


      Did you ever stop to think that serious high end workloads might be handled by linux for a reason? Go and tell the big CGI houses that they should dump linux and switch to MAC because it "JUST WORKS", I'm sure they'd love to hear from someone as experienced and knowledgeable as yourself :P


    2. Re:The way it is by pandrijeczko · · Score: 1
      You've made a totally unreasoned comparison.

      Macs are designed for "application orientated" desktop users - if you just want a desktop machine for normal day-to-day usage without worrying about the underlying OS, then a Mac is probably for you. And good luck to you.

      Furthermore, you've obviously not used Linux that much because if you had, you'd be aware of distributions like Gentoo, for example, where package management issues are pretty rare these days with tools like "emerge" - yep, they happen but, even then, as an experienced user, I don't ever recall spending much time sorting those issues out because there are also some good forums to read where someone else has probably experienced the same problem.

      Likewise, most other Linux distros have pretty good package management (YAST on SuSE for example) but can't say more than that because I don't use them.

      So, by all means, enjoy your Mac and stay away from the shell prompt - but please don't then offer opinions on such when it's quite clear that you're badly informed.

      --
      Gentoo Linux - another day, another USE flag.
    3. Re:The way it is by flynns · · Score: 1, Funny

      I couldn't let this thread go more than 3 posts about package management without handwaving and saying, "UBUNTU!!!".

      You may now return to your originally scheduled programming.

      --
      'If you're flammable and have legs, you are never blocking a fire exit.'
    4. Re:The way it is by 99BottlesOfBeerInMyF · · Score: 1

      You've made a totally unreasoned comparison.

      I think the parent poster is looking at this a little wrong, but there is nothing fundamentally flawed in his assertion that application management and installation on the mac has some advantages over Linux. In truth, it has both advantages and disadvantages and I really wish both Apple and Linux maintainers would adopt a little more from one another. I'd love to see a major distro adopt OpenStep and package applications in such a way that they are portable and logical both internally to the package and within user space. The ability to IM an application to someone and know it will work, or install with a drag and drop is a great workstation feature that is underestimated until one becomes accustomed to it.

      At the same time a single interface for installation, un-installation, discovery, downloading, and updates of software is also very powerful and useful. I'd like to see Apple adopt an integrated package manager that provides automated updates for third party software.

      The previous poster may not be the most clueful, nor is it likely they take full advantage of the feature they are touting. Still, they have hit upon an area where Linux distros could use some improvement. I can take an installed application on my mac, drag it to a thumb drive, plug into another mac and run it, without worrying about installation or getting it to work. A year later, I can plug that thumb drive back into the same machine, and it will still have all my preferences set the way I left them. I'd love to be able to do this with my Linux boxes. This is not a useless feature.

    5. Re:The way it is by seb249 · · Score: 1

      Hehehehehe Your right though!!

  50. Re:Sometimes I wish I weren't such a sux programme by QuantumG · · Score: 1

    Seeing as you replied twice, here's my second reply: heard of Qt#? Most Linux distros won't even bundle mono from irrational fears of microsoft anyway.

    --
    How we know is more important than what we know.
  51. Re:Apple Rapidly Losing Its Cool by Jessta · · Score: 1

    http://www.musicpd.org/ is wonderful.

    --
    ...and that is all I have to say about that.
    http://jessta.id.au
  52. One more aspect of evolution: by Seiruu · · Score: 3, Funny

    They haven't failed. They've just found a way that doesn't work and leads to death. All part of the natural consequences of evolution.

  53. Where will their mascot go? by Anonymous Coward · · Score: 1, Funny

    But some are asking, what will happen to the Open Darwin Project's adorable mascot? With the project coming to a close, the outlook for all is bleak.

      Oh! This just in: lovable OpenDarwin mascot Hexley has signed a deal with Diz Nay Studios, and will be starring in a series of cartoon platypus porn films, presumably in order to pay for a much-rumored PPC addiction.
      Our hearts go out to poor Hexley in this dark time.

  54. Re:Apple Rapidly Losing Its Cool by pimpimpim · · Score: 1
    I'd mod this one funny as well if I had mod points :)

    (mplayer fan myself, though)

    --
    molmod.com - computing tips from a molecular modeling
  55. You're mistaken, Apple does release tons of code by LKM · · Score: 5, Informative
    To me open-source means that you have to release the source one way or another, and Apple doesn't release any piece of source code.

    Uhm... You're mistaken. Some of Apple's open-sourced code:

    • Darwin
    • Darwin Streaming Server
    • Bonjour
    • WebKit
    • Compiler Tools
    • HeaderDoc
    • OpenDirectory
    • OpenPlay

    And of course, there's more, in addition to all the other existing open source components which they use and contribute to.

    There's even more which they don't release, and you can like that or not (it's a business decision to them), but you can't claim that they don't release code.

  56. Re:Apple Rapidly Losing Its Cool (use find) by Anonymous Coward · · Score: 0

    The "find" command is more flexible if you're looking to recursively list your mp3 files thay may be in directory hirarchies of varying depth... find . -name "*.mp3" > playlist

  57. Threat of hacking is not a threat, it's fact by chiark · · Score: 1

    The threat of hacking to allow OSX to run on white box computers?

    It's already hacked, and working stunningly well: I've used OSX on a Dell C640 laptop and it's that good that I'll buy a MacBook Pro when it goes Merom. Everything I want is on OSX, and it really does appear that Apple has taken the greatest ideas from OSS and polished them to the point of near perfection.

    Part of me does wonder if Apple doesn't mind people running OSX on unsupported boxes to get them hooked to the point that they go out and buy the apple hardware. I now know many, many people who have done this: dip toes in OSX, find all is wonderful, buy Apple.

    Only bit I don't like is the development environment, as I'm not convinced I want to learn Objective C, but the CARBON APIs may be the way to go there I suppose.

    But back to the point - the white box argument for not opening source doesn't fly IMHO, as OSX is already on vanilla boxes near you right now.

    1. Re:Threat of hacking is not a threat, it's fact by TheRaven64 · · Score: 1
      Only bit I don't like is the development environment, as I'm not convinced I want to learn Objective C, but the CARBON APIs may be the way to go there I suppose.

      Some friendly advice; learn Objective-C and Cocoa. Objective-C is one of the most elegant languages I have used; all of the low-level evil of C when you need it, and most of the abstraction and clarity of Smalltalk. Cocoa is the latest incarnation of the OpenStep specification, one of the most developer-friendly frameworks I have ever used. It was originally designed by NeXT and Sun (based on the older NeXT APIs that Tim Berners-Lee waxed lyrical about) and implemented by NeXT, Sun, and the GNU project. Anything you learn about Cocoa can be directly transferred to GNUstep, allowing you to write cross-platform applications easily on the Mac.

      Carbon, in contrast, is a bastard child of the old MacOS toolkit, which no one likes unless they have a load of legacy code to maintain.

      --
      I am TheRaven on Soylent News
  58. Re:Sometimes I wish I weren't such a sux programme by Anonymous Coward · · Score: 0

    Even though you didn't reply to me...

    > Most Linux distros won't even bundle mono from irrational fears of microsoft anyway.

    novell - check
    opensuse - check
    fedora core - check
    debian - check
    ubuntu - check
    red hat enterprise linux desktop - uh... not yet.
    mandriva - check
    g3nt00 - ch3ck

    so what _is_ this "Most Linux distros" thing you're smoking?

  59. Re:Apple Rapidly Losing Its Cool by kkiller · · Score: 1

    Why not Amarok?

    Not a flame, just curious. I actually prefer it to iTunes...

  60. What a pity by Rorian · · Score: 1

    For the last couple of years, I have stumbled upon OpenDarwin once every 2-3 months and thought I'd really love to install and use it at some point. However, I always looked at the hardware support list and decided it probably wasn't ready.

    But there was always the dream..

    And now it's gone..

    --
    Will program for karma.
  61. Wishful thinking I'm afraid by Anonymous Coward · · Score: 0

    Unfortunately that particular large ape lives on....

  62. Re:Apple Rapidly Losing Its Cool by flynns · · Score: 1

    Neerrrrrrrrrrd. ;)

    --
    'If you're flammable and have legs, you are never blocking a fire exit.'
  63. pkgsrc by LizardKing · · Score: 2, Informative

    The pkgsrc project www.pkgsrc.org supports Mac OS X. The packages it contains are much more up to date than either Fink or DarwinPorts, and can also be used on a number of other Unix like operating systems. I bought a Mac at the beginning of the year, and intended to wipe the disk to install NetBSD. I ended up dual booting it because I found I liked Mac OS X so much, especially when I can use pkgsrc on it.

    1. Re:pkgsrc by TheRaven64 · · Score: 1

      Last time I checked, pkgsrc required a case-sensitive filesystem. This meant that you had to either format your disk as UFS (and lose nice treatment of forks and metadata), make HFS+ case-sensitive (requiring a reformat and re-install, and possibly breaking things) or install it on a disk image (slow). Has this been fixed?

      --
      I am TheRaven on Soylent News
    2. Re:pkgsrc by LizardKing · · Score: 2, Informative

      Yes, it does require a case sensitive filesystem. I have to admit being slightly bemused that Apple had gone down the same braindead route as Microsoft in this respect - having a case aware but case insensitive filesystem. NeXTstep used a "normal" case-sensitive Unix filesystem, so I can't understand why they switched bahaviour instead of adding the extra metadata and fork support to UFS.

    3. Re:pkgsrc by Daniel+Dvorkin · · Score: 1

      Apple had gone down the same braindead route as Microsoft in this respect - having a case aware but case insensitive filesystem. NeXTstep used a "normal" case-sensitive Unix filesystem, so I can't understand why they switched bahaviour instead of adding the extra metadata and fork support to UFS.

      Because doing that would have killed them during the transition from OS 9 to OS X, probably. The entire Mac user base was used to case-insensitivity; making Classic work with UFS was impossible. (No Classic app would have known what to do with a directory containing the files "Foo.txt" and "foo.txt".) Now that they're killing Classic for the Intel transition, they could probably do it, but there will be enough PowerPC machines running Classic apps out there for a while that I doubt Apple will be in any hurry to make the change.

      --
      The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    4. Re:pkgsrc by neersign · · Score: 2, Insightful

      this gets way off topic of the article, but is on the topic of this thread. I have been using computers casually for 12-15 years now, and I gotta say, I have never wanted to save two or more files into a single folder where their name was the same but case was different. I can see some benefit in security, so that you don't mean to run "MySqL" but you get the virus "mysql" instead (just used to prove a point). But, really, who has a need to save files like Foo.txt, FOo.txt, fOO.txt, etc. all in the same directory, and doesn't give them a more descriptive name? But I guess thats just me being a hobbyist and not a professional sys-admin/programmer.

    5. Re:pkgsrc by Daniel+Dvorkin · · Score: 1

      Actually, I tend to agree with you; when I'm working in a case-sensitive file system, I still never have files named "Foo.txt" and "foo.txt". (Of course, this may be simply force of habit, since I move around between OS X, Linux, and Solaris all the time; it's just safer if I don't do things on one platform that will mess me up on another.) OTOH, as a programmer, I do find it useful sometimes to have variables named "X" and "x" -- since most of what I do these days is statistical programming, it's useful to follow the convention that "X" is a random variable and "x" is an observation, i.e. a fixed value; I also tend to capitalize the names of vectors since there's no way to represent boldface in ASCII. ;) On the occasions when I'm forced to use SAS (the Windows of the stat world!) its case-insensitivity drives me nuts.

      So by extension, I can imagine programming conventions where it would be useful -- e.g., suppose you always capitalize class names, so "Foo.cpp" contains the class definition for class Foo, while "foo.cpp" contains functions which operate on objects of class Foo but which, for whatever reason, don't belong inside the class. I'm not saying this is a good idea, mind, but it could happen.

      --
      The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    6. Re:pkgsrc by Anonymous Coward · · Score: 1, Insightful
      >I have to admit being slightly bemused that Apple had gone down the same braindead route as Microsoft in this respect - having a case aware but case insensitive filesystem.


      Maybe Apple did this because 99.9% of the people in the world have found that case sensitive filesystems cause more confusion than they're worth? Just guessing.


      My favorite quote is from Philip Greenspun: The great case-sensitivity winter descended upon humankind in 1970 with the Unix operating system.

    7. Re:pkgsrc by Durandal64 · · Score: 1

      Case-insensitivity was a holdover from the Classic Mac OS. But HFS-X is case-sensitive and has additional metadata features. (UFS on OS X really, really blows. No one wants to use it.) I run HFS-X on my machines personally, and for the most part it works okay. But it does break some stuff. For example, Adobe Photoshop crashes when run from a case-sensitive volume. That's just lazy development. Dashboard widgets are also particularly bad. But the file system itself is pretty rock-solid. It's just stupid and/or lazy developers that fuck things up.

    8. Re:pkgsrc by archen · · Score: 1

      I've tried all three systems (and I'm somewhat familiar with source systems as I'm and avid FreeBSD user, and usee Gentoo as well). Tried Fink but couldn't get it to work. Tried drawinports but had some problems - can't recall what they were. Tried Fink again, couldn't get it to work. I then tried pkgsrc. I was "fortunate" because I formated using UFS, although I now know that performance sucks using UFS on a mac so I now use case sensitive HFS. Anyway pkgsrc has a lot of packages to be sure, and 50% of them don't compile on my G3 & G4. I hung in there for quite a while, figuring it would be a good system to know so I could get into DragonFly BSD but it just got fustrating. Tried Fink again, but rdesktop wasn't in the stable section. Eventually I went back to darwinports.

      Darwinports may not have the most, or the most up-to-date packages out there. But they usually work, and seriously I'm just happy to even get that now. Darwinports is ungodly messy, and occasionally a compile can completely hang with no explanations but out of the three systems it will be the one I'm using for a while - and I breathe a sigh of releif to know that it's only opendarwin closing shop.

    9. Re:pkgsrc by LizardKing · · Score: 1

      I never knew about HFS-X. I'll consider converting my Mac over to it seeing as I don't use Photoshop or Dashboard widgets.

    10. Re:pkgsrc by mstone · · Score: 2, Insightful

      Yeah.. how silly of them to make software that matches human behavior.

      Why can't we have filesystems that are character-encoding sensitive? Foo.txt{ASCII} and Foo.txt{Unicode} are clearly different at the data representation level, so why can't filesystems recognize that simple, obvious fact?

      Heck, while we're at it, let's add font-sensitivity: I want my Foo.txt{Arial} to be distinct from my Foo.txt{Helvetica}. Then we can throw in attribute-sensitivity, so Foo.txt{Unicode, Garamond, bold, oblique, second 'o' red} is the truly unique identifier it was intended to be.

    11. Re:pkgsrc by Chazmyrr · · Score: 1

      This is what we call a PEBKAC problem. Problem Exists Between Keyboard and Chair. The developers wrote the code before the case-sensitive file system was released. The code therefore doesn't support the case-sensitive file system. Adobe tells you to install the software on a case-insensitive volume. http://www.adobe.com/support/techdocs/326193.html. So the real problem is that the user is too stupid and/or lazy to follow directions.

      Don't like hearing that do ya? Maybe next time you can avoid calling people stupid when they didn't anticipate everything you could possibly do to fuck up the software they've written.

    12. Re:pkgsrc by Flagran · · Score: 1

      Foo.txt {ASCII} == Foo.txt {UTF-8}

      --
      Make love, not sigs
    13. Re:pkgsrc by IpalindromeI · · Score: 1

      One argument that I've seen against case insensitivity is that it is not very well defined. Especially with Unicode and other languages thrown in, mapping a letter to its upper/lowercase equivalent might not be so straightforward. Better to just making everything distinct that have users lose data because the filesystem author couldn't get it exactly right.

      I don't necessarily agree with that argument, it's just one that I've seen that seemed to have some weight to it. I'm sure it can be worked out with some decent forethought, especially if that work went into a library that others could then reuse.

      --

      --
      Promoting critical thinking since 1994.
    14. Re:pkgsrc by LizardKing · · Score: 1

      Maybe next time you can avoid calling people stupid when they didn't anticipate everything you could possibly do to fuck up the software they've written.

      With an attitude like that I've got to ask, can my company hire you for our technical support department?

    15. Re:pkgsrc by Retype · · Score: 1
      Foo.txt {ASCII} == Foo.txt {UTF-8}

      UTF-8 != UNICODE
      --

      I have no sig and I want to scream
    16. Re:pkgsrc by QuantumFTL · · Score: 1

      That's gotta be one of the most helpful responses I've ever received on slashdot, I don't know why I've never even heard of them - probably because most of the people I work with use Fink. Thanks!

    17. Re:pkgsrc by Durandal64 · · Score: 0, Troll
      Don't like hearing that do ya? Maybe next time you can avoid calling people stupid when they didn't anticipate everything you could possibly do to fuck up the software they've written.
      Hey fuck-stick, it doesn't take some sort of special effort to support a case-sensitive volume. There are plenty of apps out there written on case-insensitive volumes that run just fine on case-sensitive ones. All it takes using the correct paths and being consistent. If you refer to the path "/This/is/a/path" with the string "/this/Is/A/Path", you're doing it wrong, period, regardless of what your target filesystem is. Know why? Because those two aren't the same fucking string. It's not a question of whether or not you're being an idiot (you are); it's a question of whether the system is going to punish you for it. This is not a difficult concept to grasp, and yes it is developer laziness.

      Saying, "Install it on a case-insensitive volume" is a stupid solution because it could involve reformatting your existing volume. They couldn't even give a decent workaround: creating a disk image with a case-insensitive file system.
  64. Sad to see the open source version leaving....... by Anonymous Coward · · Score: 0

    This is really a shame. Great projects such as ncutil were built for darwin and are very useful within an OS X environment.

    Sun really has the right idea, with an open source operating system. Darwin should stay open source; open source is a great idea.

    A partition has been setup for people to beg for the open darwin project to be kept alive. I am signing!

    Any one else fell like groveling?

  65. Re:Sometimes I wish I weren't such a sux programme by jcr · · Score: 4, Insightful

    Qt is internally a work of art

    This is precisely why GNUStep gets no traction: the Linux crowd actually believes that a cross-platform abortion like Qt is acceptable. Of course, this isn't surprising for a community that still hasn't admitted to itself what an abomination X11 is.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  66. Re:Sometimes I wish I weren't such a sux programme by LizardKing · · Score: 2, Insightful

    Qt, a toolkit written in a language that Trolltech finds so deficient that they extended it, a language that has such a baroque library that Trolltech wrote their own. As for Glib and GTK+, I have been through a fair bit of the code, and it is a work of art. I'm not saying that the Qt code isn't a work of art, but your criticism of Glib/GTK+ is bullshit.

  67. Not surprised. by alphasubzero949 · · Score: 3, Insightful

    If anyone had been keeping up with Rob Braun's musings about Open Darwin and Apple's behavior with the OS community, this decision was simply not a matter of 'if' but 'when.' The following links below illustrate that this wasn't a spur-of-the-moment decision but rather the final straw:

    A Brief History of Apple's Open Source Efforts
    WebKit and Apple's Open Source Efforts

    Those are just for starters. And to top it all off where Braun gets to the meat of the matter:

    Why Darwin Failed

    It doesn't take a degree in rocket science to figure out that the holdouts on the Darwin project have finally had it with Apple.

    In a nutshell: Apple have never let anyone touch their code which is a twisted beige box-grade edition of FreeBSD. If something burps no one can help outside of Cupertino. Worse, Apple deliberately makes it nearly impossible to report bugs and allow for patches to be made. This extension of Jobs' secrecy policy is why some holes remain wide open while the rest of the *nix world have patched them a long time ago.

    With OpenDarwin shutting down not too long after Apple closed down OSx86, Apple execs selling Apple shares all over the place, and the exodus of two former NeXT gurus, it isn't hard to see what path Apple and OS X are heading down.

    Go ahead and mod me as a troll for preaching against the Gospel of Steve, but if key players both at Apple and in the developer community do not believe in OS X (or are giving up on it entirely), how can the rest of us do so?

    1. Re:Not surprised. by plaidhacker · · Score: 1
      With OpenDarwin shutting down not too long after Apple closed down OSx86, Apple execs selling Apple shares all over the place, and the exodus of two former NeXT gurus, it isn't hard to see what path Apple and OS X are heading down.

      While the rest of your post is informative, you deserve a troll mod for your last comment. No one wants to see good people leave, but their departure will hardly affect MacOS as a platform. Execs selling stock might be a sign that they feel the price is inflated, but its hardly the end of a company. I know that people don't expect intelligent debate in Slashdot articles, but you would sound more intelligent and respectable if you didn't include the wild speculation at the end of your post. People have been forecasting the end of Apple for thirty years, and they all look stupid when nothing happens.

      Instead concentrate on the points of improvement:

      • Apple needs to focus their product. No one wants to pay for BSD, and Apple shouldn't be funding a proprietary fork. This needs to be an Open Source collaboration.
      • They also need to manage the underlying OS differently than products. Steve's desire for secrecy interferes with the Open Source community.
      • Over time, more APIs will have to go Open Source as they become commodities that people aren't going to pay for.

      But lets not forget that Apple is a company, and they are responsible for every line of code in their product. It should be obvious why they won't simply accept every patch that gets sent their way. Sure, a number of companies are experimenting with this, but it isn't an accepted business practice quite yet. From a customer point of view, its okay if their Debian installation gets updates every day, and is sometimes broken, and sometimes changes drastically. None of these are acceptible to MacOS users. The other side of the coin is RedHat, who spends a lot of time validating the software quality of thousands of packages. Apple just doesn't have the time for this. On top of these, they have some self-serving interests, such as resticting code from running on beige boxes. No one likes that, but its key to their current business plan.

      Apple's open source projects can't be viewed from the perspective of traditional open sourcers. Linux/GNU users have a certain set of expectations that are fundamentally different from Windows/Mac users. Open Source code from Apple is not the improvement playground of Linux, but a utilitarian structure that is only changed when necessary, and only by Apple. Its the same as any corporation that uses open source - they find a system that works and freeze a snapshot. I'm not sure how you build a community in that environment, but I can be certain that Apple is the tip of an enormous corporate-opensource iceberg, and learning to integreate the two cultures will be fundamentally more important than helping a single computer company.

    2. Re:Not surprised. by GaryPatterson · · Score: 1

      That's absolutely not an insightful post. A bunch of poorly-thought theories does not constitute reality.

      To attack your points: Are Apple about to close their doors? There's absolutely no sign of this, but apparently execs selling shares is your indication. Well, this happens in all companies. A quick Google search turns up a story on Google execs selling shares back in Nov-2004. That didn't indicate Google was failing then, and neither does Apple execs selling shares indicate Apple is failing now. You actually need some evidence for that. Got any?

      Apple closed OSx86? As far as I can see, the Darwin x86 source is available (http://www.opensource.apple.com/darwinsource/). Is that what you mean? Can you be more specific as to what you allege Apple did?

      Your post *deserves* to be modded down. Not because you're out there speaking the truth and people just don't want to hear it, but because it's completely biased, has no insight and attempts to cobble together a conspiracy theory out of smoke and air.

  68. Re:Sometimes I wish I weren't such a sux programme by Whiney+Mac+Fanboy · · Score: 1

    This is precisely why GNUStep gets no traction: the Linux crowd actually believes that a cross-platform abortion like Qt is acceptable. Of course, this isn't surprising for a community that still hasn't admitted to itself what an abomination X11 is.

    *snort* - and people say that members of the linux community are rude!

    --
    There are shills on slashdot. Apparently, I'm one of them.
  69. Re:Apple Rapidly Losing Its Cool by cortana · · Score: 1

    In addition to the use of find(1) suggested by another poster, you can also eliminate your use of a temporary file:

    find -name '*.mp3' | mplayer -shuffle -playlist -

  70. Re:Apple Rapidly Losing Its Cool by Builder · · Score: 1

    I'm not sure I can take an article seriously when the author does not know the difference between then and than.

  71. Late to the party by Jaxoreth · · Score: 1
    And even now look at xcompmgr with transett or compiz - they just basically fashion themselves after inbuilt mac effects or 3rd party add ins that have existed for awhile under OSX.

    Look at OS X's memory protection, demand-paging, preemptive multitasking, and GNU toolchain, present in other systems for decades before Apple got around to adopting them. And Apple didn't even write it themselves; they had to buy from a third party.

    The point being, who cares? Basically you're saying that coming late to the party is unfashionable. I don't give a rat's ass about that, and neither do you -- or you would share the complaint I feigned above.

    On top of that mac make computers end users like and OSX Just Works(tm) which for a Linux user is really handy some days when Debian sid decides it wants to blow the heads off all the toys.

    Cute Toy Story reference, but sid == unstable and is meant for Debian developers only. I use testing (etch) and haven't had the sort of drama you allude to, which I can't say of OS X.

    (By the way, your saying "mac make computers" instead of "Apple makes computers" makes me suspicious of your Mac experience.)

    It also interconnects flawlessly with my other Linux boxes through ssh, samba, nfs, vnc and everything I need (I use Fink for random unix tools I need).

    Okay, my turn to call bullshit. From Terminal, ssh to a Debian box and run nano on a file at least several screens long, and page down. It doesn't update correctly. Manually setting TERM=vt100 works around this, but that's not "interconnecting flawlessly" in my book. Where's sshfs? Where's svn?

    So really outside the RM ethos of everything should be open (to which, hypocritically in context of the above, I subscribe) there isn't really much reason for a mac user to smarten up and switch, try maybe, to Linux

    Bingo. Nail, meet hammer. I demand an open system, and that is why I'm switching.

    --
    In general, it is safe and legal to kill your children. -- POSIX Programmer's Guide
    1. Re:Late to the party by argent · · Score: 1

      From Terminal, ssh to a Debian box and run nano on a file at least several screens long, and page down. It doesn't update correctly.

      What's $TERM set to on your Debian box when it's misbehaving?

      If it's set to something that's got a correct terminfo entry on your Debian box, and nano doesn't update correctly, that *might* be nano's fault, or it *might* be Apple's fault.

      If it's set to something that doesn't have a correct terminfo entry, it *might* be Debian's fault, it *might* be OpenSSH's fault, or it *might* be Apple's fault.

      If you can fix it by changing $TERM, odds are it's *not* Apple's fault.

      Here's an analogy:

      If you're using Firefox and you go to a website that doesn't display correctly, do you blame Firefox or the website? Or do you check to see if the website's doing something weird? If you can fix it by changing the browser string to MSIE, do you blame Firefox?

      Personally, I consider people who blame Firefox when the website's doing the wrong thing with the browser string lusers.

      I demand an open system

      An open system is a matter of following publicly defined interfaces and protocols, it's got nothing to do with the source or whether it's bug-for-bug identical to some other open system. In many ways, OSX is more of a traditionally "Open" system than Linux.

  72. Etoile by Elektroschock · · Score: 1

    > There just was no need for OpenDarwin without Aqua.

    Is it possible to run Darwin with Etoile / Gnustep? I think so.

    I mean, if aqua misses why not recreate it.

    And sure, you could run KDE on Darwin, so what's the problem?

  73. Thanks by theolein · · Score: 1

    I also am a bit dissapointed with fink, and am considering moving to Darwin ports. I was worried that it too would dissappear and am now relieved.

    Thanks.

  74. Re:Sometimes I wish I weren't such a sux programme by grahamlee · · Score: 1

    GNUstep is binary compatible with Cocoa, as long as you're on Mac OS X then you can configure GNUstep with the apple-apple-apple library combo and it'll build against the Cocoa.framework. GNUstep is also to a large extent source code compatible with Cocoa on other platforms, not surprising really as OpenStep was the original "write once, run everywhere" platform a couple of years before Java hit. If you want to run Mac OS X binaries on a non-Mac platform you've got a bit more work ahead of you, but take a look at NetBSD's COMPAT_DARWIN as a good starting point.

  75. Leopard on Linux? by bill_mcgonigle · · Score: 1

    though not Free Software because it doesnt' seem to like GPL stuff much, like many corporations

    Let's see what happens at WWDC. The writing's on the wall about Mach at Apple - it's slow and Avie left. Apple is keeping xnu for x86 secret and dropping weird hints about waiting and seeing.

    So, Apple has to pick a new kernel. The allure of the NT kernel is hard to argue against (and others have given good arguments for it), given driver support, on a practical basis, but Apple has to realize getting into bed with Microsoft never benefits any company in the long term. So, what else is there?

    Open Solaris? Not bad, but Sun is running it. BSD? Probably easiest to shoehorn in but not likely to be featureful enough for Apple. Linux? It has the momentum, the clout among the geeks, IT, and even Wall Street to a certain extent, and has all the features Apple wants, plus forkability. It's where Apple's former Alpha Geeks have gone.

    The GPL is still something Apple doesn't embrace fully, but they managed to swallow their pride with WebKit and it's worked out well, so perhaps they've warmed. Let's just say I won't be surprised to see a version of linux running launchd with an IOKit layer at WWDC.

    My next laptop is going to be a linux machine; I'm just not sure yet if it will be a Mac.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    1. Re:Leopard on Linux? by Frumious+Wombat · · Score: 1

      Given Sun's current financial state, 64-bit on AMD/Intel Solaris-x86, and technologies such as Java, it could easily be eaten by apple. Paying the premium to ship SnApples without having to deal with the screaming hordes of Linux geeks may be worth it for a company as tightly-wound and controlled as Apple. I doubt they want any confusion in people's minds over whether Aqua is their own, or just a shell on top of Gnome. In the end, does it matter, since they entire point of the Apple experience is in the UI and higher-level libs, which aren't open, and aren't about to become so. On the other hand, I, for one, welcome our new Efficient, Poly-cored, Multi-threaded, Preemptively Multitasking Overlords.

      --
      the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
    2. Re:Leopard on Linux? by Trillan · · Score: 1

      Isn't WebKit LGPL? *checks* Yes, it is. Apple's never had much of a problem with LGPL. Not surprisingly, they don't want to give away every line of source code they have.

    3. Re:Leopard on Linux? by bill_mcgonigle · · Score: 1

      Given Sun's current financial state, 64-bit on AMD/Intel Solaris-x86, and technologies such as Java, it could easily be eaten by apple.

      Interesting thought. It wasn't too long ago that Sun was trying to acquire Apple. Apple has grown cold towards Java, at least with regards to Cocoa, yet WebObjects relies on it. It does have enterprise caché though which Apple needs (but doesn't seem to want). Sun servers are also pure Enterprise, and Apple is a good Sun customer, with OpenStep having run on SPARC back in The Day.

      Would Apple 'get' the Enterprise with such an acquisition or would it divvy up Sun with Intel, perhaps?

      I doubt they want any confusion in people's minds over whether Aqua is their own, or just a shell on top of Gnome.

      Perhaps I wasn't clear - I was talking about the Linux kernel replacing the Mach/xnu, not any part of OSX. I wouldn't expect Apple to replace any other part of OSX. Neither GNOME nor even X would be in the picture.

      In the end, does it matter, since they entire point of the Apple experience is in the UI and higher-level libs, which aren't open, and aren't about to become so.

      Right - only developers should notice the change, and fewer developers than some might expect, because things are well abstracted. Where it could matter are for things like hardware support from vendors and "hard" problems (e.g. virtualization in Xen) which Apple could pick up for free. Some of this depends on if Apple is going to free OSX to run on generic hardware and also where they want to compete.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    4. Re:Leopard on Linux? by bill_mcgonigle · · Score: 1

      Not surprisingly, they don't want to give away every line of source code they have.

      What do you mean? Shipping a linux kernel wouldn't require them to give away all their source code, only kernel modifications. Which they do already (at least on PPC).

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    5. Re:Leopard on Linux? by QuantumFTL · · Score: 1

      I for one hope we see a Solaris kernel in Leopard, if nothing else for ZFS support, but having better kernel tracing and swapping routines would be nice as well.

    6. Re:Leopard on Linux? by Anonymous Coward · · Score: 0

      Let's see what happens at WWDC. The writing's on the wall about Mach at Apple - it's slow and Avie left. Apple is keeping xnu for x86 secret and dropping weird hints about waiting and seeing.

      While I'd love to see them drop all of the slow parts of Mach to really speed up Leopard, it ain't gonna be replaced with Linux. No way no how. If anything, it'll more closely resemble FreeBSD underneath. And isn't FBSD still the performance king on x86?

    7. Re:Leopard on Linux? by Trillan · · Score: 1

      See the GPL FAQ, but in a word, no.

    8. Re:Leopard on Linux? by bill_mcgonigle · · Score: 1

      See the GPL FAQ, but in a word, no.

      That's funny - I was going to suggest the same to you. :) This is the "mere aggregation" debate.

      The case of Apple's proprietary layer, say Aqua, Cocoa, and the applications, are levels above the kernel, accessing kernel-mediated resources through well-defined abstracted interfaces. The IOKit, Frameworks, etc., are all BSD licensed already - if anything, they would have to be relicensed under the GPL.

      Just look at the Open Darwin project - a system running on the Apple kernel, IOKit, Frameworks, etc, with an X11 display system and no Cocoa or Carbon or Rosetta in sight. If that's not evidence that Mach/xnu and Aqua, et. al. are separate programs I don't know what is. So, running on a different kernel, the separation wouldn't change. If these aren't separate programs, things like Apache running on Linux have serious license issues as do other proprietary applications which run on linux systems. But I think those issues are settled.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    9. Re:Leopard on Linux? by Trillan · · Score: 1

      Unless they go through the stdlib exception, yes they do. I don't think many people have fully realized exactly how restricting GPLv2 is. I'm hoping GPLv3 will be more reasonable, or at least better spelled out. In the meantime, how do you propose integrating non-GPL code with GPL code under the user level?

    10. Re:Leopard on Linux? by bill_mcgonigle · · Score: 1

      In the meantime, how do you propose integrating non-GPL code with GPL code under the user level?

      What kernel linking is done at the user level? Or are you suggesting that making system calls to the kernel is enough to trigger GPL compliance? That would mean proprietary software running on linux is impossible, yet there are plenty such vendors and nobody is raising the appropriate stink about them.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    11. Re:Leopard on Linux? by Trillan · · Score: 1

      There is an exception for software that runs through the Standard Library, which covers most user-space applications. My concern is that accessing the kernel without the Standard Library is a GPL violation. Any thoughts?

    12. Re:Leopard on Linux? by bill_mcgonigle · · Score: 1
      My concern is that accessing the kernel without the Standard Library is a GPL violation. Any thoughts?

      So, if a proprietary application calls open() rather than fopen() it's in violation? I imagine nearly all the proprietary apps on the market call open().

      From the GPL FAQ:
      If the two programs remain well separated, like the compiler and the kernel, or like an editor and a shell, then you can treat them as two separate programs--but you have to do it properly.
      They fail to define 'properly' but they give the example of an app calling the kernel and declare it kosher.

      Wikipedia says not all linux distros use the GNU Standard Library though I'm not sure which ones don't (embedded maybe?). It would be interesting to see how any of those have solved this problem, and if they have.
      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  76. Why Fink and Darwinports? by Anonymous Coward · · Score: 0
    Back in 2000 and 2001, it was difficult to build OSS on OS X because it was essentially a timewarped NeXT from like 1989. Things have improved since then. You don't need packages or portages. Just type:
    ./configure
    make
    sudo make install
    1. Re:Why Fink and Darwinports? by mh101 · · Score: 1

      Dependencies.

      Would you rather simply tell Fink you want Gnucash and it does everything for you, or would you rather try to figure out and install all the dozens of dependancies yourself?

      Just like the difference between Linux From Scratch and Gentoo.

      --
      Duct tape is like the Force. It has a light side, a dark side, and it holds the universe together.
  77. So what? OSX = platform for SSH. by Anonymous Coward · · Score: 0

    I use OSX daily.... to ssh into linux and bsd boxes where all my real work happens,
    and will continue to do so as long as ssh doesn't break.

    The day Apple fucks things up so I can't ssh will be the day you find my box on Craigslist.

  78. What do you expect Apple to do? by argent · · Score: 1

    "the tiny bit of code sharing they have done."

    When you see reactions like this from the open source community it's no wonder Apple's gotten a mite miserly over recent months. Back when Rhapsody was first brought to the table Apple wasn't planning on even shipping the "BSD subsystem" beyond what was absolutely necessary to run the OS. I'm not talking about source code here, I'm talking about binaries. You were going to have to download your awk and sed and vi and grep and maybe even eventually the shell from Apple IF you wanted it. UNIX hackers the world over, inside and outside Apple, responded in shock... and someone managed to convince the Steve to tear down the wall.

    From their point of view they've bent over backwards, going far beyond the requirements of the FOSS licenses on the software they've used. What have they gotten in return? They've got slander, libel, words you never heard in the Bible. They responded to the complaints about Safari by setting up a new repository for Webkit. They've released a whole boatload of packages that were completely developed inside NeXT and Apple, including netinfo, HFS, launchd, ... you can cavil about the usefulness of these packages if you like, but if Microsoft had released one percent of their comparable code it'd be a miracle. Hell, Microsoft's gotten proportionally more milage out of a smidgen of effort.

    Can you download the source to Microsoft's HTML control (based on NCSA Mosaic), NTFS, or even Microsoft's BSD-based software like the Interix and TCP userland? No. Yet even with the tiny crack of support for Open Source that Interix and the carefully selected open source honeypots^Wreleases at Sourceforge represent Microsoft's gotten tremendous traction. Even the FSF backed down on killing GCC on Interix (even as they knocked back Dave Korn and U/WIN!).

    It seems like the best way to get good press from the open source community is to be a bastard. It doesn't pay to be the nice guy.

    Sun got the same message, didn't they? Open up Java a bit too much, Microsoft turns it into a honeypot. Pull back, you get slapped, and the FOSS community jumps aboard the dotnet bandwagon with Mono. They're probably saying "thank god we never Open Sourced NeWS...".

    1. Re:What do you expect Apple to do? by evilviper · · Score: 1
      You were going to have to download your awk and sed and vi and grep and maybe even eventually the shell from Apple IF you wanted it.

      You act like I should be upset by this. If they want to cripple their own OS, it's not my problem. They've gotten tremendous mileage out of their Unix base, it's not as if we should be grateful to them for their "charity".

      From their point of view they've bent over backwards, going far beyond the requirements of the FOSS licenses on the software they've used.

      No, most of the time they're just barely within the terms of the licenses. It's taken this "slander" as you call it to get them to contribute back in any useful form (not globs of code interdependant on unavailable propritary code).

      you can cavil about the usefulness of these packages if you like,

      Yes I can.

      but if Microsoft had released one percent of their comparable code it'd be a miracle.

      Microsoft's OS is all propritary. It wasn't ever copied wholesale from an Open Source project. And, as I've said, Microsoft isn't touting themselves as a good OSS supporter... Apple is.

      Hell, Microsoft's gotten proportionally more milage out of a smidgen of effort.

      Mileage? Nobody thinks of Microsoft as supporters of OSS. Sure, their code gets used more widely, because they have more users, plain and simple.

      Open up Java a bit too much, Microsoft turns it into a honeypot.

      Java was never open, and Microsoft was forced to pay Sun for violating their contract. Making Java more open (or closed) wouldn't have helped one bit.

      and the FOSS community jumps aboard the dotnet bandwagon with Mono.

      Java is just as popular as it ever was with OSS, which is to say, not very popular. Just because a handful of people are developing Mono doesn't change things one bit. Practically nobody is actually using it, anyhow.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    2. Re:What do you expect Apple to do? by argent · · Score: 1

      No, most of the time they're just barely within the terms of the licenses.

      The GPL simply requires that they make the source available for a nominal charge, not that they provide a free and continually updated repository.

      The BSDL simply requires that they retain the copyright intact, and yet they are *still* providing updates for most of their BSD licensed source.

      Neither the BSDL nor the GPL, not any of the other open source licenses, require that they release their own code as open source.

      Calling Apple's open source releases "barely within the terms of the license" is ludicrous. If you're actually competant to comment on this subject, then you're making stuff up. If you knoestly believe this, then you can't have so much as looked at what Apple's actually released.

      Microsoft's OS is all propritary. It wasn't ever copied wholesale from an Open Source project.

      I was one of the 386BSD "patchkit" era developers back before it became FreeBSD, and I'm 100% in agreement with McKusick and the rest of the *original* BSD team in supporting anyone's right to use it and release as much or as little of it as they want. Whether that's Microsoft (who've used an awful lot of BSD code over the years), Apple, Network Appliance, IBM, HP, or Sun. If the people who wrote the code and worked on the code don't have a problem with it, who the hell are you to complain?

      Oh, right, you're the guy who thinks Apple's just been minimally complying with their OSS licenses.

      And, as I've said, Microsoft isn't touting themselves as a good OSS supporter.

      So what? I care about what they do, not what they say.

      Java is just as popular as it ever was with OSS, which is to say, not very popular.

      Dear god, I wish that was true. I've got weeks of my life I'd love to have back that have been wasted on dealing with projects like Tomcat.

  79. case sensitivity by ChristTrekker · · Score: 1

    Case-sensitive filesystems are stupid. If you tell someone "go bring up the 'college' document" do you think they hear any case-sensitivity? If they see "college", "College", or "COLLEGE", don't you think they'll assume they found the right one? How would he know you said "college" and not "COLLEGE" - they sound the same to me!

    Case-preserving non-case-sensitive filesystems are absolutely the right way to go for any consumer-targeted OS. Only (some) geeks would say otherwise. If you're relying on case to differentiate files, may I suggest that you choose better names?!

    1. Re:case sensitivity by LizardKing · · Score: 0, Flamebait

      There are ways to optimise it, but case insensitive filesystems make many operations more complex. For instance, searching a file heirarchy for files name "foo*". In a case sensitive filesystem I can ignore anything started with the letter "F" without considering any other letters. In a case insensitive but case aware filesystem I can't hash the filenames (expensive in itself and only beneficial if performing whole name matches), or store two versions of the filename - the display variant preserving case, and a second one that adopts a consistent convention of either uppercasing or lowercasing the name for fast operations.

      So from an implementation perspective case aware but case insensitive filesystems chug cock.

    2. Re:case sensitivity by ChristTrekker · · Score: 2, Insightful

      Well, you can optimize for hardware/software, or you can optimize for users. Users' tolerance for working in ways constrained by system limitations is diminishing - they expect the computer to work the way that is intuitive to them. We've got about a million times the power of computers 20 years ago. I think it's pretty obvious that the user argument is going to win here.

    3. Re:case sensitivity by askreet · · Score: 1

      I'm a geek and I think case-sensitivity is useless. Do you really have any directories with foo.txt and Foo.txt? It only makes things confusing.

    4. Re:case sensitivity by _Swank · · Score: 2, Insightful

      with the appropriate implementation, a case aware but case insensitive file system is essentially equivalent to a filesystem allowing only lowercase characters (but allowing for a display name including mixed case). this makes most of your issues go away (most operations just need to canonicalize the input filenames to the lowercase equivalent and then perform the operation as if the filesystem were case sensitive) completely as well as fixing a normal user searching for "foo*" as they may or may not remember exactly if the document is really "Foo*" or "fOo*" or some other variant. the only issue left is if the user really does want a case sensitive search for "foo*" as they know they have a lot of documents that are "Foo*" or "foo*" but only want the latter. this really isn't nearly as common as the first instance and should not be the case the system is optimized for.

      when designing for a user, very very rarely (never) should you make something harder for the user but easier for the programmer. as many have already pointed out, most users really want case aware case insensitive filesystems.

    5. Re:case sensitivity by LizardKing · · Score: 1

      as many have already pointed out, most users really want case aware case insensitive filesystems.

      Pointers to studies to back that up please. In my experience, the user gets very upset when "foo" is the same as "Foo" or "fOo" or "foO".

  80. MOD PARENT UP? by argent · · Score: 1

    Leopard will be Universal (i.e., won't have two trees like 10.4.x does)

    Interesting, and Informative. That's worth +2 at least. :)

  81. Who cares about Yet Another Gnome Platform? by argent · · Score: 1

    it seems to be more of a full system (with GNOME and WindowMaker)

    Now if they were going ahead and building on GNUstep, I'd be interested. But sticking Windowmaker on top of yet another Gnome clone isn't very interesting.

  82. Why do I want to run Win32 on Linux? by argent · · Score: 1

    what Mac apps would you want to run on Linux that you can't find a windows version to run on Wine or some windows emulator.

    Running apps under Wine is about as insecure as running apps on Windows, because it's the Win32 subsystem and all the COM-derived code like ActiveX that are the source of Windows security woes. All you're doing by running Win32 on a Linux kernel instead of an NT kernel is bringing all the things that make Windows suck so badly over to the UNIX world, in a less convenient and lower performance package. You're better off just using VMware or dual-booting.

    OS X apps, on the other hand, are UNIX native at the lowest level, and even ports of Windows apps to OS X generally benefit from that. On Linux or a non-Mach-infected BSD they'd likely run *faster* than on OSX.

  83. How long till OpenSolaris goes the same way? by whoopi_cat · · Score: 2, Interesting

    I say they'll muddle on for another year.

  84. Mod Parent UP! n/t by sgtrock · · Score: 1

    blah.

  85. Such a cynic (me too) by argent · · Score: 1

    Well, basically, it's like this: the people who know enough to work on it are, for the most part just using Mac OS X, and most of the Linux crowd can't really tell the difference between GNUStep and Gnome (ie, they actually believe Gnome is good enough).

    God, you're such a cynical bastard. Alas, I agree with you 100%.

  86. Neither C nor C++ for GUI work, thanks... by argent · · Score: 2, Funny

    C is syntactically and semantically poorly suited to object oriented programming, and it doesn't matter how much radioactive spider venom you pump into it it's never going to start swinging from building to building like some comic-book super hero. Even wrapping a powered exoskeleton around it is iffy, but at least there's some realistic hope that you can implement something that'll make the transition from the funny pages to the front page that way.

    C++, of course, is the spider-man standin, and Objective C is our metaphorical iron man. I'd rather program in Javascript than either of them... at least Javascript is built around the object model from the start in a way that even Java (the "new spider man") hasn't managed.

    What we really need is to for someone rip the dregs of Xerox PARC's ugly-sister user interface out of Smalltalk or Squeak and just use Objective C as a bridge to an open-source programming language that doesn't suck, but alas the Smalltalk crowd's got this horrible baby-duck fixation on the worst parts of the platform...

    1. Re:Neither C nor C++ for GUI work, thanks... by SteeldrivingJon · · Score: 2, Funny


      "C++, of course, is the spider-man standin, and Objective C is our metaphorical iron man. "

      I think that's backwards. Objective-C is C that was injected with radioactive serum which effected a deep change in original language's existence and modus operandi.

      C++, on the other hand, is like Iron Man (or even the bulkier Iron Man armor-based War Machine armor with attached gatling gun and rocket launchers), a highly complex, difficult to maintain technology that has many different versions, yet which essentially wraps around a still-flawed core with a bad heart and a booze problem. And a stack of C++ reference books is analogous to the briefcase Tony Stark had to carry around with him all the time to hold the armor.

      Whereas Tony Stark is forever tinkering with his armor, charging it, improving it, tuning it, trying to fix bugs, and maintaining it, the radioactive spider venom "just works".

      --
      September 2011: Looking for Cocoa/iOS work in Boston area Cocoa Programmer Quincy, MA
  87. Re:So what? OSX = platform for SSH. by slyborg · · Score: 2, Insightful

    Even for an AC, this gets my vote for dumbest post of the week. Both OT and inane, and extra credit for throwing in Craigslist. Well done!

  88. Misguided by porkface · · Score: 1
    Too bad their dreams did not work out, but frankly, they will not be missed.

    Their dreams being that they would create an open source project, and everybody else would do the work for them.
  89. Did they? by 2nd+Post! · · Score: 1

    They have contributed patches and fixes to GCC, they have released their WebKit, based on KHTML, as open source which was recently adopted by Nokia for their web browser, and they host the source for several of their own in house projects, such as Bonjour, Darwin (though out of date), Quicktime/Darwin Streaming Server, and others.

    So they have full time developers working on open source projects (GCC), release their own source, and contribute to existing projects. Are you just pissed that Apple hasn't adopted Linux and moved it forward?

  90. Re:Bug Reporting by Anonymous Coward · · Score: 1, Informative
  91. How to spell "Mac OS X" by rgovostes · · Score: 1

    Sorry to nitpick, and I realize that this isn't contributing much to the discussion, but for the record it's "Mac OS X" written just like that, with the capital letters and spaces as written. It's usually abbreviated to "OS X" but never MAC or OSX.

    I believe part of the confusion over this is that it used to say "MacOS 8" on the startup screen, but since then Apple has clarified the way it is to be written.

  92. fortunately Darwinports is separate by ubiquitin · · Score: 1

    The good news is that darwinports, while related to OpenDarwin, is a separate project, and James Berry indicated on the mailing list that porting efforts could continue on.

    --
    http://tinyurl.com/4ny52
  93. Re:Apple Rapidly Losing Its Cool by Anonymous Coward · · Score: 0

    Same here, and that's after using iTunes since version 2 in OS 9. Though I just started using it about three weeks ago, so maybe past versions have sucked hard? I suggest the GP should give it another shot.

  94. Thanks by chiark · · Score: 1

    Thanks for taking the time to post that, I really appreciate it. I'm currently working through Cohen's Mac XCode 2 book, and have yet to write any code but was leaning towards carbon - your post does help me to rethink that! I hadn't realised about GnuStep, either, which means I'm not wasting effort.

  95. Re:You're mistaken, Apple does release tons of cod by feranick · · Score: 1

    Yes, correct, I was a bit too extreme sayng that Apple does not release any piece of code. However, as it wwas very nicely explained above in other posts, If you had to recompile the OSX yourself with the bits of source that actually are available, you would not go further than the login screen.

  96. re: unstable tree by King_TJ · · Score: 1

    Yes... I saw that post right after I commented.
    I'll give that a try!

    Thanks!

  97. XAR ! by Anonymous Coward · · Score: 0

    xar!

  98. Again mistaken, and hardly fair by LKM · · Score: 1
    If you had to recompile the OSX yourself

    The question here is: What is Mac OS X?

    You can compile your own PPC Darwin. You can boot that and log into it. There's no Intel version of Darwin (yet - maybe Apple will never release it, maybe they will do it after 10.5), but again, what is Mac OS X? The relevant userland parts are from BSD, anyway. You can combine FreeBSD or OpenBSD with some of Apple's code and KDE to get something that shares a lot of the functionality with Mac OS X.

    There are some things you can't get: The most obvious are Cocoa, Carbon, the Finder and the Core compenents (like Core Graphics). There's a simple reason for that: Apple relies on these parts for its competitive advantage. If you want Apple to exist, you must accept that they will keep this proprietary. If they were to open these things, they'd lose their competitive advantage and would be an iPod-only company within few years.

    Most Mac users buy Macs for two reasons:

    1. They prefer the look and feel of Mac OS X
    2. They prefer the applications on Mac OS X

    Opening the Finder and stuff like Core Graphics would mean that Linux would have a superior file manager and UI within months. Opening Carbon and Cocoa would mean that Mac apps would run under Linux within months.

    Blaming Apple for not opening these parts is hardly fair. They need these parts to remain proprietary if they want to keep existing as a computer manufacturer and OS developer.

  99. Re:Sometimes I wish I weren't such a sux programme by QuantumG · · Score: 1

    "Bundle" does not mean "make available to download", it means "put on the install CD".

    --
    How we know is more important than what we know.
  100. NO IT DOES NOT by Anonymous Coward · · Score: 0

    Linus has declared that he does not believe the GPL covers binary modules and he will not sue anyone distributing them. But there is no special exception in the Linux GPL, and the laywers who wrote the GPL disagree with Linus, and any of the other kernel authors could sue ATI and NVIDIA at any time.

  101. Re:GNAA by Loconut1389 · · Score: 1

    meh- karma to burn. If you're not sick of GNAA shenanigans, you haven't used the internet long enough.

  102. Re:Apple Rapidly Losing Its Cool by Geoffreyerffoeg · · Score: 1

    Temporary files!? Why not just mplayer -shuffle -playlist ?

  103. Re:Apple Rapidly Losing Its Cool by Geoffreyerffoeg · · Score: 1

    Temporary files!? Why not just mplayer -shuffle -playlist <(ls *.mp3)? Or even ls *.mp3 | mplayer -shuffle -playlist /dev/stdin (if mplayer doesn't support the - convention)?

  104. Re:Apple Rapidly Losing Its Cool by Anonymous Coward · · Score: 0

    Whoops, typo.

  105. Re:Sometimes I wish I weren't such a sux programme by Ilgaz · · Score: 1

    On OS X some of the best performing multi platform software is written using QT. They have great reviews from ordinary mac users too. I see Mono guys shipped .NET for OS X but I haven't seen a single software requires it.

    QT programs are complete commercial success. A good example is Skype. If you are against QT because they require money from closed source developers who sell commercial software please say it openly.

    If they will be crushed, I won't believe until one of these guys who actually codes real life, billion dollar stuff switch to .NET
    http://www.trolltech.com/customers

    As we speak about Apple here, these guys gave up PowerPC because they see future as portable. Guess who already has a working product which works on every portable device out there? Trolltech.

    I see c# people speaks about how great thing it will be and how excellent it performs but in reality I got Opera Mini on my phone, a free application which uses 107kb of space. It is the J2ME 2.0 version with all bells and whistles. I got Skype which gets good reviews from the most OS X community.

    Where is the .NET for OS X or Linux? I mean the usage. I see there is .NET for OS X true, downloadable, perfectly packaged. Where is the software using it?

    Perhaps people got their own reservations because of stories like this?
    http://developers.slashdot.org/article.pl?sid=05/0 9/17/226241

  106. Re:Sometimes I wish I weren't such a sux programme by Anonymous Coward · · Score: 0

    What, exactly, is acceptable?

    Qt is straining so much at C++'s limitations that the authors felt the need to extend C++ to implement it. OpenStep takes this one step further and grafts an entire second-generation* object oriented system onto C to try to make C a viable platform for its development. They're not exactly comparable either as OpenStep also covers a wide range of functions outside of the widget toolset.

    Both, quite honestly, suck in many ways, but they get the job done, and most of the religious wars to do with both have to do with what the developers are used to.

    Meanwhile, pretty much the entire GNU/Linux community does, contrary to your comment, accept that X11 is an abomination. It's just the alternatives so far come up short. Most Windowing systems don't even run over a network unless you're willing to take your entire desktop with you. So we plod on with X11 as the least awful of the terrible windowing systems, waiting for the day someone will come out with something actually good. Word to the wise: that ugly, PDF-inspired (WTF?), mess that is Quartz is NOT even remotely a decent design.

    * First generation == SmallTalk and other "complete" OO designs. Second generation == systems grafted onto existing procedural unmanaged languages in an attempt to fix them. Thid generation == Java, C#, OO implementations that are complete and don't compromise in an attempt to be compatible with legacy code, that nonetheless use familiar syntax.

  107. Re:Sometimes I wish I weren't such a sux programme by jcr · · Score: 1

    Quartz is NOT even remotely a decent design.

    Show me something better. That's Ok, I'll wait.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  108. How exactly is *Apple* pissing you off here? by argent · · Score: 1

    when I mention Linux they respond with "But OS X is Linux" [...] but they say "same thing" it really pisses me off(especially as a Linux user).

    How is it that something Apple isn't doing (claiming OS X is Linux) is pissing you off with Apple? There's lots of people who confuse BSD and Linux, but that doesn't make me pissed off with Linux Torvalds.

    I cannt imagine what the BSD developers/users feel.

    Clearly, because this BSD developer/user isn't pissed off with Apple at all. Some Linux users, though, really need a free whack with a clue stick. :)

  109. Most programmers are "non-geeks". by argent · · Score: 1

    I spent 20 years supporting a team of PhD engineers and programmers, and most of them were [non-geeks]. Even a lot of the ones who thought they were, who pulled stupid stunts that ended up with me having to disinfect their computers while they railed at me about how they were special and should be allowed to ignore the security policies that would have kept them from getting infected.

  110. Nit-pick by metamatic · · Score: 1
    More specifically, because both IBM and HP push it - the same code base - instead of both making it into incompatible proprietary products, as happened to the BSD variants.

    IBM and HP made System V into incompatible proprietary variants, not BSD.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  111. Re:You're mistaken, Apple does release tons of cod by mikefe · · Score: 1
    • Darwin
    • Darwin Streaming Server
    • Bonjour
    • WebKit
    • Compiler Tools
    • HeaderDoc
    • OpenDirectory
    • OpenPlay

    And of course, there's more, in addition to all the other existing open source components which they use and contribute to.


    There's even more which they don't release, and you can like that or not (it's a business decision to them), but you can't claim that they don't release code.




    I have often wondered why apple's open offerings didn't get traction on other platforms and then I read the APSL - Apple Public Source License.

    It has nice protections from Patent infringement law suits -- but only for Apple. I haven't read the license word for word, but from a quick glance Apple is keeping most of the protections for themselves, not any other contributors.
    --
    There: Something at a specific location.
    Their: Owned by someone.
    Please make sure your english compiles.
  112. Um, no, "plagiarism is what BSD is *not* about". by argent · · Score: 1

    In fact it's the FSF that convinced the CSRG to remove the attribution clause from the BSD license.

    Ain't that ironic?

    I wish Apple would have partnered with GNU/Linux.

    That wouldn't have happened. If the choice had been Linux, BeOS, cutting a deal with AT&T over the System V license, or finishing Copland... Linux wouldn't have made the short list. The license is a deal breaker for anything but an embedded system.

  113. Way to confuse an analogy... by argent · · Score: 1

    the radioactive spider venom "just works".

    Only in comic books, Objective C works in real life.

  114. BSD is *in the kernel*, and GPL won't work there. by argent · · Score: 1

    I'd say that their web browser is a strategically more important component to Apple and its userbase than some unix userland utils.

    Mach is a LONG way from a complete operating system, and there's most of a BSD kernel there in kernel space alongside Mach: the "BSD single server" for operating system services.

    If they made the kernel GPL, they'd have to make many of their kernel modules - and most of the really critical ones - GPL as well, which would have brought Quartz and everything built on top of it into the GPL. That was just NOT going to happen.

  115. Becomes part of the commons -- and stays there? by argent · · Score: 1

    I don't find GPL software stays in the commons any better than BSD software. I have just as much trouble finding old GPL software as old BSD software.

    What keeps open source software in the commons is active development by the commons. Lose that, and the software rots... falls behind current APIs... and eventually vanishes.

    The only difference with BSD software is that with BSD software there can be proprietary forks. If the open source model works (and it does, for an awful lot of stuff) the proprietary fork has to play catch-up. Where the open-source model doesn't work, the version in the commons is going to tend to be a poor cousin to the commercial version anyway... and end up falling out of active development.

    Like happened here, and would have happened eventually no matter what Apple did, because the real problem was the lack of interest from the open source community for a slower and less capable cousin of FreeBSD, OpenBSD, NetBSD, Red Hat, Suse, Debian, Gentoo, Solaris, or Lites...

  116. I wish Microsoft *would* open source the NT kernel by argent · · Score: 1

    It's like Microsoft opensourcing the NT kernel and keeping Win32, DirectX, COM, .NET*, etc closed.

    That would be tremendously useful. The NT kernel is a really interesting system that has all kinds of potential that Microsoft's thrown away for fear they'll distract attention from their "crown jewels"... the Win32 subsystem. An open source NT kernel would allow for a real open UNIX-compatible subsystem, rather than having to choose between staying in the awful Win32 environment or depend on Microsoft's goodwill with Interix. It would allow for GOOD ports of filesystems like UFS or XFS to NT, and better interoperability with open systems. It would also let people do to Microsoft what OSx86 did to Apple, and wiping out all their DRM and license validation in one fell swoop... which is the real reason it won't happen.

  117. It's the applications, ... by argent · · Score: 1

    Yes, it's nice that Apple "just works".

    It's nicer that Apple actually has commercial applications available.

    1. Re:It's the applications, ... by HiThere · · Score: 1

      Sigh ... yes.
      They aren't always better, but sometimes they're the only option...if they're there.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  118. Red hat *can* fork off an go it alone. by argent · · Score: 1

    If red Hat was willing to give up the input from the open source community to the extent that Apple has, they pretty much *could* fork off and go it alone. There have been forks in GPLed projects in the past, and there will be in the future.

    It's not the GPL that binds Linux together, it's the open source community. It's not the GPL that makes Open Source work, it's Open Source that makes the GPL work.

  119. Why was nobody interested in open darwin? by argent · · Score: 1

    So why was nobody interested in Open Darwin? Because it's Apple's product.

    Hardly.

    I'm not interested in Open darwin because it's got no point.

    Darwin is a lower performance kernel than FreeBSD, supports fewer drivers than FreeBSD, and can't do much of anything that FreeBSD can't do better other than provide a modicum of compatibility with OS X for server applications... and OS X is a poor server platform.

    People don't run operating systems for the sake of running operating systems, they run them for the sake of doing something with them. What can yo do with Open Darwin you can't do better elsewhere?

  120. A project has to have a point. by argent · · Score: 1

    What, is it only if you're taking on Microsoft that you guys give a damn about a project?

    No, it's only if I've got a reason to use a project that I give a damn about the project.

    As a platform for understanding and working with OS X, developing tools to work with OS X, darwin's got a point.

    As an operating system, it's a sluggish poor relative to FreeBSD, and it doesn't do anything I can imagine wanting to do that FreeBSD doesn't do better.

    The only valuable thing they were doing was providing a place for "the insignificant little projects" you're complaining about. The core itself is pretty much worthless beyond that.

  121. People don't pay for APIs... by argent · · Score: 1

    Your other two bullet points are really all variants of this:

    Over time, more APIs will have to go Open Source as they become commodities that people aren't going to pay for.

    People don't pay for APIs, they don't even pay for operating systems, they pay for having their problems solved. Apple provides a way to run commercial software that doesn't involve the toxic swamp of Windows, and that's why people are still buying Macs.

    And the same thing with open source. You can't *push* something into the open source community. Software succeeds as open source if it provides something that people need and are willing to pay for in time spent hacking on it. Darwin as a collection of open source projects that build on the source code Apple's releasing and do things with it that people actually need was a success. Darwin as an open source OS based on the core of OS X had no market. Why? Because nobody needs another free UNIX variant that provides no new and interesting capabilities. Darwin without the rest of OS X is just FreeBSD writ slower.

    Open Source code from Apple is not the improvement playground of Linux, but a utilitarian structure that is only changed when necessary, and only by Apple.

    The same is true of Red Hat, really, and yet they're the most popular Linux version in the real world.