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."

84 of 470 comments (clear)

  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. 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 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. 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 kfg · · Score: 3, Funny

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

      KFG

    3. 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...
  4. 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 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.

    6. 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)
    7. 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.

    8. 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.

    9. 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
    10. 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.
    11. 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.
    12. 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.
    13. 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.
    14. 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)
    15. 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.

    16. 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...
    17. 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.
    18. 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!
    19. 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.

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


      OK, now you're trolling...


      Rich

  5. 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 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.

    3. 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."
    4. 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.

  6. 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 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. .... 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 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.
    3. 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.

    4. 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. 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.
  9. 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.
  10. 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

  11. 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.
  12. 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."
  13. 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.

  14. 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.

  15. 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.

  16. 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.

  17. 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.

  18. 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!
  19. 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.
  20. 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
  21. 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.
  22. 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
  23. 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.

  24. 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.

  25. 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.

  26. 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.
  27. 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
  28. 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 :|

  29. 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.
  30. 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 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.

    2. 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.

    3. 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.

  31. 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"
  32. 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."
  33. 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.

  34. 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?

  35. 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.
  36. 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.
  37. How long till OpenSolaris goes the same way? by whoopi_cat · · Score: 2, Interesting

    I say they'll muddle on for another year.

  38. 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.
  39. 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
  40. 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!

  41. 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.

  42. 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.