Slashdot Mirror


How Good Of A Unix Is Mac OS X ?

Anonymous Coward writes: "Greg Knauss, a UNIX guy from way back and a contributor to Suck, TeeVee, creator of Metababy, etc., has written a piece for Macworld.com. He looked at the Unix underneath the new Mac OS X Public Beta and has generally positive things to say, with a few caveats." Among these shortcomings are the lack of the GNU tools, about which Knauss says "... [W]hile the arrival of the GNU tool set -- the mainstay of Unix development -- is inevitable, it's a shame that Apple didn't see fit to include it in the Mac OS X beta."

360 comments

  1. Re:Well, that's okay... by pb · · Score: 2

    Ok, I finally found the paper I was citing. It's in postscript, but it's really worth reading at least once, even if it is from '95...

    It's a good paper, but I'd like to see current results for the testing, too. I guess I should hunt down a copy of the FUZZ tools. I don't have a copy of NEXTSTEP, but it looks like they were using NEXTSTEP 3.2.

    However, NEXT had the worst failure rate, at 43%. If they switched to the GNU tools later, well, that's fortunate, 'cause they were the best, at only 6%...
    ---
    pb Reply or e-mail; don't vaguely moderate.

    --
    pb Reply or e-mail; don't vaguely moderate.
  2. Re:Well, that's okay... by pb · · Score: 1

    Don't those FreeBSD people have any notion of binary packages? Or would that be completely non-portable now?

    I'm with the other guys: if they changed *that* much stuff, then grab a copy of Darwin; there are many crazier things out there. Otherwise, good luck writing a compiler (and an assembler, and an...) with the tools they give you. You might have more luck with a cross-compiler, in that case. :)

    I completely sympathize; my school uses tcsh, and trust me, there's no good way to change that. (you can have tcsh run a bash, yeah, but then you have to port all the aliases and crud that's already set up) Whenever I want to do any real scripting, I run bash; I'm just more comfortable with it.
    ---
    pb Reply or e-mail; don't vaguely moderate.

    --
    pb Reply or e-mail; don't vaguely moderate.
  3. Is Mac OS X anything like A/UX (remember that)? by root · · Score: 2

    I always thought A/UX was the coolest OS around. Apparently, very few people used or seen it. Our school (UCLA) got a bunch donated by Apple. They were great! UNIX underneath with the Mac interface running on top. Truly the best of both worlds, without the bloat and limited apps available for X. What ever became of A/UX? Did it evolve into OX X or is OS X something totally new?

    1. Re:Is Mac OS X anything like A/UX (remember that)? by I+R+A+Aggie · · Score: 1
      I always thought A/UX was the coolest OS around. Apparently, very few people used or seen it.

      It ran on top of MacOS -- with all the dangers inherent in that. It was a somewhat strange unix for it's time -- SysV2 based, IIRC.

      I think you're the first person I ever heard say good things about it. And it was damnably expensive. Like most of its competition...

      James

    2. Re:Is Mac OS X anything like A/UX (remember that)? by cpt+kangarooski · · Score: 1

      the only reason a/ux ever existed was IIRC government regulations that mandated that computers they bought had to be able to run a POSIX OS. They didn't have to actually run it, they just had to be able to.

      In fact, you're the first person I've ever talked to that _did_ use it. I understand that most people just bought it to satisfy the requirement, and then sat down and used the Mac, never even opening the a/ux package.

      I suspect that MS's Xenix was sold to OEMs selling to the government as well. But a/ux died around the time of the Great PowerPC Migration and has never come back since (though there was MAE, which was a Mac on Unix type of deal...)

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    3. Re:Is Mac OS X anything like A/UX (remember that)? by jvj24601 · · Score: 1
      I always thought A/UX was the coolest OS around. Apparently, very few people used or seen it.
      It ran on top of MacOS -- with all the danger inherent in that.

      You are wrong. System 6.0.x ran on top of the UNIX core, and in later versions System 7.0.1 worked (I don't think it ever got to 7.5).

      It was a somewhat strange unix for it's time -- SysV2 based, IIRC.

      That's very true. I think GNU stuff worked, but it was painful.

      More info is available from the A/UX FAQ.

    4. Re:Is Mac OS X anything like A/UX (remember that)? by coult · · Score: 1

      Mac OS X is isn't totally unrelated to MkLinux. MkLinux is based on the Mach microkernel, and Apple leveraged their development on the MkLinux project to improve the Mach kernel they are using in Mac OS X.

      --

      All is Number -Pythagoras.

  4. NeXTSTEP was the best *nix by Jack9 · · Score: 1

    Ajax said it was the best UNIX there he has ever used. I value his opinion; so should you.

    Often wrong but never in doubt.
    I am Jack9.

    --

    Often wrong but never in doubt.
    I am Jack9.
    Everyone knows me.
  5. Re:Well, that's okay... by Nonanonymous_User · · Score: 1

    But NEXTSTEP used the GNU tools too (gcc, and so on). Read your NEXTSTEP license agreement before posting. :)

    -David

  6. Re:NeXTSTEP wasn't a good Unix either by Felinoid · · Score: 1

    > THIRD RULE OF SLASHDOT READ THE DAMN ARTICLE.

    (Third rule of geeks in space.. don't talk about anything BUT geeks in space while on geeks in space) [CmdrTaco]

    Rule 4.. Ignore rules 1-3.. existing posts.. and the artical itself

    GCC will be available for MacOs X soon

    --
    I don't actually exist.
  7. One button mouse by DigitalDragon · · Score: 1

    Hmm.. If only they had a normal 2+wheel mouse, then they would rock. I mean not some M$ or Logitech, but brand name Apple mouse. Then I would for sure switch from Windoze, to Mac for Java programming.


    --
    http://dtum.livejournal.com
    1. Re:One button mouse by cpt+kangarooski · · Score: 1

      it's got to come with _some_ kind of mouse. might as well be a simple one that everyone's used to. By all means, if you want a multibutton mouse, just get one. You might need a driver for some of the more exotic ones, but generally I'd expect them to just work. (and there are plenty of people that'll buy the Apple mouse off of you, I'm sure ;)

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    2. Re:One button mouse by Lowdown · · Score: 1

      ah that old chesnut.
      you know i honestly wish Apple would release a three button mouse. partly because i want the functionality (which is why i'll order one) but more because i'd like to see what people would find to complain about if they did.
      probably just another pointless rehash of Apple SUX! they killed the clones!

  8. Yes by TheInternet · · Score: 2

    I guess it would be too much to ask for Mac OS X to use rpm

    Not natively, but somebody could probably port it. Of course having two project managers on the same system is probably a bad idea, at least for non-hackers.

    but I would be thrilled to hear that there is a real package management scheme built into Mac OS X. Is there?

    Yes. The files are .pkg (or at least they were in the developer releases). I don't know if the package management system has any special name beyond "package manager."

    A real problem with the Mac OS X of old is that it's waaay to easy to scatter installed software all over the place.

    I assume you mean the "Mac OS" of old. ;) And despite the lack of package management, I still felt it was easier to find installed files on Mac OS than on Windows or *nix.

    A real package system would also make it so convenient to upgrade the system, especially during the beta cycle.

    I'm pretty sure it has signed internet-based updates (Mac OS 9 does). The help system is also dyanmically grabbed from the net, apparently. Though I hope there's backup access if TCP/IP is unavailable.

    - Scott


    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
    1. Re:Yes by TheInternet · · Score: 1

      Of course having two project managers on the same system is probably a bad idea

      Errr, would you believe "package managers"?

      Also, I believe USB printing is available to some degree in this release.

      - Scott
      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
  9. Re:Heh. Now MS Office will run on *nix! by Kronovohr · · Score: 1

    Microsoft vs. carbon compliance...why is it I got a giggle off that?
    "Damnit, Word just locked up on me again!"
    "It's 'cause you're a 'carbon based lifeform', and Office isn't carbon
    compatible yet."

  10. Re:Come on... by KFury · · Score: 3

    To address your points one by one:

    - If there's a consistent interface, then where did my window managers and widget sets go?
    Consistant doesn't mean identical. Almost no two mac desktops look the same today. What would make you think people won't customize them on OS X as well?

    - If it's "easy to use", then where did my shell prompt go?
    Nice use of sarcastic quotes, but easy to use means using the best tool for a particular job. With that in mind, go ahead and use a shell prompt when you want to. It's there and full-featured. What's the complaint?

    - How do I turn these (*@#% tooltips off?
    Ahh, that's not an OS X complaint, as MacOS doesn't have tooltips. That's more a Microsoft/Adobe/Macromedia complaint, yes? In point of fact, Mac OS X also does away with balloon help, so this is a good thing.

    - How do I get a real, 8-bit-clean text editor?
    Use TextEdit, the 8-bit-clean text editor that replaces SimpleText in OS X.

    - Why does the shell bug me about 'filetypes' all the time? Why do I care?
    It doesn't because you don't. You must have noticed all these .app extensions, yes? Is n.3 really better than type/creator attributes?

    Linux does look pretty slick, but personally I've found that when I have work that requires my own skill (coding, composing text, etc) I use my Linux box, but when I have work that requires the computer's skill (page layout, gif animations, etc.) I use my Mac or Win laptop. The Linux OS is slick, the Linux tools are powerful, but the MacOS is friendly, and if it can give me power and slickness(?) too, I'll take it over the alternatives.

    Kevin Fox

  11. Apple hints about Intel by quickquack · · Score: 1

    If you look at this page, you'll see right under 'Release 1.0' Apple says this:

    [...]Preliminary support for Intel is provided, allowing developers to begin bringing Darwin to the Intel platform.[...]

    Could this possibly mean they *are* interested in porting it to Intel? I sure wouldn't mind...

    -----
    GPLed POP3/IMAP/SMTP to Web/WAP gateway
    ------------

    --
    ------------
    Tonight on Fox: Deadliest Executions Part XVII
    1. Re:Apple hints about Intel by ptbrown · · Score: 1

      That's Darwin. The Darwin team is working on x86 support because it's good developer PR. And, of course, "because it's there." There's also the need to pay homage to the legacy of OpenStep.

      MacOS X, on the other hand, is Darwin + Quartz + Quicktime + Java + Aqua + Carbon + etc-etc, and no one has even accidentally said that MacOS X will ever work on anything other than PPC w/ AltiVec.

      --
      Any sufficiently advanced civilization is indistinguishable from Gods.
    2. Re:Apple hints about Intel by Harv · · Score: 1
      Here's progress. The Darwin site referenced above is running Apache 1.3.4 on MOSX. A lot of Apple's sites are still running on Solaris, but it's apparent now that they're willing to trust the family jewels to their own stuff. Cool .

      In addition, I believe this page is clear evidence that MOSX can eventually be ported to Intel hardware, whether to put the fear of god into MOTO, or just do the prudent thing and keep some options open should MOTO be unable to goose the PPC chips over 500-600Mhz.

  12. Re:NeXTSTEP wasn't a good Unix either by spoot · · Score: 2

    Um... Wasn't the first web client and server -- built with NEXTSTEP at CERN by Tim Berners-Lee ? Without this 'not so great... desktop... Unix... that sucked", this page would not be here.

  13. Re:Software by E+V+I+L+G+E+E+K · · Score: 1

    You're right it doesn't (we'll it does as long as you like products two versions out of date), I was merely replying to a post which I interpreted as saying an easy to use UNIX had never existed.

    Yes, carbon is good - the Rhapsody model was asking to much of developers and probably would've killed Apple, and I'm glad someone at Apple got hit with the cluestick(tm) and saw that it would never really work and should be replaced with a more sensible one.

    --
    This space intentionally left blank.
  14. Re:Apple pie by Yardley · · Score: 1

    No. The G4 is affordable. From the Apple store, you can get a box for $1,599. Used G4's are even cheaper and available from many sources online.

    400MHz PowerPC G4
    1MB L2 cache
    64MB SDRAM memory
    20GB Ultra ATA drive
    DVD-ROM w/DVD-Video
    RAGE 128 Pro graphics
    Gigabit Ethernet
    56K internal modem

    Drop the 56k modem to save $50 more.

    --

    --

    --
    He lives in a world where those who do not run the client software of the omnipresent meme are unacceptable.
  15. Want gcc under OS X? by Rura+Penthe · · Score: 1

    Go to http://maximumlinux.com/content/news/2000/09/13/11 335 and have a blast with gcc on OS X public beta.

  16. Re:Wow! by ca1v1n · · Score: 1

    More importantly, it even comes with vi!

  17. Re:article references DeCSS-through-DNS! by Colbey · · Score: 1
    That worked for me yesterday (or something similar)...except now, the resulting text isn't DeCSS...

    --Colbey

  18. Software by TheInternet · · Score: 2

    I use something like this every day - it's called IRIX

    Ah yes, but IRIX doesn't have all the Mac software -- Adobe, Macormedia, MetaCreations/Corel, games, etc. This is why Carbon is good, and Rhapsody was bad.

    - Scott
    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  19. Re:NeXTSTEP wasn't a good Unix either by Anonymous Coward · · Score: 1

    Actually, in the 80s, Apple planned to buy Sun and move the MacOS GUI to SunOS. I think they also toyed with Apollo.

    The Sun deal fell through when Apple offered a ridiculously low price. Sun got them back by doing the same during Apple's low period in the 90s.

    This is all in an old Wired article about Apple's decision not to allow clones in the 80s.

  20. My Innocent Comment by Outlyer · · Score: 5

    Perhaps they were afraid that, by including the GNU tools, Stallman would badger them into calling it GNU/MacOS X :)

    --
    ----------------- "I have a bone to pick, and a few to break." - Refused -------------------
    1. Re:My Innocent Comment by cpt+kangarooski · · Score: 1

      you mean i registered macosxiv.com for nothing?

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    2. Re:My Innocent Comment by ActionListener · · Score: 1
      I'm confused by the name as it is. I mean, how is one supposed to pronounce Mac OS X?

      Here are some of my current best guesses. Someone tell me which is correct.

      1. Oh Ess Ex

      2. Oh Ess Ten

      3. 0 S eX (Zero Sex?)

    3. Re:My Innocent Comment by ptbrown · · Score: 1

      Oh, haven't you heard? The Steve says we should support Microsoft apps on MacOS.

      --
      Any sufficiently advanced civilization is indistinguishable from Gods.
    4. Re:My Innocent Comment by rabidMacBigot() · · Score: 2

      Besides, there's no reason you couldn't compile the GNU tools yourself.
      Kudos to Apple for setting the default shell to tcsh, too - and aliasing ll to ls -l by default.

    5. Re:My Innocent Comment by Coward,+Anonymous · · Score: 1

      I assume Apple calls it Oh Ess Ten since the X stands for 10, but everyone I know calls it Oh Ess Ex, since that's how it's written. I suspect the next version will be called 11 instead of XI and we'll be done with this roman numeral silliness.

    6. Re:My Innocent Comment by Enahs · · Score: 1

      Oh mah Gawd!!! Paw!!! We kin git sum barls made right special just ta shoot badgers!!!

      God, that's funny. I wonder what RMS would say to this...God, what a riot.

      --
      Stating on Slashdot that I like cheese since 1997.
    7. Re:My Innocent Comment by Paradise_Pete · · Score: 1
      El Steve calls it oh ess ten. Everyone else calls it oh ess ecks.

      ABCD Goldfish?
      LMNO Goldfish!
      OSAR.

      -Pete

    8. Re:My Innocent Comment by benedict · · Score: 1

      I figure it can be abbreviated "MOSX" and hence pronounced "Mosix", to highlight its unix heritage.

      Mosix would also be a good name for a jewish version of Jesux, I suppose.

      --

      --
      Ben "You have your mind on computers, it seems."
    9. Re:My Innocent Comment by gig · · Score: 1

      tell application "Finder"
      display dialog "hello world"
      end tell

    10. Re:My Innocent Comment by tao · · Score: 1

      Nope. Emacs exists in many different variants; GNU Emacs being one of them. The beast has got many faces. But why care? Go Go VIM!

    11. Re:My Innocent Comment by Bouncings · · Score: 1
      What about emacs? It's GNU isn't it?

      BTW, for the "GNU is bloated and sloppy" comment parallel to this one: BSD's sort will die on anything over 50, 60 megs on any server. I've had Linux on an emachine desktop sort hundreds of megs while the SMP BSD box down the hall's sort command dies on "out of filehandles" after taking up crazy amounts of memory.

      In my data importing experience, GNU's sort, sed, awk, and grep are far faster and take less memory.

      --
      -- Ken Kinder ken@_nospam_kenkinder.com http://kenkinder.com/
    12. Re:My Innocent Comment by dvdeug · · Score: 1

      Bloated I can see, but why sloppy?

    13. Re:My Innocent Comment by ColdGrits · · Score: 1

      Easy.

      Given previous releases were called "Mac-oss ate" etc (MacOS 8) thenyou pronounce MacOS X as

      "Mac-oss ex"

      Or "Mac-oss 10" if you really want I guess.

      --
      People should not be afraid of their governments - Governments should be afraid of their people.
    14. Re:My Innocent Comment by Prolog-X · · Score: 1

      This is true. csh is unable to manipulate any file descriptor, errs on a simple time | echo statement, says kill -1 `cat foo` is ambiguous, can only trap SIGINT, and has strange bugs. However, tcsh fixes some of these bugs. See Tom Christiansen's Csh Programming Considered Harmful article for more information.

    15. Re:My Innocent Comment by Prolog-X · · Score: 1

      mtool's mdir command can emulate MS-DOS's dir command.

    16. Re:My Innocent Comment by Mawbid · · Score: 1

      Indeed. Didn't the GNU tools crash less than vendor tools in the "feed'em input from /dev/urandom" test, for instance?
      --

      --
      Fuck the system? Nah, you might catch something.
    17. Re:My Innocent Comment by xhypertensionx · · Score: 1

      Either OS 10, or OS X is correct... I think they added the X because in a way, it signifies a new Mac OS. Don't worry though, just talking about it makes you smart.

      --

    18. Re:My Innocent Comment by nufan · · Score: 1

      GNU tools typically do have more features than their class Unix counterparts but they are almost never "sloppy." 95% of the time they work better than their traditional counterparts.

    19. Re:My Innocent Comment by mevan · · Score: 1

      Actually, the "display dialog" command belongs to the standard additions OSAX, so it's not neccessary to "tell Finder". You can shorten your script to ...

      display dialog "Hello World"

      Fortunately, AppleScript is kind enough to pass the command on to the OSAX even though you've sent it to the "Finder".

    20. Re:My Innocent Comment by be-fan · · Score: 2

      Like Linux?

      PS> If he did't get modded down for calling GNU stuff bloated and sloppy (which it isn't) I shouldn't get modded down for calling Linux bloated and sloppy ;)

      --
      A deep unwavering belief is a sure sign you're missing something...
    21. Re:My Innocent Comment by be-fan · · Score: 2

      That's because FreeBSD uses the BSD-C library.

      --
      A deep unwavering belief is a sure sign you're missing something...
    22. Re:My Innocent Comment by plunge · · Score: 1

      I don't want to open a can of worms, but GNU stuff is generally bloated and sloppy. Apple is trying to avoid such things.

    23. Re:My Innocent Comment by psergiu · · Score: 1

      Mosix allready exists and is an cluster extension for Linux.

      --

      --
      1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
    24. Re:My Innocent Comment by tzanger · · Score: 1

      it's true. GNU stuff is bloated. take glibc for example. gcc helloworld.c -o helloworld -static and you've got a whopping big ~700k binary on my system. strip it down and it's still at least 250k.

      I'm calling you on that.

      #include <stdio.h>

      int main(void)
      {
      puts("Hello, world!");

      return 1;
      }

      $gcc -o hello hello.c -static
      $ls -l hello
      -rwxr-xr-x 1 andrew users 109919 Sep 17 10:47 hello*

      $strip hello
      $ls -l hello
      -rwxr-xr-x 1 andrew users 95448 Sep 17 10:47 hello*

      Granted, I only get about 16 bytes' worth of savings with -O2, but that's still under 1/2 of your 250k "estimate". Dynamically linked the binary hits 2.5k. So yeah it's kinda bloated. But not quite like you would suggest. I can't get LCC to generate a statically-linked win32 file, but a dynamic, static win32 hello world requires CRTDLL.DLL and KERNEL32.DLL and is 3.6k. My dynamic compile on Linux is 2.5k. Apples to oranges, yes, but there's the numbers.

  21. Re:Of course the tools stink, it's a Mac. by cerulean_blue · · Score: 1

    ...Hummm...
    "You don't sound like you've used it; perhaps you should, before you pass judgement?
    Probably the best bet for now is to stick with LinuxPPC, something not blocked by Steve Jobs' arrogance
    Unless you run it on an RS-6000...."

    Are you looking at the same RS/6000 I am?
    LinuxPPC runs quite well on the RS/6000. However, I am partial to AIX which was written from the ground up to run native on the POWER Architecture.
    The problem with the RS/6000 is that it is not common in every household like a PC or Mac. AIX has a number of features that would be great in other *NIXes including Linux and maybe OSX...JFS is one.

    vi
    i
    "Enter your comments here!"
    ESC
    :q!

    --

    vi
    i
    "Enter your comments here!"
    ESC
    :q!
  22. Sit back and laugh by KFury · · Score: 5

    This is the most entertaining Slashdot discussion I've ever read.

    On one hand, you have Unix weenies who will swear forever that MacOS is as stupid and lame as a jar of rocks painted like jellybeans, even when they themselves have to resort to FUD.

    On the other you have people who have actually taken a look at OS X and can see that Apple's done a remarkable job at modernizing their OS to a Unix kernel.

    Apple's finally succeded at breaking the Unix ranks into those who like Unix because it's better and those who like Unix because it makes them feel superior.

    Kevin Fox

    1. Re:Sit back and laugh by nebby · · Score: 1

      It is my sig now. Sorry it's paraphrased and you don't get credit.. i couldn't fit the whole idea into less space :P

      --
      --
    2. Re:Sit back and laugh by KFury · · Score: 2

      Cool. Obviously one of the 'superior' camp didn't like it so much, as I've been 'overrated' back down to 3...

      Somebody obviously needs a jar of jelly beans...

      Kevin Fox

    3. Re:Sit back and laugh by AtrN · · Score: 1

      But it's all about 10 years too late as NeXT did it all back then. Hopefully this time around they won't drop the ball again.

    4. Re:Sit back and laugh by Enahs · · Score: 1

      >I'd like to thank... The *BSD crew, for >constantly being the research arm for anyone who >can't do their own research.

      I see...you say that as though you don't appreciate that happening. I see.

      So, if I am to understand you correctly, every time someone goes to build a new OS, they should start anew. I see! We could extend this to other industries as well! I can see the fun now. Ford, for example, hiring large teams to determine how:
      1.) A good, cheap way to propel a vehicle
      2.) A good, cheap way for a vehicle to "roll"
      3.) A way for the locomotion source to deliver energy to the devices that allow the vehicle to "roll"

      The research position possibilities are endless! Wow, Larry Wall won't have time to write Perl anymore, because he'll be too busy inventing a written language every time he needs to commit his thoughts to something other than verbal language...as soon as someone invents a way of recording a written language...and something to put that written language on...

      --
      Stating on Slashdot that I like cheese since 1997.
    5. Re:Sit back and laugh by TheInternet · · Score: 1

      But it's all about 10 years too late as NeXT did it all back then

      Ah, but this time, the revolution doesn't cost $10,000.

      - Scott
      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    6. Re:Sit back and laugh by xhypertensionx · · Score: 1
      However, there's still no reason to use MacOS X.

      Despite all the power and ease of use, plus the ability to run Linux and (since the first PPC shipped) Windows just like a regular PC?

      Sigh, another ignorant jerk. I swear, all my life I have been flamed for being a hardcore Mac user by those who were too foolish and closed-minded to be able to understand the OS.
      I for one have never been able to understand how people who hate another OS are given any technical credibility at all. The most intelligent techies I've met are open minded towards all technlogy; they understand that it exists as a means to an end.
      It seems as if this individual is afraid of what he doesn't understand, like every other Mac agnostic I've met. I think that upon the final release of OS X, "technical" individuals who hate all things Mac will be exposed as the frauds they really are.

      MacOS X is the Messiah that will deliver Macintosh users from exile and restore them to the honor and respect they deserve.

      --

    7. Re:Sit back and laugh by RickHunter · · Score: 1

      I think that what Apple's done with OSX is really cool. However, I wouldn't consider using it in a million years. I am unfortunately a member of the small percentage of the population that cannot look at Aqua without feeling like taking a bite out of my computer screen (it looks SO much like candy). ;-)

      Seriously, I think it is going to wind up being a good thing. At the very least it will help dispell the myth that Unix systems aren't usable as desktop machines. Now, if Jobs will only allow skinning... (Last I'd heard, he wouldn't even consider it)


      -RickHunter
    8. Re:Sit back and laugh by be-fan · · Score: 2

      Undoubtedly, someone will figure it out. Hell, even Windows has theming.

      --
      A deep unwavering belief is a sure sign you're missing something...
    9. Re:Sit back and laugh by wraith9 · · Score: 1

      Myself, I think you ought to be able to like Unix for both reasons. I don't see they're mutually exclusive. It's better, it makes me feel superior, and I hate jelly beans.

      --
      pax ex machina, elvis@whoever.com
  23. Here's why GNU tools weren't included. by juicy · · Score: 4

    I found this in a post from Holt Sorenson on MacWorld.
    Why gnu tools weren't included

    On another note, I think it's shocking that to this day I still hear talk about:

    1. The price of Macs. You can scan this very list to see that it's really not an issue anymore for what you get. I think that people might just be irritated that even a low-end mac is a high-performance machine compared to a less expensive piecemeal Intel box.

    2. The availability of software. In the old days, the argument was that critical apps weren't available and so the machines are fully proprietary. This is of course absolutely the opposite now. Most of the things you *can't* get now are shareware or small-scale development items. Kinda like DOS compatibility with Windows right now.

    3. The quality of the operating system. The normal Mac OS has stunk for a while. But the Unix in Mac OS X has been well proven in the last ten years (since NeXT).

    Here's the post I found:
    Posted By: Holt Sorenson Date: 15-Sep-200011:26p.m.

    At the 2000 Usenix Technical Conference, Wilfredo Sanchez of Apple gave a presentation on The Challenges of Integrating the Unix and Mac OS Environments. The paper can be found at: http://www.mit.edu/people/wsanchez/papers/USENIX_2 000/

    An audio recording of the presentation of this paper at USENIX 2000, including the Q&A session, is available Dr. Dobb's TechNetCast at: http://www.technetcast.com/tnc_play_stream.html?st ream_id=332

    During the questions period, he was asked if GNU tools would ship with OS X. He said that they would not because in an e-mail discussion with RMS, RMS insisted that OS X would have to be GPL'd if Apple included GNU tools.

    --
    -- Eli Juicy Jones
    1. Re:Here's why GNU tools weren't included. by Anonymous Coward · · Score: 1

      I can't imagine that Sanchez is lying about this, as he's a very cool guy who's been doing good work for a long time, but it's also possible that there are some weird details that we don't know about.

      While I can't imagine a reading of the GPL that would require GPLing an OS because it ships with GPL'd applications, I do know that RMS really hates Apple -- he hated it when Apple shipped the GNU tools under A/UX, and even more when they ported them to run under MacOS, particularly adapting gcc to link to the (proprietary) MacOS libraries, allowing developers to use GCC to build non-GPL'd MacOS applications. Remember, RMS' sole agenda is in getting everyone to use free software -- he's stated that he'd prefer to deny the use of his tools to Mac users and attempt to force them to move to a free OS. That was a long time ago, but when Apple's involved he could well be going out of his way to find "problems."

    2. Re:Here's why GNU tools weren't included. by Patrik+Nordebo · · Score: 2

      The cheapest possible G4 costs $1549 (from Apples online store). That gives me a 400MHz G4, 64 megs of memory, 20 gig hard disk, DVD-ROM drive, 16 meg ATI Rage 128 Pro graphics.
      The closest Dell Dimension 4100 I can build costs $1179, with an 800MHz PIII, 20 gig hard disk, 64 megs of memory, a DVD-ROM drive, a 16 meg Rage 128 Pro, an SB64 PCI (I'm not sure how that compares to a G4, I don't know what their sound hardware does), a 3C905C NIC, Altec Lansing speakers with subwoofer.
      So I save $380 for something that is probably faster than a G4 in real use (unless I run Photoshop filters all day). And Dell aren't exactly the cheapest PC maker, and they don't sell Athlons. So it seems to me Macs are still expensive compared to PCs.
      I do prefer Apple's design, though. Macs are much sexier than any PC I have seen. Though older SGI boxen are even sexier.

    3. Re:Here's why GNU tools weren't included. by be-fan · · Score: 2

      Funny, almost the entire user-land POSIX stuff in BeOS is GPL'ed. Can you point me to the source code?

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:Here's why GNU tools weren't included. by cfish · · Score: 1

      Gee, juicy dude, if you use half a second to think about it, you'd know it ain't true. All the free BSD variants are released with GNU tools but the OSes are not GPL'ed.

      Anyway, if NeXT is the only "prove" of Apple's UNIX ability, Steve Jobs must be running scared now.

    5. Re:Here's why GNU tools weren't included. by scrytch · · Score: 2

      > RMS insisted that OS X would have to be GPL'd if Apple included GNU tools.

      And thankfully RMS's license renders RMS's own opionion on this matter not worth a bucket of spit. Solaris 8 includes many GNU tools. BeOS includes the entire GNU toolchain. Cygwin is a GNU distribution for Windows. None of these OS's are GPL'd and my guess is none of them solicited RMS's opinion. My guess is neither did Apple, or for that matter, even Linus.

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    6. Re:Here's why GNU tools weren't included. by gig · · Score: 1

      Some things the Dell is probably missing compared to the Mac:

      FireWire ports ... the G4 has two independent FireWire busses with 400Mbs each, and you can hot-plug digital camcorders, hard drives, CD-RW drives and more
      iMovie 2.0 is bundled for free
      Gigabit Ethernet
      space for 1.5GB of RAM
      easy-access case where the whole mobo is on the door
      Mac OS X Public Beta preinstalled along with Mac OS 9
      Optical mouse
      Mac OS X comes with more apps and more useful apps than Windows, including Apache, HTMLEdit, Sketch, ColorSync, QuickTime, Sherlock, real-time spell checker that all apps can use, print-to-PDF, StuffIt Expander (how can Windows still not have a Zip decompressor built-in?) ... and it can run third-party Mac and Unix apps
      Plus de style

      To me, that's worth $380. Easy DV is amazing. Adding a new hard drive to your system in a few minutes with FireWire is amazing. Adding RAM or a PCI card in less than a minute is amazing. Once these things are made that easy, you don't want to give them up.

  24. "ugly dumptruck"? by jetson123 · · Score: 2
    A lumbering dump truck to the Mac's zippy roadster, Unix is the pug-ugly workhorse that delivers more Web pages, routes more mail, and gets more done than any other computer operating system in existence.

    I'm sorry, but I fail to see the analogy.

    In terms of size and performance, UNIX installations can be small and nimble compared to MacOS X, which has to support a lot more "stuff".

    In terms of software architecture, MacOS is a mess and a dumping ground of legacy technologies: microkernel, UNIX personality, Objective-C, Java, MacOS ROMs, etc.; no design or taste there.

    In terms of appearance, there are plenty of pretty UNIX GUI interfaces.

    MacOS X, with its consumer market share, may be an OK compromise for people who want UNIX reliability and some kind of consumer-oriented system. But I don't think people have been holding their breath for this; MacOS X isn't salvation for the UNIX users of the world, it's salavation for Apple: without it, the company would not have a competitive product at all. This way, they at least have a chance against NT and Linux.

    1. Re:"ugly dumptruck"? by Lowdown · · Score: 1

      i know metaphors can be difficult for the way too literal minded so let me explain.
      all it meant was power vs. style.
      MacOS is pretty, UNIX is powerful.
      get it?
      almost any metaphor can be broken by taking it too far.

    2. Re:"ugly dumptruck"? by connorbd · · Score: 1

      And MacOS X splits the difference.

      /Brian

  25. switching between powerbook and linux laptop by pixel+fairy · · Score: 1
    have you tried running linux on your powerbook and using mac on linux?

    of course, the one mouse button thing really sucks. thats why im using a PC laptop instead despite the nice long battery life of those powerbooks.

    1. Re:switching between powerbook and linux laptop by dbrutus · · Score: 1

      If you want a multibuttion mouse, you can get one fairly inexpensively. If you want long battery life on a PC, you can always try a transmeta powered one... oops, those aren't shipping yet.

      DB

  26. OS X for x86? by frli · · Score: 1

    Anyone know if Apple are planning a port to x86?
    Guess the chances are pretty slim, but it would be kinda cool.

    1. Re:OS X for x86? by bjohnson · · Score: 1

      Oh my.

      "Apple About To Die!"

      News at 11!

    2. Re:OS X for x86? by gig · · Score: 1

      > The biggest issue for mac porting darwin/os-x to
      > the x86 would be the loss of their hardware market.

      No, the biggest issues are:

      1) Most Mac software is full of PPC-specific code, and you can't call something Mac OS if it won't run Mac software. OpenStep x86 did not exactly light the PC world on fire.

      2) Microsoft makes most of its money from two things: porting its own Macintosh software such as Word and Excel from Mac to x86, and copying other people's Macintosh software on x86, so that Mac OS becomes Windows, QuickTime Player becomes Windows Media Player, and iMovie becomes Windows Movie Maker. What can x86 users get from Apple that they can't already get a shitty version of from Microsoft for a little less money?

      > They do not make a single piece of silicon in the
      > computers, and do not sell much of anything that
      > benefits the x86 community hardware wise

      They design and take responsibility for every part of the computer. Sometimes they make the tech (FireWire, case designs), sometimes they use existing tech for interoperability or economics (PCI, USB, BSD, 802.11), sometimes they buy another company for the tech they need (NeXT, and that DVD-authoring company they just bought). Certainly, they put more work into a box than any x86 manufacturer.

      If you're suggesting that you can replace Mac hardware with x86 hardware and not notice the difference, all you have to do is place a PIII cartridge next to a PowerMac Cube. How the hell are you going to fit that inside there? It's running a full-speed G4 chip with 1MB L2 cache that only needs 11 watts, and is the size of a Pentium chip (the original Pentium chip). The Cube would have to be twice the size and have a fan to run a desktop x86 chip (45 watts). It would have to be a quarter of the performance to run a mobile PIII (15 watts).

      There are also no x86 machines with integrated antennae, and none that can give you 5-6 hours on one battery.

      > porting to x86 would allow current mac harware
      > buyers to get the same operating system they love
      > on cheaper hardware.

      This didn't work for NeXT, or else why did they merge back into Apple?

      Apple's stuff is competitive price-wise with Gateway, Dell, and all the rest. It's about to get moreso when Mac OS X replaces Mac OS 9. Apple's competitors offer Windows ME, or you can pay $200 more for Windows 2000. Certainly, the Mac user with Mac OS X is getting more for their money than a Windows ME user.

      Only x86 users think Macs are too expensive. Mac users can't wait to drop their money down for a Cube or an iBook or whatever.

      > steve jobs will most likely kill the efforts for a port
      > (i've heard rumors that darwin/os-x has been ported
      > and is sitting/tied-down in a lab somewhere,
      > screaming to be released).

      Successfully booting Darwin on Intel was announced TODAY and was the result of a lot of open source volunteer work. If Apple already has Darwin running on x86 machines in their labs, it would be a pretty crappy thing to release Darwin PPC as open source and ask people (they did ask people) to start porting it to Intel.

      The rumors you've heard are because there are a few PC's at Apple that run OpenStep or Rhapsody. When Steve Jobs took over the CEO job at Apple, the first thing he did was replace the Mac in the CEO's office with a PC running OpenStep. Later, Rhapsody developer releases ran on x86 as well. A janitor sees a Dell running something non-Windows and thenext thing you know everybody thinks Mac OS X runs on Intel.

    3. Re:OS X for x86? by david.heyman · · Score: 1

      FWIR The idea behind it being "PDF based" is the same as NeXt having been PostScript based. The engine running what is being shown on the screen is a PDF engine getting PDF commands.

    4. Re:OS X for x86? by bmajik · · Score: 1

      Mac OS X is more or less nextstep/openstep. Some things have been updated, somethings added, and some removed.

      The windowing system on OS was "WindowServer". It natively rendered postscript. It's analagous to the Xserver, and the Xserver using the Xlib protocol to be its base set of functionality.

      In OSX, they ditched postscript as the imaging model and went iwth "Quartz" which is more or less PDF. This lets them get away from wholly-adobe owned code.

      people that want to speculate intelligently about OS X should have done at least one of the two following things:

      1) used Mac OS X
      2) used Openstep and/or Nextstep

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    5. Re:OS X for x86? by xjesus · · Score: 1

      The biggest issue for mac porting darwin/os-x to the x86 would be the loss of their hardware market. As of now, macintosh is entirely a hardware manufacturer (like dell/gateway/etc. except they don't use x86) where they put their own operating system and software on that hardware. They do not make a single piece of silicon in the computers, and do not sell much of anything that benefits the x86 community hardware wise so porting to x86 would allow current mac harware buyers to get the same operating system they love on cheaper hardware. Given this, steve jobs will most likely kill the efforts for a port (i've heard rumors that darwin/os-x has been ported and is sitting/tied-down in a lab somewhere, screaming to be released).

    6. Re:OS X for x86? by dbrutus · · Score: 1

      Aside from the ROM, bootstrap code & firmware, what exactly is proprietary about today's mac hardware?

      PCI, AGP, Firewire, IDE, USB, what is it? Is it their case design you want to be "non-propietary"?

      DB

    7. Re:OS X for x86? by TheInternet · · Score: 2

      so porting to x86 would allow current mac harware buyers to get the same operating system they love on cheaper hardware

      It's a little more complex than that. One of the reasons the Mac is so easy to use is that the OS doesn't have to support tons and tons of video cards, SCSI cards, hard drives, etc. It's standardized hardware. So a Mac OS X on x86 would probably not work as seamlessly as one on PPC.

      This intergration also allows Apple to make simultaneous changes to both the hardware and OS to introduce new features. Example: AirPort.

      - Scott


      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    8. Re:OS X for x86? by xjesus · · Score: 1

      This is true. (after reading your bio i realized this a good topic for you). I think what the x86-*nix community is really looking for is the new GUI that Mac has developed on top of the posix-compatible/bsd core. I don't know how much of the UI is built into the kernel, but if they could port the UI to x86 and run it on top of your favorite distro, you could have the nice fluffy mac interface (which the masses seems to like so much) and the tweakable core for the variations of x86 hardware.

      I personaly think the X interface is what is killing linux from being more popular to the masses. The trick is having good default configurations such that to normal users it seems just like the older mac OSes, but to those who know you can open up a terminal and tweak to your hearts desire. Mac could easily get away with it because of the whole 'most people will never know the difference under the covers' of OS-X.

    9. Re:OS X for x86? by TheInternet · · Score: 2

      I don't know how much of the UI is built into the kernel

      I don't think the kernel is married to the UI at all, though the Mac apps are. All the fancy UI stuff happens with the help of the Quartz libraries, though. Quartz is apparently "PDF based," whatever that means.

      but if they could port the UI to x86 and run it on top of your favorite distro, you could have the nice fluffy mac interface

      Interesting idea, but I don't think it's every going to happen. Aside from the fact that it would be a bad monetary decision, it would be a confusing move for Apple strategically.

      - Scott


      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
  27. Re:NeXTSTEP wasn't a good Unix either by sstaton · · Score: 2
    Nonsense.

    NeXTstep (old spelling) was a fantastically clever GUI built upon Mach/BSD4.X and (of all things) Display Postscript. Everything I read about MacOS X tells me that the core ideas of NeXTSTEP remain buried under a slightly different Mac UI; nothing of significance has been removed. Mac OS X is NeXTSTEP.

    Was the UNIX under NeXTSTEP bad? Not really. It was typically a year out of date in terms of the core utilities, but the kernel was unique (Mach) and quite powerful. If you had access to the source of BIND, Perl and other tools, you could update the essential sys admin and developer tools and be quite up to date. Remember, it was just emulating BSD 4.X (2, 3 & 4).

    What makes me sad is how few of you actually got to work on the NeXT. This is like the Second Coming of NeXT, and as one of the few (lucky) ones who saw it in the Cube Daze, let me tell you, it's great to see it back.

    --

    The two most common things in the Universe are dark matter and stupidity.

  28. Well, that's okay... by pb · · Score: 1

    As long as they used the tools from *BSD instead of the ones from NeXT, (which it sounds like they did) I have no problems with it.

    Of course, I like the GNU Tools better, so I'd probably do what every other hacker stuck on a foreign platform would do: compile them.
    ---
    pb Reply or e-mail; don't vaguely moderate.

    --
    pb Reply or e-mail; don't vaguely moderate.
    1. Re:Well, that's okay... by Afterimage · · Score: 1
      tcsh, ugghhh. 'Course, my main reason for not liking it is because I already have my pref's set in bash and i simply port my config files from boxen to boxen (so far, 3 linux boxes and OpenBSD).

      What's weird is that my understanding is that as late as DP3, Apple was distributing multiple shells (bash, tcsh, ksh, zsh). I'd be a little curious as to why they stopped. I suppose they could argue so folks don't mess things up. But then, why did they ship Terminal.app as part of the default install?

      So, until I get a compiler, I guess i'm SOL. Of course, the question I have is whether or not MacOS X supports a ports tree? IIRC, that pretty much delivers the binary, yes?

      That said, I signed myself up as an online developer through ADC so I could get access to the dev tools they'll be releasing for Mac OS X shortly. If I don't fsck my system up by pulling from Darwin CVS first.

      --
      --Humpty Dumpty was pushed!
    2. Re:Well, that's okay... by ahknight · · Score: 1

      And that's an utterly brilliant idea. It really is. There's just one problem: Apple did not include a compiler. =) I'm running it now and for the love of bash, I hate tcsh (flame on, trolls), but I can't get bash because there's no OS X binary that I can find. Same for everything else. And damned if I'm going the route of milking Darwin; that's a little on the crazy side.

      Yeah, so, I'm learning tcsh now. =)
      --

  29. How Good Of A Unix Is Mac OS X ? by zp · · Score: 2
    The developer tools have been a separate install option in the MOSX lineage. I run MOSXS and the developer tools came on a separate CD. Apple will make the tools available later (free registration required), as stated by Ernest Prabhakar (Darwin product manager) to the Darwin announcement list on 09/14/2000:

    The Public Beta does include the basic command-line utilities as well as Terminal.app ( as well as lots of cool non-Darwin code. :-) However, it does not include the compiler or build tools. Those (as well as all the GUI-based developers tools) will be available for free download (registration required) from the Apple Developer Connection website in mid-October [http://developer.apple.com/member ship/macosx.html]. Again, people interested the latest code or general Mac OS X development may wish to join one of the paid Developer Programs, which generally get free access to pre-release software (on CD) as well as technical support and other goodies.

    Enjoy!
    --
    ZP
    We only can learn from our mistakes.
    --
    ZP
    We only can learn from our mistakes.
    --K. Popper
  30. Re:The reason Apple has based MAC OS X on UNIX by jayc33 · · Score: 1

    XFree86 is being ported to OS X.

    BSD won't be able to run OS X apps, because of the
    gui and other closed-source libs, sure, but in
    case you haven't noticed yet, OS X is _PPC_ only.

  31. Re:MG's by bjohnson · · Score: 1

    Old one:

    Q:"Why do the British drink warm beer?"
    A:"Lucas Refrigerators."

  32. Re:Heh. Now MS Office will run on *nix! by Frymaster · · Score: 1
    I just built

    wow. How about you compare to a pre-built machine? It's exactly these false comparisons I was complaining about...

  33. Re:Ummm.. by the+eric+conspiracy · · Score: 2

    I figure the user interface in a year or two will be equal on Linux, BSD, BeOS, Mac and Windows.

    I don't think so. Microsoft has been trying since 1984 to come up with something as good as a Mac, and the best they have got is still ten years behind the Mac. There are huge, perhaps insurmountable problems with the heterogenaeity of the application base in both Windows and Linux that make it very unlikely that anyone will ever match the Mac look and feel.

  34. Re:Something left out.... by FunkyChild · · Score: 1

    Yeah, but there's a hell of a lot more difference between BSD and MacOS then there is between win16 and winNT..

  35. Re:Sports Cars, and Dump Trucks... by teflon007 · · Score: 1

    Bah my MG B looks good but runs like shit!

  36. Re:NeXTSTEP wasn't a good Unix either by craw · · Score: 1
    I heard the rumors that Sun wanted to licence the MacOS GUI. I also heard that other companies wanted to licence the NeXT interface. Then came X Window. There was also rumors about the revolutionary NeXT object oriented programming interface. These, AFAIK, were just rumors and chest thumping manipulatings.

    As I said earlier, this was in the midst of the UNIX war. I don't trust any of the manipulations that were done during that time. This backstabbing was the reason why UNIX fragmented. A common GUI would have helped. But the GUI war (that was only practical when workstation graphics matured) then reared its nasty head with the Motif/OpenLook division. NextStep would no have been adopted as the common platform. The PHB had already denuded themselves on the value to their inteface.

    I write this rant, but I'm in agreement with your central premise,

  37. Something left out.... by levendis · · Score: 3

    One important feature that got left out of the article is the "Classic" mode of OSX. It basically emulates MacOS 9, and does a damn good job of it (think WINE written by Microsoft, instead of a bunch of reverse-engineering hackers). This, to me, is one of the most impressive elements of OSX. Never before has an operating system vendor so completely been able to offer full backward compatibility.

    --
    ---- I made the Kessel Run in under 11 parsecs.
    1. Re:Something left out.... by msnomer · · Score: 1
      Never before has an operating system vendor so completely been able to offer full backward compatibility.

      Apple emulating the 68k chip on the PowerPC so that old software would run on new Macs is pretty amazing too. While Apple has orphaned machines on occasion, they certainly put a lot of effort into making things backward compatible without crippling things.

      --meredith

      --
      --meredith
      Sometimes a scream is better than a thesis
    2. Re:Something left out.... by be-fan · · Score: 2

      However, Win32 is derived from Win16. MacOS and BSD are completely different.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:Something left out.... by AndyS · · Score: 1

      This sounds broadly similar to "WoW", which is the NT way of emulating win16 apps. Indeed, the limitations on Classic apps (all running in the same process space) sounds very very similar

      (WoW = Windows on Windows)

    4. Re:Something left out.... by be-fan · · Score: 2

      Actually, I think that the reason that all Classic apps run in the same process space is because that's what the apps expect. It's probably not a limitation, but a requirement to make the apps work.

      --
      A deep unwavering belief is a sure sign you're missing something...
    5. Re:Something left out.... by Paradise_Pete · · Score: 1
      Well jeez - they always ran in the same processor space. How could it be any different now?

      -Pete

    6. Re:Something left out.... by TheInternet · · Score: 1

      Not as much effort as Intel and Microsoft have put into backward compatibility. (Lotus 1-2-3 R2 and Word 2.0 on Windows 2000 work great, despite the fact nobody uses them.)

      That's good and all, but Duke Nukem doesn't run on W2K. :)

      - Scott

      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    7. Re:Something left out.... by MrBogus · · Score: 1


      "Classic" is actually more like Win-OS/2 because it actually boots a virtual machine.

      "Carbon" is more similar to WoW (API translation to 'native' Cocoa calls.), although for I all know Carbon might actually talk directly to Mach/BSD too.

      --

      When I hear the word 'innovation', I reach for my pistol.
  38. Re:What about mach? by InfoVore · · Score: 1
    OK, MacOS X on the whole looks pretty nice, but there`s one thing I simply don`t understand: why are they using BSD on mach? I mean, I do not understand the benefit mach gives them.

    Pardon me while I get pedantic for a minute. No offense is intended.

    One thing that people keep forgetting about Apple is that they are a hardware company. Heck, even Apple forgot that for a while and almost died as a result. Since Apple is in the business of designing, building, and selling non-commodity hardware (lets face it, intel/AMD boxen are commodity items), they are in the position of being in complete control of how the box works. Which means everything in the OS and apps should be tweaked down as hard as possible to get the best performance, right?

    Wrong. Apple is in this for the long haul. Several times in their history they have had to completely redesign both their hardware and their software, while also maintaining that illusive requirement of Backward Compatability for the masses of Mac faithful (heck I know people whose primary home machine is STILL a MacPlus, and they are fellow techies!). That means that Apple is basically in a state of constant porting of their OS to whatever new hardware they decide to manufacture. Remember, Apple is trying to create a stable and flexible software system that supports their bread & butter sales: hardware. (yes, I know it is a bit more muddy situation than that, but that is closer to the truth than any other assessment).

    A microkernal architecture does make porting a little easier by abstracting the OS interface to the hardware. Yes it slows things down a little, but not that much. You also get lots of nice advantages. Think of it as contingency planning:

    - Apple might have to move off of the AIM PPC design to something else (a very real possibility if Motorola can't bump past 500mhz G4s very soon)

    - They might choose to attempt a raid on part of an Wintel/Lintel/Sun/SGI market segment (I doubt it, but they might) and need to port over to some other architecture while still maintaining code compatibility with the MacOSX main branch

    - They developed OSX with the promise that it would run on G3 machines or better (boy was there alot of grumbling about THAT. Mac people keep and use their machines a LONG time). Some of those machines are now 1&1/2 generations out of date (2+ years). It just makes it simpler to abstract not only the microkernal, but everything in the new OS that they can (which is what they have done)

    - They need to plan for the unknown. They don't know what the future holds techwise. They want to make sure they can maximize their response as quickly as possible (say for example if USB2 supplants Firewire/IEEE-1394).

    There are lots of other good business reasons as well. One is that by abstracting to a microkernal, they don't have to exhaustively test every stinking OS upgrade on every type of OSX legacy machine. They can instead pound the heck out of their currently manufactured machines and then do restricted testing on legacy machines. Since the microkernal is identical on the machines and the microkernal gets exhaustively tested on all machines (a much smaller job), it eliminates a whole class of hardware unique bugs. That saves both time and money testing as well allows them to bring more features to market faster.

    Another reason is security. How many potential security holes can you plug by not letting ANY software, including the OS, touch the hardware? The answer, alot. Apple has a tradition of this sort of abstraction. How many older MacOS developers bypassed the ToolBox API to talk directly to the hardware, only to find that in the next machine their software broke? The answer: many. If Apple tells you "don't rely on attribute X being there in the future" then don't expect it to be there. Additionally, the various flavors of BSD are considered by many to be the most secure OS on the planet. Using a microkernal architecture to take away potential hardware backdoors should make it even more secure.

    Anyway, that is my assessment of why they chose the microkernal direction. I could easily be wrong. It could be something much simpler than that: we have this NeXT code, lets use it.

    Cheers,

    IV

    --
    "These laws they're passing won't even compile anymore, let alone execute." - anon
  39. Re:Come on... by um...+Lucas · · Score: 1

    I haven't played with a DP at all, but file extensions on the Mac kinda scare me. I hope you weren't insinuating that file type/creator codes are on their way out.

    I've always relished the type and creator codes, because files would essentially remember what program you used to create them. If you downloaded a page from the web and double clicked it later on, it'd open in Netscape. If you double clicked another .html file, but that one having been created in dreamweaver, meaning that you're probably writing the page, then it'd open in dreamweaver. The same with almost everything else.

    I want the old/current filesystem... none of this .xxx stuff.

  40. What is a MAC? by kruczkowski · · Score: 1

    A MAC is a computer for people like my mother. Someone who do NOT recompile there kernel on a daily basis. Please just calm down If apple does not include a compiler into there OS. That's why there is FTP, to download one.

    --
    hmm... for fun I enjoy launching DDoS attacks against 127.87.42.5
    1. Re:What is a MAC? by xornor · · Score: 1

      How do you get any work done if you are always recompiling your kernel??

  41. Re:No by Mark+J+Tilford · · Score: 1

    Actually, I think that MS did port NT to the mac, but it never sold well.
    -----------

    --
    -----------
    100% pure freak
  42. Re:My take on QuickTime by AFCArchvile · · Score: 1

    I'll sum up my opinion on QuickTime in one sentence: I love the codec and the format, but I hate the player.

    --
    "Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
  43. Re:Apple pie by Graymalkin · · Score: 1

    No way really?

    --
    I'm a loner Dottie, a Rebel.
  44. What kind of file system does it use? by weave · · Score: 3
    It's been a long while since I mucked in the Mac universe, but this will probably bring me back.

    But I am curious. What about the file system? Do Macs still have separate resource and data forks with each file? Will this be supported by the file system in OS X? What about the app and creator 4-byte codes (which are actually in the resource fork). Will that be used, or will they move to the horrible filename extension crap that UNIX and DOS world suffers under? :-(

    1. Re:What kind of file system does it use? by zephc · · Score: 1

      The default is HFS+ (4K block size) which has a 32 char per node name maximum (but unlimited folder depth :) ) and i think semi-unix like permission scheme, but you can also use UFS :)

      ---

      --
      "I would say that 99 per cent of what my father has written about his own life is false." - L. Ron Hubbard Jr.
    2. Re:What kind of file system does it use? by pyrotic · · Score: 1

      You can choose UFS or HFS+. HFS+ already has support for unix style permissions. The only "significant" filenames are the . files, like .htaccess. Folders can be executable (i.e. they can call executable programs), which means you can have a folder with 3 executable resouces for x86, PPC and Sparc, with all the libraries/multilingual versions contained together. Just like next. No more looking though /usr/lib trying to work out if...

    3. Re:What kind of file system does it use? by TheInternet · · Score: 2

      The default is HFS+ (4K block size) which has a 32 char per node name maximum

      I think you're thinking of HFS (without the plus). HFS+ is capable of much longer filenames, but Mac OS 9 just doesn't utilize them.

      - Scott

      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    4. Re:What kind of file system does it use? by zephc · · Score: 1

      ah yes i seem to remember hearing about that once... ah well, macos x would i assume, in which case i will have no more filename probs in about 2 days :)

      ---

      --
      "I would say that 99 per cent of what my father has written about his own life is false." - L. Ron Hubbard Jr.
    5. Re:What kind of file system does it use? by Malichus · · Score: 1

      But I am curious. What about the file system? Do Macs still have separate resource and data forks with each file?

      Yes.

      Will this be supported by the file system in OS X?

      The OS X filesystem is HFS+, the same filesystem used by Mac OS 8.1 through 9.0.

      What about the app and creator 4-byte codes (which are actually in the resource fork). Will that be used, or will they move to the horrible filename extension crap that UNIX and DOS world suffers under? :-(

      Those are also supported, although filename extensions are also checked as a fallback and to support operaton on metadata-less filesystems, such as UFS (which is fully supported by Mac OS X) or most NFS installations.

      --
      - Mali
    6. Re:What kind of file system does it use? by po_boy · · Score: 2
      ...the horrible filename extension crap that UNIX and DOS world suffers under?

      You mean like /usr/share/magic ?

  45. Mac OS X on Intel by mutzinator · · Score: 1

    Many of you posting on the subject of Mac OS X on Intel seem convinced it will never happen. It may happen for the following reasons:

    1.) the traditional argument about why Apple does not release a version of its operating system is that it would kill its hardware sales, and as a result, its revenue sream would dry up and it could not survive long enough to live on software alone. This used to be true. It is not true anymore.

    Why? consider the traditional reason to buy a macintosh. the operating system was Apple's crowning jewel and the primary motivator for its sales. This is not the case anymore. Between its technical limitations and various incompatibilities (hardware, software...) and the ease of use of windows (ok, not as easy as the mac, but not too far off) the MacOS is not the driving force behind Apple's sales.

    The driving force behind Apple's sales is its innovative hardware designs. Today, people buy a mac because it looks so damn cool. If the iMac (or cube, tower, etc) were running windows, people would buy it. If people can get the Mac OS on a white box PC, there will still be many many people that purchase iMacs and Cubes for style.

    2.) The other thing preventing Apple from making a major push on to the PC desktop is the sheer breadth of hardware available on the PC platform and driver support. Delivering the level of compatibility that microsoft does with windows would be a monumental effort.

    This is why Darwin exists. Apple hopes that the OSS process will apply to its darwin and individual developers will scratch their respective itches and bring breadth to darwin's hardware support.

    This is where we come in. If we want to make OS X on Intel a reality, it is 90% in our hands. If we start scratching some driver itches, OSX/Intel will become technically feasable.

    If the day comes when OSX/Intel is feasable, it will be in Apple's hands to actually deliver it. That much is beyond our control. But if you would like to see this, start looking at darwin. Subscribe to the developer mailing list. When the intel installer is available (currently its a real pain in the ass to get it installed on intel) throw it ona spare machine and check it out.

    Come on, this is what OSS is all about. :^)

  46. Duh! by Andrew+Cady · · Score: 1
    GNU's Not UNIX because it is not closed comercial source code. It's free and you are it's master. GCC, G77, find, and the rest are all great gifts.
    That has nothing to do with how GNU got its name. GNU's not Unix(tm) because Unix(tm) is trademark AT&T/Bell, and without a license from AT&T/Bell (which GNU does not have) it would be illegal to say GNU is Unix(tm), even if it was Unix(tm), which (of course) it is. See, it's funny: laugh. :)

    As to the original poster's comments: if Apple had used their own proprietary compiler, then yes, it would have been sufficient to include that rather than gcc. However, they didn't use proprietary tools, they used GNU, so GNU should have been the tools to include (actually, they apparently used some proprietary tools in addition to GNU, but nevertheless, it definitely would have been better if GNU had been included, as well as the proprietary tools. But apparently, they are available through a free download, so it's somewhat of a non-issue, except that the ability of newbies to explore and learn programming has been somewhat inhibited).

    1. Re:Duh! by gig · · Score: 1

      > the ability of newbies to explore and learn
      > programming has been somewhat inhibited).

      Also, the requirement that newbies keep dev tools on their systems, download automatic updates for the same, or worry about a cracker using the compiler to take over Mom's Web and email machine has been severely inhibited.

    2. Re:Duh! by Andrew+Cady · · Score: 1
      Also, the requirement that newbies keep dev tools on their systems, download automatic updates for the same, or worry about a cracker using the compiler to take over Mom's Web and email machine has been severely inhibited.
      Your comment about a "cracker using the compiler to take over Mom's Web and email machine" is so absurd that you almost seem to be a troll. Nevertheless, I will play the odds, assume you are genuinely that clueless in matters of computer security, and give a serious answer to your one almost-valid criticism, i.e. "the requirement that newbies keep dev tools on their systems". Of course the solution is obvious: simply have the installer refrain from installing by default programs that are not likely to be used by most people. Now, it may be the case that development tools could not fit on the disc. This would be a valid criticism, but I doubt it is actually the case.
  47. True, this is damn cool! by Paradox · · Score: 1

    I fully agree. Apple has finally gotten off their ass and "Thought Different" for the first time since their shining pinnacle of glory back in the beginning.

    This OS is basically what Be strove to be, UNIX for the rest of us.. but it's not just for the rest of us. It's the real deal here folks. At the same time, we get a nice (themeable, did you know that? Macs went themeing many years ago with Kagi Software's Kaleidoscope) GUI and some good graphics performance. Ask anyone whos serious about *NIX, "What's wrong with *NIX?" and they'll say "Xwindows" right off the bat.

    So now we have the best of both worlds here. I for one, am shelling out the cash for dual 500mhz G4 as soon as I get my next paycheck. The hardware is better, and now the OS is better too. What more reason do you want? You don't even need to settle for a 1 button mouse!

    Just my rant.
    - Paradox
    Man of the C!!!

    --
    Slashdot. It's Not For Common Sense
    1. Re:True, this is damn cool! by TheInternet · · Score: 2

      Macs went themeing many years ago with Kagi Software's Kaleidoscope

      Actually, Mac OS 8.5 and higher has built in theming. Apple just never publicized how to make themes (or released any on its own). Some people did some reverse engineering magic and figured it out, though.

      The hardware is better

      Oh, no. I sense a flameware coming. Let's preempt this and say that Apple hardware has some great advantages, but x86 is probably a bit cheaper on average and better for hacking around with.

      - Scott


      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
  48. Okay, the metaphor sucks, but... by TheInternet · · Score: 3

    In terms of size and performance, UNIX installations can be small and nimble compared to MacOS X, which has to support a lot more "stuff".

    I agree. Particularly true in devices like Tivo. The author's metaphor is broken.

    In terms of software architecture, MacOS is a mess and a dumping ground of legacy technologies: microkernel, UNIX personality, Objective-C, Java, MacOS ROMs, etc.;

    I don't really agree with your assessment. There are only two real APIs to be concerned with for Mac OS X: Carbon and Cocoa. Carbon is a cleanup of Mac OS libraries so that old software still runs. Cocoa is a combination of OpenStep's Objective-C and Java. The reasoning for the inclusion of the BSD layer should be obvious. MOSX even comes with built-in Java 2 support. To the best of my knowledge, nobody else is doing that.

    Nothing here is too ridiculous. People would be upset if any of this was left out. In fact, one could argue that deciding which Linux environment to develop for (GNOME, GTK) is more of a hassle. Not to mention all the basic services that X is lacking (or whoever is supposed to take care of fonts, printing, graphics, color correction, etc).

    no design or taste there

    I'm sorry, but I just don't feel Linux has much to say to Mac OS X in terms of design and taste. If you use the software, you'll realize this stuff has been very well thought out, and this is just the beta. Look for, example, at the fact that the configuration are XML-based, and are modified with an XML GUI front end. Linux would do well to learn from this. Consitency is certain an area where Linux could grow.

    In terms of appearance, there are plenty of pretty UNIX GUI interfaces.

    Pretty and intuitive are different things. Enlightenment is pretty (not as pretty as Aqua, though), but not intuitive. And frankly, that's not really E's fault as much as a function of that fact that it has to remain compatible with the way *nix is setup. Mac OS X does not.

    MacOS X, with its consumer market share, may be an OK compromise for people who want UNIX reliability and some kind of consumer-oriented system. But I don't think people have been holding their breath for this

    Hmmmm, even just reading slashdot posts (largely an Apple-hostive environment), I would think the opposite. Very interesting comments have also come from Carmack and other people at Id.

    MacOS X isn't salvation for the UNIX users of the world, it's salavation for Apple: without it, the company would not have a competitive product at all.

    I agree that Apple needs this product badly, but if you really want the Unix userbase to grow (in other words, anything that's not NT), than take a hard look at MOSX before you make sweeping generalizations. You don't have to like it if you don't want to. Heck, Linux might even learn a thing or two from it.

    - Scott

    (I've used/administered SunOS/Solaris/Linux/Mac OS X/Mac OS X Server and many others)

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
    1. Re:Okay, the metaphor sucks, but... by TheInternet · · Score: 1

      Sorry for all the mispellin.., misppelli... mistakes in that post, btw. It's late.

      - Scott

      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    2. Re:Okay, the metaphor sucks, but... by be-fan · · Score: 2

      BeOS is doing Java2 as well. In fact, so is Caldera LTP (Linux technology preview.)

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:Okay, the metaphor sucks, but... by zephc · · Score: 1

      lets see: a crappy backslashing OS and a vaporous programmiing language that can run untrusted yet still talk directly to the OS

      OR

      a unix-based OS with a clean GUI, great development env. and two really nice, very REAL programming languages

      The choice is yours... I've already chosen... I bought a G4 Cube :)

      ---

      --
      "I would say that 99 per cent of what my father has written about his own life is false." - L. Ron Hubbard Jr.
    4. Re:Okay, the metaphor sucks, but... by jetson123 · · Score: 2
      I'm sorry, but I just don't feel Linux has much to say to Mac OS X in terms of design and taste.

      Neither do I (did I say anything like that?). But the comparison by the author was not between Linux and MacOS X, the comparison was between UNIX and MacOS X. UNIX (meaning, what the systems research lab at Bell Labs developed) was consistent, well designed, and clean.

      UNIX started from scratch and developed a few novel paradigms that worked well for its user base at the time. If only Apple had done the same with their next generation OS. Instead, Apple did what they have always done: get a bunch of technology from other companies and market the hell out of it. Yes, it is still better than Windows NT, but that doesn't make it much less disappointing. For true innovation, we'll apparently have to look elsewhere.

    5. Re:Okay, the metaphor sucks, but... by daviddennis · · Score: 2

      The classic Slashdot user's problem is the tricky question of, "What should my artistically-inclined girlfriend who doesn't want to learn computers use?"

      Or, for that matter, what should I use when I want to take off my programmer's hat and use Photoshop or Final Cut [video editing package] or even a word processor?

      True, Gimp and StarOffice and friends are here and making some inroads, but even there the ugly fonts and bad printing are a royal pain.

      What MacOS X really does is make it possible for us to be able to sincerely and wholeheartedly recommend a solution that actually works for our friends without making us wince.

      I think it's fantastic, personally. I have a dual G4/450 right here just waiting for the new beta (which I've ordered).

      D

      ----

  49. Re:you're referring to my quote. by AFCArchvile · · Score: 1

    I thought of that one (adapted from a Jeff Goldblum line from Jurassic Park) because I was sick of software engineers coding stuff, "just because." One of my blaring examples was someone posting in the "Open MPEG-4 Contest," putting in a comment called "Write it in Java." Take a look at my reply to that. I think that my reply embodies my motivation behind my quote.

    --
    "Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
  50. Re:Sports Cars, and Dump Trucks... by Lowdown · · Score: 1

    um...you didn't know i guess that MG's are notorious in the auto community for constantly breaking down and being just generally impossible.
    sure are great looking though.

  51. Re:No by um...+Lucas · · Score: 1

    no... it actually took a bit longer for the emulation performance to catch up to 68k performance...

    1st generation 6100/60, 7100/66, 8100/80
    2nd generation 6100/66, 7100/80, 8100/100, 8100/110
    3rd generation 7200/75 + 90, 7500/100, 8500/120, 9500/120, 9500/132

    The first powerPC macs to beat out the Quadra 840AV in 68k performance were 604/PCI based machines, which didn't arise for at least (i'm guessing here - 2 years) after the NuBus PowerPC's.

    If they migrate their OS anywhere from the PowerPC, let's hope they go to Alpha's...

  52. Re:NeXTSTEP wasn't a good Unix either by skoda · · Score: 2

    Hear Hear!
    I spent three summers and academic years programming both cubes & slabs, B&W and color, as an undergrad. Those machines were lucious.

    I'm a PC guy now, but I'm hoping OS X is good enough to lure me away.
    -----
    D. Fischer

  53. He obviously values appearance over substance by A+nonymous+Coward · · Score: 2

    Only a Mac fanatic would ignore the working guts in favor of the cosmetic appearance. I have no knowledge of the working guts of any MacOS. It could be a beautiful design for all I know. But his whole approach is based on the GUI. That's like saying a spartan sports car is crap because it hasn't got fine Corinthian leather like his bloat barge rolling down the freeway. I know which one I'd take.

    --

  54. Re:Heh. Now MS Office will run on *nix! by loglan · · Score: 1

    Where are all the moderators?

  55. Re:Come on... by Enoch+Root · · Score: 1

    ThAT wASn'T ME I cAN bE StUPiD WIThoUT pOStING AnonYMOUSlY

  56. Separate GUI from system? by Fervent · · Score: 1
    One of my computer professors (who I didn't think quite understood MacOS X) said the GUI for the system is not separated from the underlying kernel in a way that X Windows is. That is, if the GUI (or new finder) crashes, the whole system will go down.

    Is Aqua just another kind of window manager?

    --

    - I don't care if they globalize against free speech. All my best free thoughts are done in my head.

    1. Re:Separate GUI from system? by be-fan · · Score: 2

      Quartz=X (more or less)
      Aqua=WindowMaker.

      Plus, you have to note that Quartz is absent from Darwin, (the underlying kernel and servers.) Do you think Apple takes Quartz out of Darwin for each Darwin release?

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:Separate GUI from system? by zephc · · Score: 1

      "Is Aqua just another kind of window manager?" kinda. What they mean by not seperated is that i guss it has a pretty low run level. also, Aqua is the look n feel for all the new system widgets, the window manager, and to an extent, the Finder and the Desktop experience.

      ---

      --
      "I would say that 99 per cent of what my father has written about his own life is false." - L. Ron Hubbard Jr.
    3. Re:Separate GUI from system? by TheHornedOne · · Score: 1

      He is entirely wrong.

  57. MacOS X is just what Linux needs. by ameoba · · Score: 3

    Just the other day, I was reading the infamous Halloween Memorandum that MSFT released. (In case you don't know, it's a briefing for MSFT execs. on the OSS movement, with a particular focus on Linux). While, frightening in many ways, it brings up some interesting points about OSS, one of which in particular is that most successful OSS projects start out trying to recreate existing software.

    While this replication may be viewed by some as a lack of creativity, those with an engineering backround will see the strength and resourcefulness of it.

    As any introductory engineering text will tell you, the key to a succesfull, manageable project is having a well defined product specification. Replicating an existing product allows the OSS developer to focus on the early organization of the project, as opposed to fiddling over details such as the provided feature set (not to mention the lack of deadlines imposed by the financial side of things).


    If Apple can make a marketable, user friendly Unix-based operating system, what's to stop us from doing the same? If nothing else, it will be an excuse to get rid of X Windows for good.

    Apple's hit some major points with MacOS X, primarily of which is the inherrent strength of Unix, this is something the OSS community already knows about. The big thing here is that where Linux has been fighting to stay truthfull to the existing codebase, and continuing to use Xwin, OS X threw it away.

    What's to stop somebody from developing a Linux Distro that mirrors OS X? We've been strugling for years to find the "Linux your mother could use", and Cupertino has shown it to us. All it takes is getting rid of the kludge that is Xwin, and comming up with a decent GUI (Speaking of, what ever happened to the Berlin project? I can't find any real info on it...) and some user friendly config tools.

    As a bonus, we could engineer the new GUI to compatable with the Cocoa/Aqua APIs, allowing for source level compatability between the two systems, finally making Linux development justifiable to a large number of commercial software companies. Wham, two birds dead, and we've still got more stone to go.

    Where right now, Linux is still the domain of 'geeks' (as most of the world considers those who can use a CLI), we wouldn't just be making the system 'user friendly enough' for mother, this might finally make Linux the user-friendly choice.
    If linux drops the ball on this, there's always the Hurd, which, might arguably be a better choice for this than Linux, as both the Hurd and OS X are based upon the same micro-kernel...

    Of course, with big names like IBM and SGI pushing Linux, I'm suprised this hasn't happened yet. Perhaps this is what Sun had in mind when they started their 'Gnome Foundation'...

    --
    my sig's at the bottom of the page.
    1. Re:MacOS X is just what Linux needs. by zephc · · Score: 1

      "What's to stop somebody from developing a Linux Distro that mirrors OS X? We've been strugling for years to find the "Linux your mother could use", and Cupertino has shown it to us." well really, FreeBSd your mother could use :) "As a bonus, we could engineer the new GUI to compatable with the Cocoa/Aqua APIs, allowing for source level compatability between the two systems" The GNUStep project is working hard on that now. gnustep.org

      ---

      --
      "I would say that 99 per cent of what my father has written about his own life is false." - L. Ron Hubbard Jr.
    2. Re:MacOS X is just what Linux needs. by po_boy · · Score: 2
      What's to stop somebody from developing a Linux Distro that mirrors OS X?

      Perhaps Apple would. I seem to recall some kind of lawsuit or something relating to an Enlightenment theme (perhaps called aqua) that looked a lot like a Mac OS interface. I don't remember how or if it was settled.

      Anyone recall what I can't about this incident? Given the little that I can remember, I can't find any related references.

  58. Re:Prices by loglan · · Score: 1

    Actualy, if you look, ALL the G4 towers have gigabit Ethernet. From the single 400 to the dual 500.

  59. Re:No by tjb · · Score: 1
    big endian

    little endian

    big problem

    Honestly, this isn't that big of a deal. At work, we keep all of our driver/firmware/host code in the same files regardless of endian-order through conditional compilation, and adjust our makefiles accordingly. I wouldn't doubt the Mac guys did the same, you know, just in case :)

    Any place you have assembly language, however, this could be a royal pain in the ass. But then again, you're porting to a *completely* different architecture, so its a pain in the ass regardless.

    --The Timdog

  60. Re:Does Mac OS X have package management? by pyrotic · · Score: 1

    Yup. They've used the Debian system.

  61. $800 iMac by TheInternet · · Score: 2

    Or did you actually think for a second that $800 for the lowest end of the entry level is cheap?

    I didn't say "cheap," but I think "reasonable" is a good word. Also, unlike many sub-$1000 machines, this price is not contigent on signing up for three years of ISP service. The iMac also has built-in ethernet, speakers and FireWire, and ability to upgrade to wirless networking for $100. Find me another $800 machine with those features.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
    1. Re:$800 iMac by TheInternet · · Score: 1

      I think the entry-level iMac is a good deal. However, I must correct you. The entry-level iMac does not come with FireWire nor is it "AirPort-ready". You'd need the $999 iMac DV for those features.

      You're right. My mistake.

      - Scott
      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    2. Re:$800 iMac by chrischow · · Score: 1

      yes it is airport ready i think, it tells you how to install it in the manual anyway (i'm using my new indigo baby now)

    3. Re:$800 iMac by dmarcoot · · Score: 1

      its a good bet that by time OS X ships installed on new macs, the entry level imac will have firewire and dvd

  62. Re:Ummm.. by Eponymous,+Showered · · Score: 1

    Bash (and more) for Win32 is at Cygwin, many thanks to Cygnus. I don't know how I'd live without the GNU tools and Perl on my Win boxen. I tried to show a co-worker how to do something the other day and he asked me to use cmd.exe instead of bash (he didn't have Cygwin). It simply couldn't be done.

  63. Re:Its not a server damnit by Tim12s · · Score: 1

    MacOS X could very easily be converted into a "server" mode by killing the GUI when "server" mode is required. Without the GUI, Darwin would be the raw unix running the various daemons.

    This GUI->Console->GUI relationship would allow less gifted system administrators to configure and secure their systems using a GUI.

    Without the extra GUI baggage, MacOS X would be the "perfect" server. All Apple would need are 4-way and 8-way PPC OS-X supported servers.

    I would speculate that OS-X would be a great contender in the small-business server market along with NT & W2K.

    I would also speculate that after an initial half a year of a stable MacOS-X rollout, they would release related server hardware making a Mac only environment more appropriate for companies. I would also imagine that their "server" hardware would be designed to be correctly stackable with appropriate power & monitor cables to make technical maintainaince easy.

    Considering i've only ever tinkered with Apple hardware, but have extensive use of FreeBSD servers, I am seriously considering purchasing an apple when OS-X is preinstalled.

    -Tim

  64. Re:Compiler/dev tool availability by TheInternet · · Score: 1

    So what are the cons?

    I believe I covered that in the original post.

    - Scott
    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  65. Re:Putting the Gnu back in OS X by Enahs · · Score: 1

    And to think, I thought that the Maximum Linux crew was too lame to even know what a compiler was.

    --
    Stating on Slashdot that I like cheese since 1997.
  66. And so what if it doesn't?... by neoevans · · Score: 1

    I mean really, does it matter if the OS doesn't port to Alpha, or Intel chips. So what if there isn't any GNU for all those too-much-time havin', Microsoft hatin', MP3 downloadin', late night hotline porn surfin', not satisfied with nothing... Sorry, I couldn't help it. Sometimes it just seems as though people, especially in the open-source community, aren't happy with ANYTHING that is released lately. As if these people actually helped develop anything other than a new way to hack a program into submission or force themselves past someone else's hard work so they can distribute it freely amongst one another. Don't get me wrong, I'm all for open-source. I just don't think people truly appreciate the effort that goes into an OS these days. Everyone and their best freind's dog was bitching about the stability of WIN2K and all of it's so-called bugs, it's like, "Can you do better? If not, shut up!" I was totally impressed with the final cut of that OS, and personally, I'll do the open source thing on my own time, but when it comes to Enterprise level OS's I'll let the big-boys handle it. And for OS X, I love the beta as I'm sure even the fellow who wrote the article of discussion did. But reading through the posts I have to say, "Do you think you can do better?" If anyone thinks so, please, release the source for such a marvel, I'm sure we would all love to pick it apart and trash all of your hard work...

    --
    "You are not a beautiful and unique snowflake."...Tyler Durden
  67. What's funny? by Enahs · · Score: 1

    You actually think we give a fuck whether or not *you* think it's funny.

    Now that's funny.

    --
    Stating on Slashdot that I like cheese since 1997.
  68. Re:Apple pie by Yardley · · Score: 2

    Yes really.

    --

    --

    --
    He lives in a world where those who do not run the client software of the omnipresent meme are unacceptable.
  69. Re:Andoveer tech support calls by Enahs · · Score: 1

    Hotline: Hello, Humor-Impaired Support.

    User: Hello? I spoofed a post on Slashdot because I didn't think it was funny, and thought if I did it in a funny way, that people would see how stupid the original post was.

    Hotline: *clears throat* And?

    User: Everyone's calling me a lame-ass son of a bitch because some people thought it was funny. WTF is wrong with people?

    Hotline: You're a lame-ass son of a bitch.

    User: *hangs up*

    --
    Stating on Slashdot that I like cheese since 1997.
  70. NeXTSTEP wasn't a good Unix either by sheckard · · Score: 1

    I'm not surprised that OS X isn't great as a Unix... it wasn't designed to be one. It was designed to be a desktop OS that just happened to use a *BSD base. I don't know if any of you have played around with NeXTSTEP, but it sucked as a Unix also. It was an *excellent* OS as far as the GUI went, and that's why everyone loved it... not because of it's *nixness. Things like no dev tools, nonstandard config files, no X, etc., don't do much for making *nix geeks happy, you know.

    1. Re:NeXTSTEP wasn't a good Unix either by TheInternet · · Score: 2

      I'm not surprised that OS X isn't great as a Unix

      This isn't what the article says. I've used Mac OS X DP4, and I think MOSX is a quite capable Unix, particularly when you grab an X server.

      - Scott

      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    2. Re:NeXTSTEP wasn't a good Unix either by cloudmaster · · Score: 1
      I wonder why no one seems to get the "it's people" reference... :)

      --Danny, who owns a color NeXT station, and thinks the unix behind it blows (but the GUI made up for that)

    3. Re:NeXTSTEP wasn't a good Unix either by Paradise_Pete · · Score: 1
      Sun offered $23 when AAPL was trading at $30 or so. Later AAPL fell to $13, making Sun's $23 offer look not too bad. This was all pre-Jobs II.

      -Pete

    4. Re:NeXTSTEP wasn't a good Unix either by kirwin · · Score: 2

      Funny that you mention that. A co-worker of mine was a 26 year veteran of Bell Labs (who incidentally, invented Unix), and was part of a team whose purpose was to plan for the replacement of Unix with NeXT. This did not happen, due to Jobs shady OEM dealings. Just think...if Steve Jobs wasn't so greedy, we would probably no longer have Unix.

    5. Re:NeXTSTEP wasn't a good Unix either by Anonymous Coward · · Score: 1

      FIRST RULE OF SLASHDOT DO NOT TALK ABOUT SLASHDOT.
      SECOND RULE OF SLASHDOT DO NOT TALK ABOUT SLASHDOT.
      THIRD RULE OF SLASHDOT READ THE DAMN ARTICLE.

      Like, duh, his only complaint is that there's no GNU tools included. You can bet there will be a third-party package as soon as OSX final is released.

    6. Re:NeXTSTEP wasn't a good Unix either by Schifter · · Score: 1
      Even if the 68000 that the NeXT was using at the time was cutting edge it was still not enough to run both client and server to run an X11.. graphics were still high load and anything that made it worse was a bad thing...

      Actually, the 68030 and 68040 CPUs that NeXT were using for their machines were plenty powerful for running X11. Before HP started using their own PA-RISC CPUs, they used m68k, and a `040 was amazingly fast at running X. I should know, I own a number of HP 9000 series 300 and 400 machines, and a 33MHz 68040 with 24MB RAM, running HP-UX 9.0 is plenty fast. (It's faster than a PA7100LC running HP-UX 10.20 in 32MB RAM, if that says anything.)

    7. Re:NeXTSTEP wasn't a good Unix either by craw · · Score: 1
      I don't quite understand your last statement. By the time NeXT was being established, UNIX had taken a life of its own outside the realm of Bell Labs. This was in the midst of the UNIX wars when many factors were trying to control the future of UNIX. By this time, AT&T had a lesser influence than some of the other computer vendors. I don't understand how Jobs could have had a major impact.

      I don't equate the influence of the evolution of the GUI with the surviability of UNIX in the context of the 80's. Furthermore, one should clarity when one says greedy with respect to Jobs. Jobs is driven by his ego. This is greed but not in the usual perspective of a monetary factor.

    8. Re:NeXTSTEP wasn't a good Unix either by cleanmachine · · Score: 1

      I programmed quite a bit under NeXTStep and thought it was quite good as a Unix, at least coming over from using Suns and DEC workstations. NeXTStep 3.0 came with a compiler, cc, which was based on gcc with modfications for Objective C support. (The objective C code was submitted back to gcc project.) It was quite easy to compile any GNU tools that were missing--I had a substantially easier time on the NeXT than on SGIs.

    9. Re:NeXTSTEP wasn't a good Unix either by Felinoid · · Score: 2

      I personally have never used a NeXT however when visiting the personal home page of the maintainer of lynx (at least at the time) he talked about his computers.
      One of his machines was a NeXT and he was proud of it.

      Let us step back in time shall we.. I used a 3B2/300...

      At the time the NeXT was created it was normal for Unix venders to charg extra for develupment tools (this being part of why the FSF exists) precompiled binarys of GCC for NeXT (and other systems) were available for download.
      This same problem existed on consummer desktop machines at the same timeframe and still exists for Windows..

      This explains why dev tools were not on NeXT (Why should NeXT offer dev tools if no one else will?)

      Many Unix machines were still text only... X11 was (and still is) designed to access a larg remote mainframe at the other end of a lan not the computer right infront of you. Part of the problem Linux has with graphics comes from this "big slothy layor"[1] (along with limited support from hardware venders)
      [1] Said on Geeks in Space
      Eventually Linux may need to dump X11 for a consummer style GUI instead of a server style Network graphics interface...
      Even if the 68000 that the NeXT was using at the time was cutting edge it was still not enough to run both client and server to run an X11.. graphics were still high load and anything that made it worse was a bad thing...
      So it made perfict sence to create a whole new GUI.

      NeXT makes a great Unix box for the 1980s.. like the 3B2.... and Sun i386...
      But a Sun i386 today sucks eggs... 3B2 is slothy and for all that NeXTs problems are not having dev tools or X11... I'd say thats surviving time pritty nicely...

      --
      I don't actually exist.
  71. Re:What about mach? by be-fan · · Score: 2

    The only reason that MacOS X uses the BSD on top of microkernel design is because NeXT did. There are far better ways to use a microkernel, namely splitting the servers up into different executables. That gives you one of the primary advantages over macrokernels, the fact that major pieces of code can be overheauled without paying much attention to other pieces of code.

    --
    A deep unwavering belief is a sure sign you're missing something...
  72. Intersting from the developer's download... by palndron · · Score: 1

    They have a beta for IPv6.

    --
    a man, a plan, a canal, panama
  73. Re:The ultimate irony. by Enahs · · Score: 1

    OK, it's Saturday. Save the logic humor for the week. :^)

    --
    Stating on Slashdot that I like cheese since 1997.
  74. Putting the Gnu back in OS X by Demona · · Score: 5

    Follow the instructions here to restore the Unix development toolkit to OS X.

    --
    Fuck Slashdot
    1. Re:Putting the Gnu back in OS X by rufo · · Score: 1

      Actually, Maximum Linux and MacAddict are both owned by Imagine Media, so I'm sure that there was permission involved, either given or explictly stated in the contract the original writer signed. Rufo

      --
      My English teacher once told me that two positives don't make a negative. Two words for her: Yeah, right.
  75. Office and MOSX by TheInternet · · Score: 2

    Office will only run in the Classic environment (RAM-hungry emulator running Mac OS 9) for about another year before Microsoft updates Office 2001 to be Carbon-compliant.

    Actually, I think they are skipping Carbon compliance and going straight for Cocoa. I could have misread, so don't quote me.

    Anyway, a good point to make is that even though Office will run in the Classic environment, it will probably still run significantly better and be more integrated than running Office 2000 on Solaris or Linux via a Win32 emulator. Plus, it doesn't have to run in a separate window.

    Emulation is never optimal, however.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  76. Compiler/dev tool availability by TheInternet · · Score: 5

    And while the arrival of the GNU tool set -- the mainstay of Unix development -- is inevitable, it's a shame that Apple didn't see fit to include it in the Mac OS X beta.

    The reason for this may be so that mortal users are not expected to actually compile their own software to use it. Example: Windows doesn't come with compilers, so virtually all Windows software (even Apache, PHP, etc.) come in binary form.

    From what I understand, the dev tools: Project Builder and friends (and even gcc, etc) will be available for free download from the ADC (Apple Developer Connection) site in October.

    I'm fairly confident that compilers, in one form or another, will be freely available.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
    1. Re:Compiler/dev tool availability by TheInternet · · Score: 1

      Perl is included in OS X, so the application could just use that as the scripting language.

      Or, if you're so inclined, AppleScript.

      - Scott
      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    2. Re:Compiler/dev tool availability by Chris+Pimlott · · Score: 2

      So what are the cons?

      If they do want to do development it's a great convience. If they don't, it's just 40 megs or so on their HD that doesn't get used.

    3. Re:Compiler/dev tool availability by MrBogus · · Score: 1

      The only con I can think of is beta-level applications that require you to change parameters in the source code and recompile.

      Of course, most Linux users nowdays use binary packages, so I can't imagine that source distribution would be real popular in the Mac user/non-programmer community.

      --

      When I hear the word 'innovation', I reach for my pistol.
    4. Re:Compiler/dev tool availability by phutureboy · · Score: 3

      The reason for this may be so that mortal users are not expected to actually compile their own software to use it. Example: Windows doesn't come with compilers, so virtually all Windows software (even Apache, PHP, etc.) come in binary form.

      Wide availabilty of free, quality development tools is one thing that's allowed Linux to skyrocket in popularity. If MacOS [7|8|9] had included a free copy of CodeWarrior (or equivalent) with each desktop, there would be a lot more software for the Mac today. Lots of people want to learn to program for their favorite platform but few are willing or able to shell out megabucks for the necessary tools.

      Dev tools don't have to be included in the default install, or even on the install CD, but making them easily and freely available can help ensure a platform's future popularity.

      I agree that end users should not have to muck with compiling software. Hopefully OS X has a decent binary package format.



      --
    5. Re:Compiler/dev tool availability by Moofie · · Score: 1

      That is an EXCELLENT point, and one that's underappreciated.

      From consoles to G4 cubes, developers aim for the least common denominator. If commercial developers (yes, Virginia, it's still OK to sell software, even on UNIX-based systems) can't rely on the user having access to a compiler, they will have to distribute it in a more user-friendly format. And that, folks, is what OSX is all about.

      --
      Why yes, I AM a rocket scientist!
    6. Re:Compiler/dev tool availability by Chris+Pimlott · · Score: 2

      Um... not as far as I see.

      You said it's not really necessary as binaries are the normal way of distributing software, and that development tools of some sort will be available.

      So what are the cons?

    7. Re:Compiler/dev tool availability by be-fan · · Score: 2

      The con would be similar to the cons in Linux systems. People start to assume that you'll have a compiler, and the binary versions have reduced functionality. For example, I keep seeing binary packages that aren't compiled with full, pentium level optimizations. For a lot of software, pentium optimized binaries aren't even availabe. It's partially the fault of Linux and it's "support those 486s!" mentality (seriously though, what idiot would run KDE2 on a 486?) but if compilers are common, the developers can just say, "oh, compile that package yourself." Also, sometimes you get stuff like ALSA, that doesn't even come in binary form except in specific distros (like mandrake).

      --
      A deep unwavering belief is a sure sign you're missing something...
    8. Re:Compiler/dev tool availability by spitzak · · Score: 2
      Actually it would be incredibly convienent for some application programs to be able to assume the compiler is installed. How about an applicattion that can convert "macros" into "plugins" (something I am working on right now).

      I kind of feel they botched it by not including this stuff.

      The average user does not ever need to see it. It can be there anyway.

    9. Re:Compiler/dev tool availability by TheInternet · · Score: 1

      Actually it would be incredibly convienent for some application programs to be able to assume the compiler is installed. How about an applicattion that can convert "macros" into "plugins" (something I am working on right now).

      That's a good pro, but I think the cons outweigh it.

      - Scott

      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    10. Re:Compiler/dev tool availability by int69h · · Score: 1

      MacOS 7-9 doesn't ship with a compiler on the install CD, but Apple has made Macintosh Programmers Workbench (MPW) available for free for quite a long time. It is easily and freely available from apple's ftp site.

    11. Re:Compiler/dev tool availability by Phroggy · · Score: 1
      From what I understand, the dev tools: Project Builder and friends (and even gcc, etc) will be available...

      From what I've heard, ProjectBuilder is basically a GUI front-end that actually calls gcc underneath, so of course gcc would be available. Apple has also submitted patches to gcc to the FSF. :-)

      --

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  77. Unix as a desktop by Tuzanor · · Score: 3
    Could it be that finnaly a company will show that UNIX(even if only in the basic sense with OS X), or even linux, CAN POSSIBLY make an exellent desktop enviroment.

    What category do we put OS X under whenever somebody divides who holds desktop market share. Does this fall uner Apple's OSes or UNIX?

    1. Re:Unix as a desktop by Tuzanor · · Score: 1

      Of course it must! :-) If we don't put it somewhere how can it be compare it to anything else? If we put it in a direct category we can more-so show that windows is dominating less and less(hopefully).

    2. Re:Unix as a desktop by Art+Tatum · · Score: 2
      Could it be that finnaly a company will show that UNIX(even if only in the basic sense with OS X), or even linux, CAN POSSIBLY make an exellent desktop enviroment.

      This already happened 11 years ago. Remember, Mac OS X is basically just a repackaged NeXTSTEP. Unfortunately, it isn't equal to NeXTSTEP.

    3. Re:Unix as a desktop by daviddennis · · Score: 2

      Depends on what kind of point you want to make with the statistics :-).

      But seriously, I'd keep it in the Apple column, simply because Apple developed it and people are going to be using it because it's the Apple OS, not because it's Unix.

      D

      ----

    4. Re:Unix as a desktop by Phroggy · · Score: 1
      What category do we put OS X under whenever somebody divides who holds desktop market share. Does this fall uner Apple's OSes or UNIX?

      Must it be categorized?

      --

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  78. Re:This is amazing... by SEAL · · Score: 1

    Just online? Shit... I'm still at work ;P

  79. How to get the gnu tool set... by e271828 · · Score: 4
    Here's a nice article from Mac Addict on how to grab the Unix tool set from Darwin.

    Also, Apple will release the developer tools to all online ADC members (free registration) in mid-October.

    1. Re:How to get the gnu tool set... by Pope+Slackman · · Score: 2

      Also, Apple will release the developer tools to all online ADC members (free registration) in mid-October.

      Maybe I'm missing something, but I don't see any free registration. Or is it only free if you've already paid the 'only' $400 developer tax?
      If that's the case, then I must say a $400 fee is NOT the way to get new developers.

      I'm considering developing on OSX, but not if it costs $400 for some GNU based tools.
      That's almost as expensive as Visual Studio...

      --K
      ---

    2. Re:How to get the gnu tool set... by Chops-Frozen-Water · · Score: 1

      but I don't see any free registration

      It's right here, and it doesn't require any money. Or see one of the previous posts about access through the Darwin project.
      --

      --
      The Future: Some assembly required; batteries not included.
  80. Re:No by gig · · Score: 1

    Before Apple bought NeXT, their short list of candidates for the "guts of the next-generation Mac OS" were NeXT, Be, Solaris, and NT. Bill Gates bugged Gil Amelio big time to go with NT, apparently. What finally nixed MS was that Gil felt that MS hadn't actually presented any good technical arguments ... any time an Apple engineer presented a sticking point like endianness, the MS guys just said things like "don't worry, we'll work that out, sign the contract". NeXT did well with Amelio because they came in and really detailed how their technology worked instead of talking only business.

  81. Re:Price of macs by jsmaby · · Score: 1

    There is more to a computer than its speed. Sure, good looks are nice to have, but I consider that secondary. What is it that makes a BMW different that a ford? It could very likely be that the ford gets better mileage, can go faster, seats more people, looks sportier, etc. Yet the BMW is `better', not necessarily in normal performance measurments, but in quality. The new fords are made of cheep components, put together in a cheep fation, so that they can be sold cheeply. BMW's are made with quality in mind, and the end product is something the driver can be proud of. Since I know next to nothing about cars, and even less about macs, don't take me too seriously. I think the idea might be about right though. One thing I can say, is that the new gateways are flakey. They do wierd things like stop responding for a few seconds, and crashing occationally with no reason. The CPU, RAM, etc tells me they should be good machines, but they left out the quality part, so the boxes are junk for my purposes.

    --

    Sometimes I've believed as many as six impossible things before breakfast.

  82. Price of macs by Christopher+Craig · · Score: 1

    Even figuring the fact that it's a $380 savings to go with a Mac initially you don't include the upgrade cost. When I upgraded from my PPro 200 to a PIII 750 it cost around $700, because all I bought was a new CPU, motherboard, and RAM. If I had upgraded my Mac it would have been $1549 for a brand new mac because I couldn't keep all of my peripherals. Admittedly this doesn't effect the average consumer, but it is a big deal to me.

  83. Ummm.. by Mr.+Flibble · · Score: 1

    For the whole of its existence, the Macintosh operating system has been a prime example of consistency and graceful design. And for the whole of its existence, the Unix operating system has been, um, not.

    Hey, hey! I beg to differ!

    That's like saying Sendmail is not graceful... Oh... Wait... ;)

    --
    Try to hack my 31337 firewall!
    1. Re:Ummm.. by scrytch · · Score: 2

      > I don't think so. Microsoft has been trying since 1984 to come up with something as good as a Mac, and the best they have got is still ten years behind the Mac.

      Apple is plugging "new" OS features like memory protection that even Microsoft had 8 years ago with NT. The sky is bondi blue in your world, isn't it?

      --
      I've finally had it: until slashdot gets article moderation, I am not coming back.
    2. Re:Ummm.. by JabberWokky · · Score: 2
      .
      For the whole of its existence, the Macintosh operating system has been a prime example of consistency and graceful design. And for the whole of its existence, the Unix operating system has been, um, not.

      Hey, hey! I beg to differ!

      Simply: cat essay | sed "s/design/user interface/g"

      It's okay. I figure the user interface in a year or two will be equal on Linux, BSD, BeOS, Mac and Windows. Then other aspects (stability, ease of upgrade, price point, industry standard) will affect the overall "user experience", of which UI *is* an important part.

      That's not to imply that a GUI is the only good UI. But I ran bash on my Win98 box. UI is slowly evening out between the various OSes. Look at Win2k's "stability" being touted.

      --
      Evan

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

      You said:

      It's okay. I figure the user interface in a year or two will be equal on Linux, BSD, BeOS, Mac and Windows. Then other aspects (stability, ease of upgrade, price point, industry standard) will affect the overall "user experience", of which UI *is* an important part.

      I say:

      Eh? I hope you're right, but I don't understand why then next year is going to be better than the previous 10. I'm going to go out on a limb here and say that very very little good engineering has gone into the user interfaces of publically available software since the introduction of the Macintosh. (with a few notable exceptions.)

      I hope I'm wrong, but we seem to be stuck in a rut UI wise. I hope that somebody can get something better going, but I certainly haven't been able to come up with anything. Here's hopin'!

      --
      Why yes, I AM a rocket scientist!
    4. Re:Ummm.. by Mr.+Flibble · · Score: 1

      It's okay. I figure the user interface in a year or two will be equal on Linux, BSD, BeOS, Mac and Windows.

      You are probably correct in that. But (IMO) the *nix community has to kill X off and build a new server from the ground up. Still, I am probably like you in that when working on servers I don't use a GUI, I don't need -or want- one. GUI's take too long currently for administrative tasks.

      But I ran bash on my Win98 box Bash for Windows? Cool! Where did you score that? The idea occured to me that it might be out there but I never actually thought to look. This will be a good addition to my Win98 workstation, which along with PuTTY will make 98 actually useful for me at work. Time to fire up google....

      --
      Try to hack my 31337 firewall!
    5. Re:Ummm.. by DjMau · · Score: 1

      The new server you are talkin about would be Berlin I believe.



  84. I disagree by TheInternet · · Score: 2

    the MacOS is not the driving force behind Apple's sales.

    I think that's a bit presumptious. I know the classic slashdot opinion is that the machines just sell because they're fancy colors, and while that may be a factor, it's not the only motivator -- particularly with long-time Mac fans.

    Today, people buy a mac because it looks so damn cool.

    That's nice and all, but that's know why I buy them. I buy them because it's the best tool for the work I do.

    If the iMac (or cube, tower, etc) were running windows, people would buy it.

    I disagree. In fact, one might look at the experimental industrial designs put out by other PC manufacturers (Compaq, Dell) that have failed.

    This is why Darwin exists. Apple hopes that the OSS process will apply to its darwin and individual developers will scratch their respective itches and bring breadth to darwin's hardware support.

    It's not just getting the drivers running on Darwin. Windows, in theory, has better driver support than anything else, but it still has tons of hardware/software compatibility problems. Apple would not be immune from this, and it would damage the brand name.

    - Scott


    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  85. Re:This is amazing... by Enoch+Root · · Score: 1
    Ouch. I sympathize.

    So, the PHB has sprung a last-minute graveyard on you?

  86. Re:A 'zippy roadster', yeah... right! by TheInternet · · Score: 2

    The part about the MAC ( pre os x i assume ) being a sport roadster and unix box being the pug-ugly workhorse

    I think the author was referring more to the end-user experience than the kernel.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  87. What the hell are you talking about? by DrEldarion · · Score: 1

    What kind of geek worth his salt is in bed at 6AM?

    True geeks don't even think about going to bed until about 8... geez.

    -- Dr. Eldarion --

  88. Re:don't forget to capture that output... by Prolog-X · · Score: 1

    Of course, perl -e 'while(<>){print pack("H32",$_)}' can be replaced with perl -ne 'print pack("H32",$_)'. The -n flag acts a while loop around the script.

  89. Re:And this is a step in which direction? by TheInternet · · Score: 2

    ... promting their newest software as being more functional because there are more ways to mess it up at the core level? That's how the lUsers will see it.
    Personaly, the less we say about the BSD backing on OSX, the better we'll all be in the long run.


    The BSD (or really, Mach) side of things is good for 1) performance 2) stability and 3) porting of server applications.

    Many iMac users won't care or know what BSD is.

    - Scott


    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  90. Capitalization by sql*kitten · · Score: 1
    Home directories, for instance, are stored in /Users instead of the more traditional /users or /home. Unix-native directories retain their classic lowercase status (/etc, /tmp, /dev), but everything else gets its formatting from the Mac side of the family.

    Actually, that's a NeXT thing.

  91. Re:Come on... by msnomer · · Score: 3

    Why is that? Many people would love a Unix with an elegant visual interface. Ease of use with the opportunity to get down and dirty in a shell sounds pretty good to me, as well as to folks who used gnome, kde, etc. I dream of the day when I don't have to keep switching back and forth between my Powerbook (graphics tools, authoring tools, etc) and my Linux laptop!

    --meredith

    --
    --meredith
    Sometimes a scream is better than a thesis
  92. Re:I'll bite.... by be-fan · · Score: 3

    1) One thing nobody mentions, is that to a person obsessed with typographics quality (take a look at my machine, all folders are perfectly capitalized and punctuated) those capital "X"'s in from of all the function names are very jarring. The "gl" in front of all the OpenGL function names aren't offensive because they are small. All the B's in from of the BeOS class names aren't offenseive because people are used to seeing capital B's. However, in your daily reading, you almost never come across a capital X in a word, and that is slightly jarring. A small point, but it basically totally ruins X. (Sarcasm) Well, at least they don't have lower-case function names.

    2) The programming isn't that hot either. True, I haven't programmed much, but it reminds me an aweful lot of Win32.

    3) It's slow. It's really really slow. Even XFree86 4 is slow. Really really slow. You'd think that KDE2 running on XFree86 4.0 and kernel 2.4 (test8) would be fast. But it's not. It's slow. Really really slow. It's so slow, I'm actually glad to be rebooting back into NT. The last time I saw a file manager take as long to load as Konqueror was when I tried Active Desktop on an old 486. Every program seems to have a built in 10-second delay before it shows up, and when resizing programs flicker and rubber-band like mad. It's not KDE's fault (GNOME does it too) and nobody ever said the kernel was slow, so it has to be X. (One day, try resizing Konqueror (on a 300MHz machine) in a folder with a lot of files. Watch the flicker and rubber-banding. Now try the same in WindowsNT. Very little flicker, no rubber-banding. Try it in BeOS. No flicker whatsoever.

    4) There are dozens of toolkits for it. What most people (toolkit writers) don't realize is that toolkits take RAM. It is silly that at any one time, I've got over 4 toolkits running concurently on my system. (TK, straight-X, GNOME, KDE, (and GTK and Qt if you count those as seperate, which in terms of size they are))

    --
    A deep unwavering belief is a sure sign you're missing something...
  93. The ultimate irony. by Black+Parrot · · Score: 1

    > Doesn't GNU stand for GNU's Not UNIX?

    GNU's Not Unix... but having GNU on board has become the ultimate test of Unix fitness. Too strange for fiction, too funny for the real world.

    And RMS can be taken up in fiery chariot now, his mission on earth completed.

    BTW, the union of "Unix" and "Not Unix" is "everything", so the combination should be pretty darn hard to beat.

    --

    --
    Sheesh, evil *and* a jerk. -- Jade
    1. Re:The ultimate irony. by yerricde · · Score: 2

      the union of "Unix" and "Not Unix" is "everything"

      OK, here's the UNIX web site.
      Here's the GNU's Not UNIX web site.
      Neither of those sites has everything.


      <O
      ( \
      XGNOME vs. KDE: the game!
      --
      Will I retire or break 10K?
    2. Re:The ultimate irony. by Black+Parrot · · Score: 1

      > A negation is not the same as the complement.

      Yeah. When you say something negative about someone, it's a negation. When you say something positive about someone, it's a complement.

      --

      --
      Sheesh, evil *and* a jerk. -- Jade
  94. MacOS X on Intel. by be-fan · · Score: 2

    You know what would be really cool? If somebody wrote a Quartz-like display layer for FreeBSD (replacing X.) With that and a little work on the GNUStep project, we'd have our own little (probably faster) version of OS X on Intel (and portable to Alpha or whatever.)

    --
    A deep unwavering belief is a sure sign you're missing something...
    1. Re:MacOS X on Intel. by TheInternet · · Score: 1

      You know what would be really cool? If somebody wrote a Quartz-like display layer for FreeBSD (replacing X.) With that and a little work on the GNUStep project, we'd have our own little (probably faster) version of OS X on Intel

      A solid idea, but I think there's a bit more to Mac OS X than OpenStep APIs and a display layer. ;)

      - Scott

      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    2. Re:MacOS X on Intel. by be-fan · · Score: 2

      Not really. There is a great deal of work done on making the GUI, and some work on polish stuff like making the file manager easy (like showing app folders as an executable) but the rest of the stuff is simply Quartz, BSD/Mach, OpenGL, and Quicktime. A FreeBSD/Quartz-like-layer would be MacOS X sans GUI, polish touches, and Quicktime.

      --
      A deep unwavering belief is a sure sign you're missing something...
  95. article references DeCSS-through-DNS! by Colbey · · Score: 1
    Well, I found it really funny that the article decided to reference the DeCSS-through-DNS thing that I've seen in slashdot comments a few times recently...

    I also find it interesting that it doesn't work anymore. Since I never really understood how it worked in the first place, this makes almost no sense to me. Anyone feel like giving me a quick DNS lesson on what's going on here?

    --Colbey

    1. Re:article references DeCSS-through-DNS! by happystink · · Score: 2
      don't be surprised, Greg Knauss has pretty much made a career lately of writing articles that are guaranteed to be linked from slashdot (ensuring readership), and this story submission was so obviously posted by him. Go back and read it, it's blatant.

      sig:

      --

      sig:
      See the "..for smart people" banners Wired runs here? Look elsewhere guys.

    2. Re:article references DeCSS-through-DNS! by Phroggy · · Score: 1
      The dig command with axfr specified contacts the DNS server and requests a transfer of the zone file for that domain. The data is in the form of a bunch of weird hostnames that all point to 127.0.0.1 (localhost). The rest of that is just stripping out extra DNS stuff and sticking it all together into a gzip file, which is then un-gzipped.

      Try this:
      dig @138.195.138.195 goret.org. axfr|less

      --

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    3. Re:article references DeCSS-through-DNS! by nevets · · Score: 2

      I got it to work with:

      dig @138.195.138.195 goret.org. axfr | grep '^c....*A'|sort|cut -b5-36|perl -e 'while(<>){print pack("H32",$_)}' |gzip -d > /tmp/p2

      The only difference here is I sent the output to a temp file. Becareful to cut and paste it correctly otherwise it won't work. It's also easier to keep it all on one line.

      Then I did...

      chmod +x /tmp/p2

      /tmp/p2


      And the DeCSS code appeared!
      Steven Rostedt

      --
      Steven Rostedt
      -- Nevermind
  96. Re:Its not a server damnit by FolkWolf · · Score: 1

    This is true. The way they accomplished this is nothing short of astounding. They took the best ideas of NeXT, which was the most usable UNIX, built some more stuff to make it more usable on top of that, took ideas from everywhere, and made what seems to be, from all descriptions, a great *usable* UNIX. Any person who is looking at making UNIX more usable has to look at this.

  97. Re:Of course the tools stink, it's a Mac. by SharxUK · · Score: 1

    Hmm. Apache. What else do you want apart from QuickTime? Let me get this right, we get Linux people complaining that it's not available, yet also complaining when it's the standard on another platform. You also seem to be forgetting that QuickTime is far more than a media playback utility. It underpins the whole OS, and that while the player is. at times, a piced of shit, the underlying technology is still amazing. The player is, of course, nothing more than a front end for the technology, and anyone who wanted to could provide a replacement, as happened a few years ago with "Peter's Player". The TCP/IP stack is the one from Darwin, which is based upon FreeBSD, so do something about it and put in a replacement into the CVS ( http://publicsource.apple.com ) rather than just complaining about it!

  98. Re:The reason Apple has based MAC OS X on UNIX by TheInternet · · Score: 2

    The reason Apple has based MAC OS X on UNIX

    Apple's Darwin team sort of answers this in the Darwin FAQ.

    Apple wants to regain their hold on anyone using mac hardware, instead of having ppl using ported linux distributions, as *everyone* knows BSD now natively runs linux apps and is far more secure than linux.

    I don't think Linux on PPC was a big factor. I don't think Linux was even really Linux actively used on PPC back in 1997 (when Apple bought NeXT).

    Also they are hoping to gain a larger user base as many people who use *NIX will be wanting to give their new user friendly OS which is actually unix a try..

    Certainly a factor.

    now as they have ported everything to BSD does this mean BSD will now be able to run their apps?
    probably not, you will need their own gui


    It's much more than the GUI. There's also QuickTime (intergral part of Mac OS), Aqua, Quartz, Carbon, Cocoa. I think the only thing out of that list that might work on BSD is Cocoa via GNUStep.

    this means you have no hope in running X apps on that

    There are several efforts underway for this, as other posters have mentioned. You could probably get xclock running today if you wanted.

    This would please me as their are a lot of mac apps out there which i would love to use on linux especially quick time.

    QuickTime is much more than an "app." It's an entire multimedia infrastructure.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  99. Re:The reason Apple has based MAC OS X on UNIX by TheInternet · · Score: 1

    Any X that winds up in there will be by the grace of Carmack.

    There are others doing this, including a commercial effort from Tenon, which is famous for providing Unix compatibility on the Mac.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  100. Re:The reason Apple has based MAC OS X on UNIX by ElMiguel · · Score: 1
    as *everyone* knows BSD now natively runs linux apps and is far more secure than linux.

    But the cause (Open)BSD is more secure than Linux is not the kernel; it's the applications. If you run Linux applications under BSD, then your BSD system is about as secure as a Linux system. And anyway, most security holes are caused by misconfigurations, and no OS can't protect you from them.

    I think that probably Apple chose BSD instead of Linux because of licensing, not because of security.

  101. Re:Come on... by ed+'g3' · · Score: 2
    OSX has extended the type / creator concept to cope properly with different file systems and the Internet.

    Any normal Mac file can still have type / creator information. On a HFS+ disk (the default disk format for MacOSX) this is held within the directory structure rather than the file itself. Different strategies are used on filesystems where this can't be done (such as having a document bundle - essentially a directory that looks like a document, with various bits held in differrent files inside).

    The real improvement is this. When a file comes from a PC, or UNIX source and does not have type / creator info within it, the OS is able to understand the extension. Hence .app and the rest of it. The OS can also recognise some filetypes by scanning the first few hundred bytes of the file against a set of templates. Any files starting %%pdf are acrobat files, or whatever. There was a great review covering all this, and a lot more, on arstechnica.

  102. Re:Heh. Now MS Office will run on *nix! by gig · · Score: 1

    > And for $1500 (us) I just built

    Yes, but how much would you charge to build one for ME?

    Of course, I want the thing to be quiet, so you'll have to build it without a fan. I can't leave it on all the time in my house if it's really noisy.

    And I don't want it to be in one of those generic beige boxes. Makes me feel like I'm a business man, or that I'm living in an office. Ugh.

    Of course, I want to be able to call you with problems for the first few months. I don't mind paying a nominal fee, like $35 or so per incident (may span multiple phone calls) later in the computer's life. I may call at inconvenient times, though.

    I also want you to keep track of all the driver updates for the computer you build for me and create a system whereby my computer can check if there are new ones and install them automatically (like Mac OS 9 does and Mac OS X will), and I want these updates to just Work. Not that Windows Update crap that you have to sign up for, and which installs useless MS apps that wreck your other apps.

    I also want you to stay on top of current events and technology and be ready with new stuff when I need it. Things like Gigabit Ethernet, 802.11 wireless networking, and FireWire. Tell me what it is, make it easy to use, and then show me how to use it.

    Building computers for yourself is a fine thing, and I used to do it, too (got tired of it and use a Mac now, though). If you want to do it, then fine, but spare us with comparisons of your own personal price point and Apple's. Please. I know you're good with a toolkit and wrist-strap, but you're going to have to do better than that in order to complain that Apple is overcharging.

  103. Corrections by TheInternet · · Score: 3

    Just think of it: the lack of ftpd and httpd

    Both come built-in. The former is Apache, btw.

    nothing for media playback except for the proprietary QT4 player (hopefully optimized for OSX)

    Download RealPlayer. Download Microsoft Media Player. Download Macster (for Napster).

    and a TCP-IP stack that's about as stable as a tall stack of dimes

    Uh, what? What makes you draw that conclusion?

    All of this adds up to an unpleasant unix experience.

    Doesn't really sound like you've used Mac OS X yet.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
    1. Re:Corrections by mduell · · Score: 2

      Just think of it: the lack of ftpd and httpd
      Both come built-in. The former is Apache, btw.


      I think you meant to say the latter not the former. :)

      Mark Duell

  104. Re:Does Mac OS X have package management? by sigmond · · Score: 1

    I seem to remeber reading that Apple was using some (or all) of the Debian tools for package management dpkg, apt, dselect. I don't have any firm information though.

  105. What about mach? by nikolas · · Score: 2

    OK, MacOS X on the whole looks pretty nice, but there`s one thing I simply don`t understand: why are they using BSD on mach? I mean, I do not understand the benefit mach gives them. Nobody seems to want to run two mach-based os`s at the same time, and on the other hand mach would help with porting the whole thing, but nobody`s going to port this os (+ GUI) anywhere in the near future. Can you enlighten me?

    1. Re:What about mach? by SEE · · Score: 1

      Because OS X isn't really a new OS, but NeXTSTEP/OpenStep 5. And NeXTSTEP/OpenStep was based on Mach and BSD, and has been ported to the NeXT, Intel, and now PPC.

      Steven E. Ehrbar

  106. Re:Heh. Now MS Office will run on *nix! by gig · · Score: 1

    Office will be Classic and Cocoa. No Carbon.

    MS said quite some time ago that they Carbonized IE (already shipping in Mac OS X Public Beta) and then decided to go with Cocoa for Office. I guess most of the Mac-specific work is building the interface, and Cocoa makes that really easy.

  107. Re:Of course the tools stink, it's a Mac. by uid8472 · · Score: 1

    Shame about the lack of gcc.

    Not entirely: If memory serves me right, the system cc is a fork of gcc with better Objective-C support, but a bit out-of-date; the last time I heard anything about it Apple was trying to merge it with the GNU version.

  108. Re:Did all of you forget? by gig · · Score: 1

    Mac OS X Server came out in early 1999. It's at 1.2 now. When Mac OS X is released, there will just be the one Mac OS X, though.

    You can think of it like this:

    Windows 2000 + Windows ME = the long-awaited "unified" Windows

    Mac OS X Server + Mac OS 9 = Mac OS X (the long-awaited "next-generation Mac OS")

    Both Microsoft and Apple are working towards having "one OS", and then adding more things on top for high-end versions. The future of Mac OS X Server will probably be as an add-on for the same Mac OS X being run as a desktop OS.

  109. No by TheInternet · · Score: 2

    Anyone know if Apple are planning a port to x86?

    This gets asked constantly. The reality is it would probably be pretty easy to get Mac OS X to boot on x86 hardware, but it wouldn't be a sound business decision for Apple for a variety of reasons. The main one is that Apple is a hardware company. Selling Mac OS X for x86 would put them smack up against Microsoft.

    Plus, you wouldn't have access to the existing library of Mac software. You'd only be able to run Cocoa apps.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
    1. Re:No by MrBogus · · Score: 1

      NT 4.0 was available for PowerPC PReP systems like the IBM PowerPersonal and some Motorola stuff, but was never compatible with Macintosh hardware.

      It could have been without much effort, but neither Apple or Microsoft seemed to want it. A latter unified PPC hardware standard called CHRP was introduced, but by then the non-Apple PPC market was pretty much dead. (Both IBM and Motorola had dropped their PPC PC lines, Microsoft had dropped NT/PPC, and Apple only partially supported CHRP.)

      --

      When I hear the word 'innovation', I reach for my pistol.
    2. Re:No by SEE · · Score: 1

      Oh, certainly. Backwards compatibility, the market, nonstandard devices, and other items are definite reasons why Apple won't do an x86 port. But endian-ness isn't really a barrier, which was the explanation I was addressing.

      Steven E. Ehrbar

    3. Re:No by great+throwdini · · Score: 2
      You'd only be able to run Cocoa apps.

      Cocoa apps?!?

      Cocoa apps!?!

      I go koo-koo for Cocoa apps!!!

      Sorry. Couldn't resist.

    4. Re:No by Frymaster · · Score: 2
      The reality is it would probably be pretty easy to get Mac OS X to boot on x86

      big endian
      little endian
      big problem

    5. Re:No by SEE · · Score: 2

      MacOS X is really a new version of NeXTSTEP/OpenStep, which already runs on x86. While a few new endian issues may have been added, it wouldn't be a "big problem" except when dealing with already-existing Mac apps. And since those don't run on x86 anyway...

      Steven E. Ehrbar

    6. Re:No by Mike_K · · Score: 1

      I don't think Apple would have a huge problem if porting to x86 only meant competing with Microsoft. Worst case scenario, nobody would buy MacOSX for x86.

      I actually think they could do well against Microsoft on x86 platform. One of the reasons Apple never took off like Microsoft did is because if you buy a Mac, you're stuck with MacOS (or some *nix, which isn't acceptable for most people). If you could buy an x86 machine with MacOSX many people would try it out. They can always buy Windows and install if over MacOSX.

      Real reason Apple doesn't want to port to x86 is because x86 hardware is cheaper and so Apple would loose their main business, which is hardware.

      My question is why didn't Microsoft port Windows to the Mac yet?

      m

    7. Re:No by plastik55 · · Score: 1
      True, however you have to realize that Apple has a HUGE user base that is largely ignorant of technical issues, and expects their already bought-and-paid for programs to continue working. The userbase values backward compatibility; this is why Apple didn't have a modern OS out five years ago.

      They pulled it off beautifully in the transition from 680x0, but that was because 680x0 was dying ( I believe it took all of 6 months before emulation on PowerPC was faster than the fastest 68040 Mac there ever was.) Migrating the user base to Intel would be a whole other can of worms, that would tend to annoy the majority of the users.

      --

      I have a positive modifier on Troll. When I mod someone Troll their karma should go UP!

  110. The reason Apple has based MAC OS X on UNIX by jjeff · · Score: 2

    Well the reason as i see it is...

    Apple wants to regain their hold on anyone using mac hardware, instead of having ppl using ported linux distributions, as *everyone* knows BSD now natively runs linux apps and is far more secure than linux.

    Also they are hoping to gain a larger user base as many people who use *NIX will be wanting to give their new user friendly OS which is actually unix a try..
    (hell i have never liked macs but want to try out their new macos X).

    now as they have ported everything to BSD does this mean BSD will now be able to run their apps?
    probably not, you will need their own gui which will come with a significant price tag, and of course this means you have no hope in running X apps on that.

    of course i could be wrong, maybe their gui is based on X or uses X libs in some way.
    This would please me as their are a lot of mac apps out there which i would love to use on linux especially quick time.

    --
    when everything is working perfectly.. BREAK SOMETHING before something else FUCKS up!
    1. Re:The reason Apple has based MAC OS X on UNIX by connorbd · · Score: 1

      There is no X here.

      There was never any X in NextStep/OpenStep/Cocoa either, for that matter. Any X that winds up in there will be by the grace of Carmack.

      /Brian

  111. Future tech support calls by joshv · · Score: 4

    Hotline: Macintosh Support hotline! How can I help you?

    User: Yeah, I am trying to use Perl to do some reporting on my apache access logs. But I have to recompile Perl to fix a bug in the regular expression matching, and there is no gcc installed on the system. What do I do?

    Hotline: Ok sir is the computer plugged in?

    User: Of course. (annoyed)

    Hotline: Well, that fixes about 50% of the problems we get here.

    User: But I just want to know how to install the GNU developer toolset.

    Hotline: Ok sir, could you reboot the computer?

    User: What the hell would that accomplish.

    Hotline: Sir, please.

    User: (pretends to reboot). Ok, rebooted

    Hotline: Wow, you have a fast machine.
    Did that fix your problem?

    User: *dialtone*

  112. I'll bite.... by Jeff+DeMaagd · · Score: 1

    What exactly is wrong with X windows again?

    I'll admit that just about everyone uses a toolkit on top of X windows for programming (for me, that's MESA, the OpenGL-like-yet-trying-not-to-say-open-GL-for-trad emark-concerns-3D-toolkit.

  113. Heh. Now MS Office will run on *nix! by James+McP · · Score: 1

    Ohh, I'm so tickled. I could run a *nix on a PPC-platform and have access to MS office natively. (yeah, I know, they'll make it OS-X tool-kit dependent)

    Heck, it's not like my desktop machine really needs all those "hard core" *nix features that Nextstep didn't have; that's what my LAN's server is for.

    Soon as GCC and the rest of the GNU kit are completely available I won't have any problems running a G4 OS*niX as my pretty desktop machine. Ooh, the option of running X+Gnome, OSX or even the upcoming Aqua. I'm just tingly.

    --
    I've been on slashdot so long I'm starting to get out of touch with the cool stuff if it ain't on slashdot.
  114. Re:Heh. Now MS Office will run on *nix! by Teancom · · Score: 1

    That is exactly the problem that mac-heads and wintel weenies run into: the mac people quote a price, the intel people counter with a home built, the mac heads complain "that's not a prebuilt", failing to realize THAT'S THE BLOODY POINT!!! You can't *get* a home built Mac, at least not easily, and that is why Mac hardware will *always* be higher priced than Intel's.

    Now, the flip side: you Intel weenies, THAT'S THE BLOODY POINT!!! Using standardized hardware from one manufacturer allows Macs to have a *much* better interface when it comes to installing/configuring hardware, and maintaining consistency. That's why Intel hardware will *always* be flakier/more difficult/bass-ackwards when compared to the equivalent Apple stuff.

    Now that I have offended everyone, I'll retire for the evening :-)

  115. Re:Yes, damn it, it's imperative by Paradise_Pete · · Score: 1
    just as all information should be free

    Yeah? What's your phone number? How much money do you make? How often do you masturbate? Come on, give us some of that free information.

    -Pete

  116. OSX at school by Count+Spatula · · Score: 1

    It's alright. I've got csh and vi and all the JDK tools necessary for doing my homework and programming, but it's a bit bloated and, well, it's a /Mac/. Still, the UNIX is nice to see on there, especially since my school's main servers are all run on Win2k. I just enjoyed seeing the look on the lab tech's face when I asked if I could copy .cshrc and alias my own commands. I don't want to be typing 'vi foo.java' all the time and then 'javac foo.java', not to mention the times I type 'ls -ral |more'.

    --
    -- Count Spatula: The Culinary Vampire "...because my cooking sucks."
  117. Are you are incapable of compiling them yourself? by gatkinso · · Score: 1

    ????

    --
    I am very small, utmostly microscopic.
  118. Java and one button by DigitalDragon · · Score: 1

    Java does support two buttons quite easily. So no worries about that. Now I enjoy working in JBuilder, and there having second mouse button is always a plus.


    --
    http://dtum.livejournal.com
  119. Re:On Apple II... by gig · · Score: 1

    > Back in the day when Apple was popular, Apple II
    > computers came with two flavors of Basic
    > interpreters (Integer Basic and Bill's Applesoft)
    > and a mini-assembler, along with instructions on
    > how to use them.

    That was also back in the day when a much higher percentage of users were also programmers, and there was no World Wide Web to make it easy to distribute tools from a Web site.

    These days, including AppleScript with the OS and asking people who want to go further into development to get the latest tools from a free Web site doesn't seem so harsh.

    Mac OS has a feature called Software Update that contacts Apple for a list of OS updates. Should every graphic designer and musician on the planet have to look at a list something like this:

    gcc 3.4a
    bash 7.1
    ProjectBuilder 5.2

    Every time they want to make sure their video driver is up-to-date?

    Imagine for a moment that Adobe suggested they include a few hundred megs of Photoshop in Mac OS X, waiting to be unlocked once you pay Adobe for it. That would actually be more useful for many current Mac users than including the developer tools.

  120. Re:Prices by gig · · Score: 1

    And Gigabit Ethernet is an option on Cubes, too. There will be lots of design shops with G4 towers as servers and G4 Cubes as clients. It's really going to revolutionize some workflows. Suddenly, all the big files that artists work with seem small when you're moving stuff around that fast.

  121. Re:Getting rid of Tcl/Tk and groff by be-fan · · Score: 2

    However, Microsoft doesn't make the YOU reformat THEIR documentation. If it did, it would catch hell from the press.

    --
    A deep unwavering belief is a sure sign you're missing something...
  122. Re:Heh. Now MS Office will run on *nix! by Snocone · · Score: 2

    And for $1500 (us) I just built

    Snort.

    For $12500 I could build a streetrod that would make a Porsche 911 huddle in a corner and beg for mercy.

    I'd rather just go buy the stylishly packaged and quite sufficient for my needs alternative, thank you very much.

    This is how a Mac user thinks. We're just not interested in being penny-scratching bottom feeders. You want to, hey good on you mate. Just don't ever think that you're going to make a Mac user do anything other than pity you.

    (Moderators: This is not flamebait. Ask your nearest Mac user. Troll, maybe :)

  123. Re:Mac vs x86 performance by cfish · · Score: 1

    The less application you have, or the less drivers you have, the better the stability. Hardware mp3 players NEVER crash and "boot" less then 1 second.

  124. Re:Does Mac OS X have package management? by gig · · Score: 1

    > I would be thrilled to hear that there is a real
    > package management scheme built into Mac OS X.
    > Is there?

    Nine out of 10 apps on Mac OS 9 just installs to its own folder and lives quietly within there, following all the rules so the user can move or rename the apps or folder if they want to. The 1 out of 10 that sprays files everywhere drives users nuts, and leads to some of the problems Windows has, except I don't think I've ever had Mac app A overwrite a library from Mac app B or from the system.

    Mac OS X uses "application bundles", similar to NeXT. They are folders containing everything an app needs to run, but they appear as if they are a single application file to the user. The user can move them around the disk, rename them, and interact with them by double-clicking, drag and drop, etc. Installing means just dragging the bundle from a CD to the hard disk, or decompressing an archive and then double-clicking the app, just like on Mac OS 9.

    The truly great thing is that the bundle has spots for binaries for multiple platforms, and for resources for multiple languages. So you can make one app bundle that will run on any Mac OS X machine, whether PPC or not, using the user's preferred language. The sytem just uses the files it needs and ignores the others.

    Also, the system has a central libraries folder, and if the libraries in the central folder are newer than those in an app's bundle, the system uses the newer ones.

  125. Re:This is amazing... by SEAL · · Score: 1

    Nah I don't really have a PHB. I work for a game company so I get deadlines from our publisher's milestones. Long hours but at least I'm having fun for the most part.

    I can think of better things to be doing on a Friday night, though. Tradeoffs... *sigh*.

    SEAL

  126. Re:Mac vs x86 performance by GandalfGreyhame · · Score: 1
    Right this moment I have more apps for BeOS on my computer than I do windoze. And you've never had an MP3 player crash? Try feeding it a corrupted MP3 file. While a computer will just gloss over it, the mp3 player crashes hard. -G

    Linux is only Free if your time is worth Nothing

    --

    Linux is only free if your time is of no value
    Be in Your Senses

  127. Office is going Carbon. Period. by Valdrax · · Score: 2

    Let's see. Do you (a) edit 5-10% of your Classic Mac API code to match the Carbon API and run natively on Mac OS X while still running on older Macs? or (b) completely reengineer the entire product suite to run on a 100% new API that doesn't share really much of anything in common with the original code base which is probably weighs in at several million lines of code? Oo! Oo! An API for which the preferred languages are Java and Objective-C, not C++?

    Errrr.... My guess MS is going for Carbon. I remember back in the days before Carbon when MS was reluctant to commit to moving to the native NeXTSTEP APIs (in Objective-C) for Rhapsody. These are the APIs that are now called Cocoa. When Apple announced Carbon, which is a new revision of the old Mac OS API set with all the crud removed, MS was one of the first supporters of the move. It's no wonder why!

    --
    If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
  128. Cross breeding penguins and dogcows by Ukab+the+Great · · Score: 1

    >What's to stop somebody from developing a Linux >Distro that mirrors OS X? We've been strugling >for years to find the "Linux your mother could >use", and Cupertino has shown it to us.

    Nothing, which is why I'm currently working on a linux distribution that incorporates essential ideas of mac interface design. I'm currently rewriting parts of gnome to make the stuff that looks like it was written by the folks in redmond look like the stuff written by the folks in cupertino. Then I'll throw it all into a nice distribution your grandmother can use

    1. Re:Cross breeding penguins and dogcows by TheInternet · · Score: 2

      Nothing, which is why I'm currently working on a linux distribution that incorporates essential ideas of mac interface design. [...] Then I'll throw it all into a nice distribution your grandmother can use

      That's a step in the right direction. However, I think the weak link will be the apps and support utils. It's good that you're making a Mac-like (or at least the good parts) distro, but I don't know how many other software developers have the same goal.

      It's a start, though.

      - Scott

      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
  129. GNUStep doesn't really get you there by TheInternet · · Score: 2

    GNUStep is your only hope...

    From what I understand, GNUStep would probably only help you run Cocoa applications. Most of the interesting stuff that exists today is written to Carbon. More Cocoa apps should appear as time goes on.

    However, even if you got something to run Cocoa apps, you still wouldn't have Quartz or QuickTime.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  130. Its not a server damnit by GiverOfLag · · Score: 2

    Of course MacOS X will never be as "good" as the other *nixs, it's not meant to be.MacOS X isn't meant to replace Solarise,OpenBSD,Linux,etc, its for the average user, those who don't know the difference between a cracker and hacker. IMO MacOS X is a step in the right direction,it dispells all the myths of *nixs not being able to handle the home market.Although I don't see it replacing Windows, Steve Jobs won't allow that, but it does show what can be done.It can only inspire the KDE and Gnome developers to make better products, and lead to widespread use of *nix on the desktop, and world peace of course :)

    1. Re:Its not a server damnit by CaptainAvatar · · Score: 1
      Yeah, and what a crock of shit MacOS is for serving. I have a MacOS 8.6 (was 9.0.4) server which controls an iMac lab. Damn thing crashes once a week (used to once every 1-2 days, until I downgraded AppleShare IP). I can't wait until MacAdministrator 2.0 comes out, then I can run the iMacs from our Solaris server(which only goes down when I tell it to!).

      Ever wonder why Apple use Solaris for www.apple.com instead of MacOS? It's a crappy OS for serving, that's why.

      --
      The real Captain Avatar is a fictional character, so I suppose he doesn't mind if I impersonate him.
    2. Re:Its not a server damnit by TheInternet · · Score: 2

      Of course MacOS X will never be as "good" as the other *nixs, it's not meant to be.MacOS X isn't meant to replace Solarise,OpenBSD,Linux,etc, its for the average user, those who don't know the difference between a cracker and hacker.

      I think you're jumping to a lot of conclusions. Just because Apple's main focus right now is designers, consumers and education doesn't mean that's the way it's going to be forever.

      I wouldn't really expect Apple to compete against Solaris anytime soon, but it can certainly evolve into a capable small-to-mid-range server platform with a little work. Heck, people have been using Mac OS (the non-Unix kind) as servers for years.

      - Scott


      ------
      Scott Stevenson

      --
      Scott Stevenson
      Tree House Ideas
    3. Re:Its not a server damnit by zfractal · · Score: 1
      I think as a server, it will do just fine as any other *nix that's out there. The foundation of OS X is basically NeXT which has been in use for years for some very specialized applications (I still remember working at a hospital where NeXT was used on radiology imaging servers).

      I'm a little more worried about it being a consumer OS - if you've used the Mac OS for any significant period of time (I'm not saying you haven't) you should know the reasons why.

      I believe this is why Apple keeps delaying the final release date of OS X - they still need to add some things to make it fundamentally Mac like - for example, being able to add a hardware driver to the OS by simply dropping a file into the system folder.

      I've used DP4 for a while now. For me, DP4 has been very stable, but coming from a Mac user experience, it's starting to look like Windows without the blue screen.

    4. Re:Its not a server damnit by kennylives · · Score: 1

      I wouldn't really expect Apple to compete against Solaris anytime soon, but it can certainly evolve into a capable small-to-mid-range server platform with a little work. Heck, people have been using Mac OS (the non-Unix kind) as servers for years.

      It seems to me that if MacOSX is as good a *nix as the article suggests, and that the GNU tools work properly, that MacOSX lives somewhere in the spectrum of low-end Solaris boxen.

      There are a number of similarities: Relatively expensive, but nicely done hardware that the OS is pretty closely tied to. Assuming MacOSX retains *nix-style uptimes - Long uptimes. Solid (if not stellar) performance. And so on.

      So, I see no reason that MacOSX couldn't quickly become some serious competition for Sun in the Ultra 5,10,(60 ?)range. Which, BTW, is the same place that Linux on modern X86 hardware seems to live as well.

      Actually, there is one reason I can think of: Apple doesn't push it in that direction. We've all seen some very curious blunders and missteps from them in the past. They've caught a wave, I hope that they can continue to ride it. Candy-coloured machines are interesting and all, but if they start pushing candy-coloured *nix boxen and everything that means... hmmm..

      This could become very interesting...

      --

      Where the value of X-Mailer: is the true measure of a man...

  131. Why the GNU system is "bloated" by yerricde · · Score: 2

    The UNIX® system is optimized for footprint (it originally ran in 1 MB machines IIRC). The GNU system, OTOH, is optimized for speed. This "use more RAM if it'll improve performance and/or simplicity" mentality helps counter copyright infringement allegations by UNIX system vendors against GNU system developers who have never read UNIX system code.
    <O
    ( \
    XGNOME vs. KDE: the game!

    --
    Will I retire or break 10K?
    1. Re:Why the GNU system is "bloated" by Anthony · · Score: 1
      It seems to me, that all GNU programs are optimized for flexibility.

      All general statements are crap

      Example 1) All the toolkits present in the average GNU system. Loads 'o bloat. However, very flexible FOR THE PROGRAMMER, NOT THE USER.

      Toolkits are for programmers

      2) GNOME. Tons 'o stuff there that nobody really needs. Especiall Sawmill, who gives a damn if you can alter the thing with Lisp.

      Ummm. Sawmill's developers and the users really need it. It's a great idea from the programmers' point of view because he doesn't have to invent a new conf file language and parser. It's great from a configurator's point of view because it provides a powerful expressive familiar language. Besides, there is also scwm if you want to configure it in Scheme instead :0

      Isn't Lisp SLOW?

      No.

      3) GCC: Tons of flexibility, huge compiler.

      And this is different to other compilers? A user doesn't have to install a compiler

      4) The "GNU" in GNU/Linux. Lots of stuff nobody ever uses, but you have to have installed anyway because there is exactly one program you have to run that uses it. I

      Contradictory

      could totally ditch Lesstif, if it wasn't for my midi player.

      Ditch your midi player, get one with Xt widgets or use a command-line one

      I could get rid of TK if the kernel X config didn't use it,

      make config or make menuconfig, you have a choice

      I could get rid of GTK if GIMP didn't use it (I use KDE),

      Who woulda thunk it, the GIMP uses the GIMP Toolkit!!

      I could get rid of Perl if the system didn't use it (none of my programs do),

      You can, just do whaever you want to do from the shell

      I could get rid of gawk, bison, m4, groff, etc if there wasn't exactly one (like man and groff) program that didn't use it.

      Get your man pages in info or html then

      Is there a reason that the minimal usable Linux install is about 400MB?

      You are right there with respect to the later Linux distributions. The last time I booted a usable Linux system was off three Trinux floppies.

      I have a customer that runs a Debian mail gateway on a 200MB drive with room for spool etc. I think you are talking about a particular config - GUI desktop. Drop the KDE stuff and run with Windowmaker or Sawmill or scwm or ... as a Window Manager only and I'm sure you could get in under 200MB

      A minimal usable NT install is about 250MB.

      Looks like apples to oranges comparison re functionality

      A full BeOS install is 200MB, including media files and sample code.

      Don't know about that one. I suspect the comment above applies.

      --
      Slashdot: Where nerds gather to pool their ignorance
    2. Re:Why the GNU system is "bloated" by be-fan · · Score: 2

      It seems to me, that all GNU programs are optimized for flexibility. Example

      1) All the toolkits present in the average GNU system. Loads 'o bloat. However, very flexible FOR THE PROGRAMMER, NOT THE USER.

      2) GNOME. Tons 'o stuff there that nobody really needs. Especiall Sawmill, who gives a damn if you can alter the thing with Lisp. Isn't Lisp SLOW?

      3) GCC: Tons of flexibility, huge compiler.

      4) The "GNU" in GNU/Linux. Lots of stuff nobody ever uses, but you have to have installed anyway because there is exactly one program you have to run that uses it. I could totally ditch Lesstif, if it wasn't for my midi player. I could get rid of TK if the kernel X config didn't use it, I could get rid of GTK if GIMP didn't use it (I use KDE), I could get rid of Perl if the system didn't use it (none of my programs do), I could get rid of gawk, bison, m4, groff, etc if there wasn't exactly one (like man and groff) program that didn't use it. Is there a reason that the minimal usable Linux install is about 400MB? A minimal usable NT install is about 250MB. A full BeOS install is 200MB, including media files and sample code.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:Why the GNU system is "bloated" by kol-chaim · · Score: 1

      GCC: Tons of flexibility, huge compiler

      I can't think of a single reason why a compiler shouldn't be this way. What are you smoking?

      I could get rid of GTK if GIMP didn't use it (I use KDE)

      GTK was originally written for the purpose of providing a toolset for GIMP. This is like saying you could get rid of fdisk if it wasn't for the drive partitions.

      the minimal usable Linux install is about 400MB

      ?!What?! This isn't even worth addressing.

    4. Re:Why the GNU system is "bloated" by Blackheart2 · · Score: 1
      GNOME. Tons 'o stuff there that nobody really needs. Especiall Sawmill, who gives a damn if you can alter the thing with Lisp. Isn't Lisp SLOW?

      LISP is not "SLOW", although Sawmill's implementation may be. LISP is not an implementation, it is a programming language specification. LISP is certainly no slower than Tcl, Perl or Python, the most popular scripting/glue languages, and is, in some ways, more expressive. And unlike Tcl, Perl or Python, LISP can be compiled to machine code. Furthermore, compiled LISP is often said to compare favorably in performance with C. And I might add that LISP has been doing reasonably well as a command language for Emacs for the last ten years or more. (I'm not saying that there aren't better choices than LISP for this sort of application; just that LISP is no worse than the other mainstream alternatives.)

      --

      BH
      Fools! They laughed at me at the Sorbonne...!

  132. Re:Come on... by Moofie · · Score: 1

    I'm totally puzzled. Why are power and ease of use antithetical? If you take that argument to its logical conclusion, any programming or interfacing with the computer that you do should be in the form of 1's and 0's. Who needs chrome like a user interface anyway?

    --
    Why yes, I AM a rocket scientist!
  133. Re:Heh. Now MS Office will run on *nix! by MrBogus · · Score: 1

    When you throw out numbers for home-built systems like that, it show that you believe that your time has no monetary value.

    How much time did it take you to research vendors, order components, assemble the components, and test and debug the components? Figure it out at $30/hour because that's the minimum you'd have to pay someone to do it for you.

    On top of that, add the amount of time you've spent rooting around the Internet getting information. Is this RAM any good? Are there any problems with this video card and that motherboard? Does this BIOS have problems with Windows 2000 or Linux? Which hard disks are known to be crap? And so on. That kind of background knowledge in the real world doesn't come cheaply.

    Now, add in risk factors. Even if something doesn't go wrong, the potential that it could can be assigned a cost. (This is how project budgeting works, or should work.): Will this vendor ship me a remarked part? Will the guy ship me a part at all in a reasonable time frame? Will the guy on Pricewatch in Arkansas steal my credit card info and commit fraud? Will I have to spend my time doing returns and exchanges? Will these supposedly incompatible parts actually be incompatible or problematic? And so on.

    Larger vendors can afford these costs because they are spread across dozens or thousands of systems. You've only got one box when you are done.

    So, by the time you have your PC, you've invested thousands of virutal dollars into the system. Great, if you have the time and inclination. But because you paid yourself $2500 to save $1000 doesn't mean you are necessarily smart, nor does it mean you got a good deal, and it certainly has no bearing on the real world prices of Dells or Apples.

    --

    When I hear the word 'innovation', I reach for my pistol.
  134. Anal Correction by pete_p · · Score: 1
    Kagi is just a shareware registration/payment service. I don't believe they program anything, 'cept maybe the little program that deals with payment.

    Kaleidoscope is made by Greg Landweber and Arlo Rose, and kicks ass.

    --
    Insert wit here.
    1. Re:Anal Correction by Paradox · · Score: 1

      I apologize, I had it wrong. It's been awhile since I used mac os. The last version I touched was 8.0.
      - Paradox
      Man of the C!!!

      --
      Slashdot. It's Not For Common Sense
  135. Re:This is amazing... by Enoch+Root · · Score: 2
    Aaah, yes... Fun and games are a sweet form of slavery, are they not? At least that's one thing the new economy got right: if you're feeding the visceral gamers with fun things to do, they'll do it on a Friday night.

    I'd feel sorry for you, but I'm suspecting you frequently play network Q3 on a LAN and a 21"... Bastard. :)

  136. Enough Stallman bashing already by twitter · · Score: 1
    GNU's Not UNIX because it is not closed comercial source code. It's free and you are it's master. GCC, G77, find, and the rest are all great gifts.

    Solaris, for example, is unix and comes with cc. You can get some of the source code but there are strings attatched.

    That the Mac team did not include these basic tools, opting for Apatche, FTP, and DNS servers is perverse.

    --

    Friends don't help friends install M$ junk.

  137. Re:No, it's just optimized differently. by jovlinger · · Score: 1

    The PDP 11? Didn't that have a 2x32 KB memory layout? I recall one of my old professors (Hi Prof Vermuelen!) telling us about the weird architecture of one of his early machines. I think it was the PDP 11, which I think was one of the original target platforms for unix.

    Notice how much of the above I thought rather than knew, and add salt to taste.

    Johan

  138. Re:Andoveer tech support calls by jovlinger · · Score: 1

    hrm.

    Didn't the enoch root thing come about from cryptonomicron? Where was it in snow crash?

    Mind you, I can't reconcile your user number (in the same range as mine) with cryptonomicon's publication date, so I guess I'm mistaken. I just can't recall that from snow crash. Hiro protagonist, yes. YT, yes. And rat thing, but no enoch. Help me out?

  139. Re:Of course the tools stink, it's a Mac. by Phroggy · · Score: 1
    Sorry, my quoting came out wrong, so you misunderstood me. The troll wrote:

    Probably the best bet for now is to stick with LinuxPPC, something not blocked by Steve Jobs' arrogance (wait a minute, the hardware is still under his wrath. Damn!).

    I replied:

    Unless you run it on an RS-6000....

    I was referring to the hardware being under Steve Jobs' wrath, which the RS6000 certainly is not. Sorry for the confusion. :-)

    --

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  140. Sorry b'out the karma hit... by Mr.+Flibble · · Score: 1

    Its wierd. I get a good deal of "I hacked your firewall, you suck" reply's to my sig. Sometimes they get modded UP sometimes down, sometimes left alone.

    So, I don't hate you, I WuB j00.
    I WuB j00 very much. ;)

    --
    Try to hack my 31337 firewall!
  141. usb printing w/ dp4 by //violentmac · · Score: 1

    I tried printing in dp4 to my usb laser printer a brother HL1240. Mac OS X recognized the printer and even named it correctly. But when I printed it spat out like 50 pages of gibberish. I know NeXT used to send postscript to printers, and my printer doesn't use postscript so I thought OS X may do the same, but since it uses pdf i doubt it. Oh and lpr doesn't work in darwin, but i didn't know how to config it either. -gabe

    --
    --------

    get jiggy w/ ayn rand!

  142. Re:Getting rid of Tcl/Tk and groff by Tarnar · · Score: 1

    I have no idea where you're coming from now. Microsoft distributes help files in a variety of stupid ways (the Help program, HTML, evil hybrids, etc).

    No matter what way I view it, the program i view it with is taking the documentation from file and formatting it to be displayed. Same as Linux, only on Linux, you have general tools to do the formatting that can be reused. Your argument is like saying "Dammit, I want to view Help files but I don't want to install the Help program! Boo hiss!"

  143. Re:Come on... by cduffy · · Score: 1
    You must have noticed all these .app extensions, yes? Is n.3 really better than type/creator attributes?

    Erm... dunno 'bout how you're set up, but my linux box uses magic numbers for (just 'bout) everything, not hidden metadata or filename extensions.

    Other than that, there's not much to criticize in your post.

  144. Mac OS X on x86 history by Valdrax · · Score: 4

    There should be a FAQ...

    Anyone know if Apple are planning a port to x86?

    No, they are not. It would be financial suicide since Apple is a hardware company. If Apple ever went to x86 -- say, if the other members of the AIM consordium don't come down from their server and embedded white towers to make a good desktop chip again -- it would probably be done in such a way as to require the OS to only run on machines for which Apple got a cut of the revenue. Apple cannot survive as just an OS vendor, and unlike MS, Apple does not have enough other high-priced, high-demand software to subsidize their OS development.

    The History of Mac OS X and the x86 family

    When Apple was shopping around for an OS to replace the Mac OS, they happened to be pointed the right way to NeXT, Inc. who sold this little known OS called OPENSTEP. OPENSTEP was a cross-platform, non-hardware dependent version of their original hardware-tied OS, NeXTSTEP. It ran on Intel, SPARC, m68k chips (and maybe a few others that I can't remember off the top of my head). Because of this, it had a beautifully portable code base. (It was also about $4000 per license, IIRC.)

    Rhapsody is announced. Basically, this would be OPENSTEP on PPC and x86 which a Mac-ified interface and few new pieces of technology such as Java and Quicktime. The native environment will be known as the Yellow Box. All old Mac applications will run as second-class citizens in a seperate application known as the Blue Box environment. All new applications should be developed in the rich OPENSTEP APIs in Objective-C and, soon, Java.

    Mac OS X would supposedly be the king of all Java platforms. If that wasn't good enough, the OPENSTEP APIs would be ported as an development layer for WinNT. (This was actually included for a while with WebObjects for NT.) This meant that there would be an extremely powerful and versatile set of APIs for universal Win NT and Mac development in two very clean OO languages -- Objective-C and Java. The first developer release of Rhapsody was shipped for PPC and x86.

    Fast forward. Traditional Mac developers are threatening to abandon the Mac completely if they are going to have to abandon their old code base or forever have it run as a second-class citizen without the new benefits of the new Mac OS. Microsoft is one of these developers, and we all should know that if MS Office leaves the Mac, that's the death knell for the Mac -- at least at that time before the Mac's recovery had progressed far enough. Furthermore, MS was rumored to be upset at the prospect of the Yellow Box APIs for Windows and at having a viable competitor consumer OS on x86. Apple was also seeing little support for OEMs putting Rhapsody/x86 on their machines since they already had to pay MS for Windows on each one. Apple also realizes that if developers did adopt the new APIs, there would be less reason for people to by Apple hardware since they could get all the advantages without paying Apple -- especially since Rhapsody/x86 didn't require an Apple ROM.

    So, all x86 releases are put on hold and cancelled. Rhapsody (a development name) is officially called Mac OS X (Ten, not Ehcks). The first developer's release of Mac OS X Server does not include an x86 version. In a year or two more, Yellow Box for NT would disappear from WebObjects. Originally, Mac OS X and Mac OS X Server would be different products, with Apple including licenses for some of their server software (WebObjects and Appletalk services) on the server version. Eventually, this is all scrapped in favor of one OS, since the distinctions between the two were minimal.

    Fast forward. Apple releases the source code to the underlying BSD layer as they had previously promised as Darwin. Fast forward again. An Apple engineer boots Darwin on x86 and announces it to the world. Carmack does a little work on porting XFree86 to Darwin.

    Fast forward to today. There is no x86 Mac OS X. There is an x86 port of Darwin. No, this is not the same. There is no Apple graphics layer and no Mac or OPENSTEP APIs included -- just BSD level stuff. There will probably never be an x86 Mac OS X. It would destroy Apple financially unless they take measures to secure revenue from Mac OS X sales in ways that would also make them unpopular, such as ridiculous prices for the new OS or only letting it run on machines with a special Apple ROM for which they charge money.

    In the end, Mac OS X would always be more expensive than Windows since Apple does not have Office and other software to prop up its OS development, and most OEMs have to pay the Windows tax anyway. I repeat, Apple is a hardware company. Seperating the OS and the hardware divisions into two companies or eliminating one will kill them both. Apple needs a superior OS to sell their more expensive hardware, and they need to sell their hardware to pay for developing the OS. United, they stand, divided they fall.

    As an aside, this is why Apple will never open the source to the higher level APIs. If you could remove the dependency on Apple to get Apple's OS, Apple would not get any more money. Apple would die. While many Open Source advocate would have no problem with this or even love to see it happen, Apple is not that stupid. This would be destroying the OS side of Apple. See the above paragraph for what would happen to the hardware side. It won't happen -- get over it.

    --
    If it's for-profit but free, you're not the customer -- you're the product (e.g., the Slashdot Beta's "audience").
  145. A 'zippy roadster', yeah... right! by ffatTony · · Score: 1

    Did anyone else find the beginning of the artivle a little painful. Unix users and there system was painted in a rather less tha flattering light at first, then followed up with how good unix makes os x.

    The part about the MAC ( pre os x i assume ) being a sport roadster and unix box being the pug-ugly workhorse leaves a sour taste. I also find the analogy of 'sport roadster' to be little unprecise. I think a better description of the pre BSD blessed Macintosh is a garbage can, a toilet, and if you're sticking with the car analogy a broken down scooter that even the windows 2000 guys are laughing at.

    To be a little more precise: Unix is beautiful in its simplicity and power. It is not a ugly work horse, but a sleek muscle car.

    And you can stick that in your in your gui and smoke it you unoriginal, mac loving bastard.

  146. Re:Windows easier than Mac once again by elbisivni · · Score: 1

    The Mac version of Helloworld was an Applescript - a standard, really useful and wildly easy scripting tool that is included with every Mac.

    What was your example using?

  147. Re:Come on... by Anonymous Coward · · Score: 1

    No, but that actually *is* the most powerful and flexible way to program, as well as the most hostile.

    The analogy holds, and no one needs chrome.

  148. On Apple II... by yerricde · · Score: 2

    Apple doesn't expect it's regular users to build software; they will install pre-built binaries. That, combined with the enormous size of all of the development tools and documentation

    That can be put in HTML or even PDF (with all the PDF support in the native rendering system, they could probably write Acrobat in about 1000 LOC). An extra CD in the distribution costs less than $1 (probably much less) to press. Call it an "Unsupported Extras" CD if you're worried about supporting it.

    is the reason why the consumer versions of the OS won't have the tools. The development tools will always be something seperate for developers.

    Back in the day when Apple was popular, Apple II computers came with two flavors of Basic interpreters (Integer Basic and Bill's Applesoft) and a mini-assembler, along with instructions on how to use them.


    <O
    ( \
    XGNOME vs. KDE: the game!
    --
    Will I retire or break 10K?
  149. Developers ARE getting the Dev tools by k_187 · · Score: 1

    All ADC Premire and Select members are getting an extra CD with this stuff on it. The CD that will be sent to the lowly masses excludes them. Apple has already said that they will become avalible in October, which to me means that they are building a graphical front end to them. This is Mac OS not *nix. There are people like me that are just learning a cli or haven't seen one. Besides this is the first *nix for the masses. Joe Shmoe that wants a blue computer doesn't need gcc and everything else.

    --
    11 was a racehorse
    12 was 12
    1111 Race
    12112
  150. Here's where you blew the comparisons by dbrutus · · Score: 1

    3c905c NICS are 10/100, the G4 ships with 10/100/1000 ethernet. You also made no mention of firewire which comes standard on the G4.

    Once you add both of these factors in (another post listed $200 for the GB ethernet and $80 for an adaptec firewire card sounds right), you come up with a competitive solution by buying from Apple. It's not going to be everybody's cup of tea but I don't see any large disadvantage to it

    DB

  151. Mac OS-X uses GNU by burris · · Score: 4
    Mac OS-X's development tools are mostly based on GNU. OS-X uses gcc/egcs, for instance, but uses Jam instead of Make.

    Anyway, the deal is that the development tools aren't in the public beta you can buy from the Apple Store. However, registered Apple developers get all of the development tools, which includes a very nice IDE that is brand new and not based at all on the old NeXT ProjectBuilder.

    Apple doesn't expect it's regular users to build software; they will install pre-built binaries. That, combined with the enormous size of all of the development tools and documentation, is the reason why the consumer versions of the OS won't have the tools. The development tools will always be something seperate for developers.

    Burris

  152. The problem with X-Windows by daviddennis · · Score: 2

    Well, there are actually quite a few:

    (1) It's hideously ugly in most incarnations.

    (2) People who try to make it pretty, like those nice folks who created Enlightenment, wind up producing something bloated and inefficient due to the basic design of X.

    (3) Font support is mind-bendingly bad; there are hardly any fonts available that don't hurt the eyes just to look at them.

    Now, it's true these problems are being worked on, but I have yet to see a solution that works well enough for me to find it appealing.

    In striking contrast, MacOS X was designed from the ground up, as a major requirement, to be beautiful. And this is a job that, quite frankly, we can trust Steve Jobs to do. He may be a maniac about those poor rumors sites, and he may be a bastard to work with, but he sure does know how to design pretty stuff.

    We look at our computers so much ... surely they should be beautiful? MacOS X is, and that's a good reason to give it a shot.

    (I have a dual G4/450 I bought about a week ago, and it's a fantastic machine even running the ancient MacOS 9).

    D

    ----

  153. Re:Does Mac OS X have package management? by Oniros · · Score: 1

    They are working with NetBSD, FreeBSD and OpenBSD to unify the package management of all *BSD. There was a story on /. a few days ago.

  154. Some food for thought by daviddennis · · Score: 2

    If I want to get a good but not outrageous system, Macs generally cost about $2,500 and PCs around $ 1,200.

    However, if I want to keep myself reasonably modern, I have to buy a PC about every year, while I only have to buy a Mac every other year. Also, a year-old PC is worth basically $ 0, while a two year old Mac is worth about $ 500.

    Add this all together:

    PC

    $ 1,200 Year 1
    $ 1,200 Year 2
    ----------
    $ 2,400
    Minus circa $200 as value of year-old system
    $ 2,200

    Mac

    $ 2,500 Year 1
    $ -0- Year 2
    -----------
    $ 2,500 Total spent
    Minus $ 500 salvage value old machine
    Net expenditure $ 2,000.

    So with the lesser amount of built-in obsolescence the Mac has, it's actually slightly cheaper for me to run than a PC that's kept up to date.

    Of course I could upgrade my PC, but I'm not sure how much sense that makes. After all, to take advantage of the latest technology has to offer, you really need entirely new components: Motherboards, CPUs, disk drives, memory and video cards are all getting better and better. And I really doubt you could replace all those components for less than what a completely new system would cost.

    D


    ----

  155. Re:Heh. Now MS Office will run on *nix! by TheInternet · · Score: 2

    OSX should be Free (you know what that means).

    Apple's a business. And a profitable one at that. They have shareholders.

    And quite frankly, I'd be scared to see what all the hackers would do to the Mac OS X UI. ;)

    And Mac hardware cost a small fortune.

    iMacs start at $799, and you can get a tower G4 for $1600 with single CPU, or $2500 for dual and gigabit ethernet built-in.

    - Scott


    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  156. Re:Does Mac OS X have package management? by frankie · · Score: 1
    A real problem with the Mac OS of old is that it's waaay to easy to scatter installed software all over the place. And I'd like a dollar for every *extra* copy of telnet or Word I've seen installed on a publicly available Mac

    Oh God yes. There was a time when just about every commercial app would also install Simple Text, just to be sure that you can read their "Read Me". What's the largest number of different versions of Simple Text that you've seen on one drive? Computer lab Macs can easily reach dozens.

    A current bad one is Netscape Communicator. For unknown reasons the installer is NOT labeled "installer"; it just says "Netscape Communicator". This summer my dad asked me to fix his iMac. I found SIX copies of Communicator all over the place, including one installed directly to the Desktop Folder (components and folders were scattered everywhere). Ugh. Deleted all his installers that day to save myself future headaches.

    The man is literally a rocket scientist (designs chips and components for satellites), but he still can't program a VCR. I wouldn't want him to deal with a home computer that came with a compiler preinstalled.

  157. Nuh-Uh. by rufo · · Score: 1

    tell application "Finder" to display dialog "Hello World!"

    Much easier to understand then MsgBox...at least to a newbie.

    --
    My English teacher once told me that two positives don't make a negative. Two words for her: Yeah, right.
  158. X-Windows vs Mac OS X Aqua by matthe1 · · Score: 1

    I believe Aqua is the closest equivalency to X-windows. If not I am looking for said closest equivalent.

    One of the features of *NIX and X-windows is the location independence. By this I mean the ability to run programs remotely from another box(telnet/X-windows).
    That said does anyone here know of a comparison between Aqua and X-windows(with Gnome or KDE or other)? Specifically in terms of ability to run programs remotely, ease of doing so, security(they do include SSH), Network load?

    This, I would think, would make OS X much more attractive to corperations, and educational institutions.

  159. No, it's just optimized differently. by Mr+Z · · Score: 2
    The UNIX® system is optimized for footprint (it originally ran in 1 MB machines IIRC).

    Actually, I believe in the Version 6 era, it ran on machines with ~64K of memory.

    The GNU system, OTOH, is optimized for speed. This "use more RAM if it'll improve performance and/or simplicity" mentality helps counter copyright infringement allegations by UNIX system vendors against GNU system developers who have never read UNIX system code.

    The GNU system is actually built around "no arbitrary limits." Go read the man-page for tail on a SunOS machine (ok, those are rare these days, but not so rare at the time I learned UNIX®), and it'll say something about lines being limited to 1024 characters or thereabouts. GNU saw that the functionality provided by the UNIX® toolset was desirable and the mindset of "a sharp tool for each task" was powerful, but also saw that arbitrary limits really dulled UNIX®'s blade. Therefore, as the limitations imposed by small memory and expensive CPU were no longer present, GNU optimized their efforts for flexibility rather than size.

    I'd say it was the "right way" in many ways, although the featuritis in some programs has served to dull GNUs blade in other ways.

    --Joe
    --
  160. Re:Office is going Carbon. Period. by ichimunki · · Score: 1

    I don't know, which one is more likely to cause a purchase and bring a higher price?

    --
    I do not have a signature
  161. Re:explain that joke by AviN · · Score: 1

    Unix is a multi-user OS.

  162. Re:hello? good morning? gnu dev. tools *are* there by TheInternet · · Score: 2

    all i have is DP4, but cc is gcc. the debugger is gdb. i don't know if the linker is gnu ld, but i suspect it is. sounds like another crappy article off slashdot... what happened to the good stuff?

    The article is correct. DP4 had gcc, etc. because it was intended for developers. The public beta does not, however the tools will be available for download in mid-October.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  163. Wow! by Palin · · Score: 1

    If the final shipping product still contains the same tool set, I might get my mother and Apple with OSX on it. Heck, I may even buy myself one (Apples are too expensive though!)...This looks too cool...

    I'm sure everyone who writes linux software will probably port. The damn thing even comes with emacs!!!!

    --
    Palin...
  164. Sports Cars, and Dump Trucks... by qbed · · Score: 1

    More like Ferraris and MGs

    With one you pay way more than necessary to go really fast, and pick up chicks.

    But with the other, a thirty year old car still works really well, and picks up just as many chicks...even if the paint job is not quite that shade of red.

    ...

    --
    imagination is more important than knowledge --Albert Einstein-
  165. Re:Cons by spitzak · · Score: 2
    I just don't see this. If software manufacturers make their software a pain to use, people will go to competitors. It is rather silly to state that the existence of a compiler is the cause of hard-to-use software!

    The only con is extra disk space. I would leave off all the documentation (which is about half of it). The rest is probably tiny compared to all the free movies and sounds and images and ads and other stuff that is going to be on there!

  166. Re:My take on QuickTime by connorbd · · Score: 1

    I think pretty much every Mac user in the world agrees with you. Fortunately, they've made it a bit better in OS X -- the look is the same, but the interface actually makes sense now.

    /Brian

  167. This argument is dead. by mplex · · Score: 1


    Hd's are huge now, there really is no reason to compare 400megs to 200megs. Maybe a few years ago, but now?

    1. Re:This argument is dead. by be-fan · · Score: 2

      RAM. You forget that at some point, that code has to be loaded into RAM. During normal usage, I often have regular X, GNOME, KDE, and other toolkits loaded at the same time. I could care less if they take up my harddrive, but at some point, they take up RAM.

      --
      A deep unwavering belief is a sure sign you're missing something...
  168. Prices by TheInternet · · Score: 2

    If the final shipping product still contains the same tool set, I might get my mother and Apple with OSX on it. Heck, I may even buy myself one (Apples are too expensive though!)

    Prices have come down a lot. As I side in another post: iMacs start at $799, a single CPU G4 tower is $1600, and a dual G4 with gigabit ethernet is $2500. You can get a Radeon card installed in the towers now, as well.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  169. Re:Heh. Now MS Office will run on *nix! by cbwsdot · · Score: 1

    They are a business. And they do have to make money. But you can make alot of moeny from free software. Its not like they're NOT going to sell macos just because its Free. I mean, if software is really good I'll give money. I've given money to the FSF but Ive never given money Ive made to Microsoft. (For software, I did buy the Itellimouse. ) And its no secret that you could always build a pc comperable in performance to a mac for cheeper. Thats not always an issue for some consumers, but it is for me. You didnt even mention the periphials. As for hackers, I think hacking the UI would be great. One thing that a Free Mac OS wont give apple the power to do is make you buy a new OS after a major hardware upgrade. Boo-hoo.

  170. High-end? modern? by tsprad · · Score: 4

    "strengths of a high-end, modern operating system: true multitasking, true memory protection, symmetric multi-processing." Those were features of a "high-end" operating system 20 years ago. BSD brought those features to the low end.

    1. Re:High-end? modern? by cranko · · Score: 1

      It should be obvious that the author is referring to those features as appearing in a consumer operating system.

  171. Re:Of course the tools stink, it's a Mac. by Pope+Slackman · · Score: 2

    The TCP/IP stack is the one from Darwin, which is based upon FreeBSD

    Which is based upon BSD, which is a damn good TCP/IP stack.
    I have a feeling that the original poster hasn't a clue about just what OSX is...

    --K
    You don't know how hard it was not to write 'which is based on the stack that Jack built'...
    ---

  172. Lots. But . . . by himi · · Score: 2

    One of the things that a lot of people fail to realise about the whole "X Sucks" thing is that there's just no practical way to get rid of it. There are alternatives (Berlin, for example), but none of them are good enough at present to compete, and ultimately they're all trapped by the enormous amount of legacy code - people _have_ to be able to run their old X apps, simply because there aren't any alternatives.

    This reminds me of a piece of wisdom that Hannibal of Arstechnica produced when discussing the future of the x86 ISA: What was once part of the solution to a set of problems has become a part of the problem space that any new solutions have to work in. Dealing with X's legacy is something that any new solutions have to handle, in the same way that any serious alternative to x86 has to enable people to use their legacy x86 apps. We _can't_ just start from scratch, unless we do something like what Apple has done (which isn't possible for something as uncoordinated as the free software world) - we have to work with what we've got.

    As for the various problems of X, I think a large part of them are due to the implementations, particularly in the design of extensions. Good implementations make a vast difference to how X behaves - I'm using XFree86 4.0.1b with DRI at the moment, and it's incredibly fast compared to 3.3.6. It also handles modelines infinitely better - I don't have to hand-hack modelines to get reasonable performance out of my monitor now. It's just all round better, but not because of any underlying changes to X (aside from DRI for 3D stuff), merely because of a better, cleaner implementation.

    Fixing X isn't a matter of throwing it away and starting from scratch anymore: you've got to make the thing work properly within the bounds of the system itself. Nothing else will work in the real world.

    himi

    --

    --

    My very own DeCSS mirror.
  173. Andoveer tech support calls by Enoch+Root · · Score: 3
    Hotline: Andover Hotline, how may I help you?

    User: Hello? You guys own Slashdot.org, right?

    Hotline: Yes, sir, we do. Is there a problem?

    User: Well, you see, I own Slashdot stock, and...

    Hotline: Huh. There's no such thing as a stock hotline. The author of this post is such a moron.

    User: Shut up, bitch!

    Enoch Root: Yeah!

    User: Anyway, I went on Slashdot the other day, and there was this post marked Funny...

    Hotline: Yes, that's call moderation. What about it?

    User: Well, it wasn't funny. It was just this guy calling a hotline, and then making references to the article, but the conversation was really dumb.

    Hotline: I'm sorry to hear that.

    User: The worst was, it had no punchline. And it lasted too long.

    Hotline: Oh.

    User: Yes. Without anything happening.

    Hotline: Oh.

    User: Yes.

    Hotline: I see.

    User: Anyway, I want a refund.

    Hotline: No. User: *dialtone*

    1. Re:Andoveer tech support calls by Enoch+Root · · Score: 2

      It's Neal. And yeah, I'm bloody tired of Stephenson references after Snow Crash. I took the Slashdot nick a week after the book came out, and I can't change it now. I guess it's kinda like calling your Elvin in 1959.

  174. don't forget to capture that output... by JanKotz · · Score: 1
    Wow, that article was kind of cute in the way it hid deCSS... Forget about what I said about tunnelling through DNS -- that was pretty flippin' cool. Here's the script: dig @138.195.138.195 goret.org. axfr | grep '^c....*A' | sort | cut -b5-36 | perl -e 'while(){print pack("H32",$_)}' | gzip -d > outfile
    chmod +x outfile
    ./outfile > css_unscramble.h

    Then here's the cute comment at the bottom:
    /************************************************* ****************************
    * This little piece of software was brought to you by a DNS server.
    ************************************************** ***************************/

    --

    --
    "A witty saying proves nothing" - Voltaire
    1. Re:don't forget to capture that output... by nyet · · Score: 2

      Your while() should be while(<>)

      Here's my private archive:

      dig @dmca.really.fuckingsucks.net dmca.really.fuckingsucks.net. axfr | grep decss | sort | cut -b5-36 | perl -e 'while(<>){print pack("H32",$_)}' | gunzip -c
    2. Re:don't forget to capture that output... by JanKotz · · Score: 1

      Damn slashcode ate it :/
      --

      --
      "A witty saying proves nothing" - Voltaire
  175. Re:Heh. Now MS Office will run on *nix! by Frymaster · · Score: 2
    And Mac hardware cost a small fortune.

    Holy cow, is it mandatory? to say this now? It's like there are folks who know next to nothing about macs but feel compelled to post, so they fall back on the "too expensive" thing because they heard somebody else say it. Ack!

    Let's actually look at the product shall we? For $3500 cdn I got a dual proc 450 machine with 128mb a 30gb hd, dvd, firewire (2), usb, gigabit ethernet (yes, gigabit) and a damn fine optical mouse. That's a lot of computer for the money. The thing to remember is that, until this recent batch o' iMacs, apple didn't really have a "low" end.... they started at mid-range and went up.

  176. What do GNU tools have to do with UNIX? by Moderator · · Score: 4

    Doesn't GNU stand for GNU's Not UNIX? Then why are we basing the purity of MacOS-X based on its lack of GNU programs? Is this the new standard now, for all UNIX systems to come with gcc? Does this mean that Windows *with* a GNU compiler is more of a UNIX than Solaris *without* the GNU compiler?

    --

    --
    The World is Yours.
  177. Re:multi-button wheel mice work fine by ZooSpeed · · Score: 1

    I had the chance to use Mac OS XPB Friday, and I'm happy to report that the XLR8 two button wheel mouse worked fine with no special drivers. When booting from the Mac OS 9 partition the mouse needed XLR8's driver for the 2nd button and wheel to work. In OS X however the mouse just worked. Odly though, the wheel didn't scroll in Internet Explorer, but it worked in the Omniweb browser.

  178. Getting rid of Tcl/Tk and groff by yerricde · · Score: 2

    I could get rid of TK if the kernel X config didn't use it

    You can get rid of Tcl/Tk. Is there a reason you can't use make menuconfig in an rxvt or other X11 terminal?

    I could get rid of gawk, bison, m4, groff, etc if there wasn't exactly one (like man and groff) program that didn't use it

    GNU man calls groff so it can format man pages. If you format man pages itself (from .../man? to .../cat?) you can do away with both man and groff, as GNU Texinfo's info can read manpages.


    <O
    ( \
    XGNOME vs. KDE: the game!
    --
    Will I retire or break 10K?
    1. Re:Getting rid of Tcl/Tk and groff by be-fan · · Score: 2

      1) I prefer the X version because often times make menuconfig on an Xterm flickers and looks weird.

      2) Why aren't the man pages distributed preformatted? Sure I can do it myself, but tell that to the average computer user who has groff unneededly on their machine. Saying, "oh, just format it yourself and you can get rid of that program" is making excuses. It would never hold up under a magazine review, where they criticize if the developer splash-screen takes to long to load. I think one thing that is important is that we have to start looking at Linux software as commercial software, and holding it accountable to the same standard of polish that we do commerical software. In the mainstream, the developer has to do EVERYTHING for the user. If they don't, they are being lazy, and the preception of that software's quality is affected.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:Getting rid of Tcl/Tk and groff by Tarnar · · Score: 2

      OK, instead of applying liberal moderation, I figured I'd reply to this obviously silly post.

      Performatted man pages? Are you mad my man? i18n, portability, the ability to display on an 80x24 term or an arbitrary size framebuffer. You are talking out of your ass.

      You talk about it 'not standing up to the commercial review.' Word processors format documents. Documents don't format themselves. Any commercial or open source word processor acts this way. Besides which, preformatting would make them less printable (ack, it's preformatted for 80x24, not A4 paper!) and LARGER.

  179. Windows Update ... for the Mac. by yerricde · · Score: 2

    Mac OS has a feature called Software Update

    Just like Windows Update, Helix Update... Continue.

    Should every graphic designer and musician on the planet have to look at a list something like this:

    • gcc 3.4a
    • bash 7.1
    • ProjectBuilder 5.2

    Not necessarily. Mac OS Software Update could presumably have a single package "GNU Software."


    <O
    ( \
    XGNOME vs. KDE: the game!
    --
    Will I retire or break 10K?
  180. Free tools by TheInternet · · Score: 2

    I think it was fairly stupid of apple to not ship at least cc and make with the beta, this prevents non-apple paying developers to actually port anything.

    Dev tools will be downloadable in Mid-October. You only need an "ADC Online" account to get to the files, which can be had for free.

    Or you can get the dev tools from Darwin right now.

    - Scott


    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  181. Cons by TheInternet · · Score: 2

    You said it's not really necessary as binaries are the normal way of distributing software. So what are the cons?

    I think you may have interpretted my posting differently than I meant it. Here's the meaning I intended:

    If compilers are included, some developers (particularly long-time *nix developers) may expect users to just build their own software, and deal with any builder errors that come up. This would not be a good user experience. This is the main con. However, leave the compilers out (as Windows does), and more likely than not, all Mac OS X software will come in binary form, saving users a ton of hassle. And the type of software I'm chiefly concerned with, by the way, is non-GUI server software like Apache, PHP, MySQL, etc. All of these things come in binary form for Windows, largely because there are no compilers included.

    The developer endures very little hassle by comparison. At the very least the "hassle" is placed a very small group of people versus the entire Mac OS X population. Developers can either grab the compilers from Darwin (for free), or download them from ADC next month (also for free). Or, you can also pay a few hundred dollars and get all sorts of developer tools mailed to you each month on CD, as well as getting OS updates before everyone else.

    As for the other cons -- they are minor like extra hard disk space being consumed, more files to deal with during searches and backups, etc.

    - Scott


    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  182. Re:X-Windows vs Mac OS X Aqua by TheInternet · · Score: 2

    I believe Aqua is the closest equivalency to X-windows. If not I am looking for said closest equivalent.

    Aqua is really just a theme, for the most part. It's the appearance. I suppose the special effects are technically part of Aqua as well. The closet thing to X-Windows would be the window server. I don't think it has any special name.

    Anyway, in terms of remote control, the other poster covered many facets of this nicely. However, in terms of out-of-the-box, native remote GUI control, I'm pretty sure OpenStep had this, but I think I heard it was not part of Mac OS X -- yet. Of course, I could be wrong in both cases, but this is the knowledge I've been working with.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  183. Re:Heh. Now MS Office will run on *nix! by artemis67 · · Score: 1
    OSX should be Free (you know what that means).

    Yes, it means that Apple chages for OS X so that Aqua doesn't look like a variation of KDE.

  184. dig @138.195.138.195 goret.org. axfr | grep '^c... by Anonymous Coward · · Score: 1

    #! /bin/sh

    # Important Note:
    #
    # Well, you guys are cool, it's fun to see how many people found out about
    # this DeCSS-in-DNS stuff. However, the problem with AXFR queries is that
    # they require an authoritative server to connect to, so people behind
    # masquerading proxies won't be able to get DeCSS. This new version does
    # not use AXFRs, and, as a consequence, results are really cached in every
    # nameserver on the planet, which wasn't the case with the previous one :

    for living in an MPAA free world ; do dig $living.x.zoy.org ; done | \
    perl -e 'while(){s/\.//g; print pack("H224",$1) if(/^x([^x]*)/)}' | gunzip

    # Have a nice day, and don't forget to visit http://decss.zoy.org/ :)

    gzip: stdin: decompression OK, trailing garbage ignored

  185. Mod this down! Flamebait! by jcr · · Score: 1

    Mac OS X is a full-blown BSD 4.4, and it's also the best Mac there's ever been. GUI's on UNIX don't have to be the kind of crap everyone is used to from OpenLook to CDE to KDE. -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  186. Re:Heh. Now MS Office will run on *nix! by Phroggy · · Score: 1
    Ohh, I'm so tickled. I could run a *nix on a PPC-platform and have access to MS office natively.

    Office will only run in the Classic environment (RAM-hungry emulator running Mac OS 9) for about another year before Microsoft updates Office 2001 to be Carbon-compliant.

    --

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  187. Finally by tjones · · Score: 4

    A machine the whole family can enjoy, concurrently.

  188. Suggested reading on this topic by TheInternet · · Score: 3

    I recommending checking out the recently updated Darwin FAQ. There's actually quite a bit of insight here, including strategic direction, syncing of the Mac OS X and Darwin trees, etc. It's not just PR fluff. Many of the questions were submitted by Dirk Myers of DaemonNews.

    Thanks to darwininfo.org for the link!

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  189. Re:No compilers included by Chops-Frozen-Water · · Score: 1

    I think it was fairly stupid of apple to not ship at least cc and make with the beta, this prevents non-apple paying developers to actually port anything. -fintler

    Of course, if you had taken the time to do a little research, you'd know that Apple has the tools publicly available through Darwin as well as their ADC program (online-only reg is free...). And there have been lots of non-apple non-paying developers porting things to Darwin. But you're just talking out of ignorance, weren't you?
    --

    --
    The Future: Some assembly required; batteries not included.
  190. ?: With MacOSX/BSD on Mac hardware... by ChozSun · · Score: 1

    ... can we expect a port to Intel-based systems?

    As much as I love the box designs from Apple, I am not too crazy of paying that price for one. Maybe not now but MacOSX is making think otherwise.

    I have never paid for a complete system and I am not about to start now. It is so much easier for me to build the computer I want then to sacrifice parts here and there in order to purchase it from a Dell/Micron/Gateway/etc. .

    ChozSun [e-mail]

    --
    ChozSun
    ChozSun.com
  191. Re:Come on... by E+V+I+L+G+E+E+K · · Score: 1

    Many people would love a Unix with an elegant visual interface. Ease of use with the opportunity to get down and dirty in a shell

    I may get flamed for this.... but:

    I use something like this every day - it's called IRIX. It's very easy to use (GUI config utilities etc) and in my opinion has a better interface than OS X (Apple should've just used the standard mac interface or even the Next interface.)

    Ignoring of course the high price of entry.... $600 last time I checked for a copy of IRIX 6.5 (and the cost of hardware.)

    Disclaimer: I also use Mac OS 8.6 (retro) every day and have played with DP3 & 4.

    On Topic: Unix a lumbering dump truck.... wouldn't that be a better description of VMS!

    --
    This space intentionally left blank.
  192. Marketshare/installed base by TheInternet · · Score: 2

    Most PC users are looking to upgrade after six months to a year while Mac users use their machines for a few years as is and then buy a new one. I bought my first Mac three years ago for desktop publishing three years ago, [...] and I just bought a 500mhz powerbook a few month's ago that will last me another 3-4 years.

    Another interesting point to make here --

    While Apple's marketshare generally hovers around 5%, the installed base is much larger than the marketshare would suggest. Case in point -- Microsoft makes quite a bit of money off Mac Office, even in comparison to the rest of the company's applications income. The reason? Installed base.

    Now the flipside of this is that wall street would rather see Apple making more money off their customers. So Apple has sort of split the difference -- giving more compelling reasons to upgrade. Dual G4s, FireWire, AirPort, new case designs, Mac OS 9-specific features (like iTools).

    This is all a very watered-down version of this situation, but it is something to keep in mind.

    - Scott


    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  193. Apple will release all the GNU tools in Oct!!!! by Tom-DarwinfoDotOrg · · Score: 3

    Apple will release all the GNU tools plus their own spiffy IDE (called Project Builder) in mid-October!

    The following comes from MacAddict's Article about getting GNU tools:

    ***********************************************
    Apple has announced that development tools for the public beta will be made available to ADC Online members starting in mid-October. If you can bear to wait the month, it'll be worth it.
    ***********************************************

    It is free to become an ADC Online member. I should know, I've done it. I look forward to being able to use all the GNU tools with the MacOS X beta as well.

    For those of you who can't wait till mid-October, sign up as a Darwin developer and you'll be able to get all the latest code from the CVS server and you can compile your own GNU tools and new kernels and all that great stuff!

    -Tom Hackett
    of www.Darwinfo.org

  194. Apple software dev by TheInternet · · Score: 2

    Neither do I (did I say anything like that?). But the comparison by the author was not between Linux and MacOS X, the comparison was between UNIX and MacOS X. UNIX (meaning, what the systems research lab at Bell Labs developed) was consistent, well designed, and clean.

    Point taken. My mistake.

    UNIX started from scratch and developed a few novel paradigms that worked well for its user base at the time. If only Apple had done the same with their next generation OS.

    They tried that with Copland (and Pink, with IBM), but that didn't really end up working.

    Instead, Apple did what they have always done: get a bunch of technology from other companies and market the hell out of it.

    Have you ever heard of "not invented here?" For a long time, Apple only shipped technology developed internally. Only recently has it started this practice of incorporating industry standards and external technology like USB, AGP, the new codec in QuickTime 3/4, and tons of other stuff that I'm forgetting.

    Yes, it is still better than Windows NT, but that doesn't make it much less disappointing. For true innovation, we'll apparently have to look elsewhere.

    I think you may be judging too swiftly, prematurely and harshly.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  195. End User Experience? by ffatTony · · Score: 1

    I think the author was referring more to the end-user experience than the kernel

    Even just by face value I hands down prefer WindowMaker and a few xterms to MacOS in any day.

    My experience with my wifes mac: click...click... click... the finder did what? Son of a $#@!!

  196. Yes, you are missing something by TheInternet · · Score: 3

    Maybe I'm missing something, but I don't see any free registration.

    There are several levels of ADC member. "ADC Online" membership is free, and will get you access to the tools in question. Or, get the compilers from Darwin right now.

    I'm considering developing on OSX, but not if it costs $400 for some GNU based tools. That's almost as expensive as Visual Studio...

    Not only gcc, etc free, but it looks like Project Builder and company will be available for free as well.

    - Scott

    ------
    Scott Stevenson

    --
    Scott Stevenson
    Tree House Ideas
  197. Re:Of course the tools stink, it's a Mac. by Phroggy · · Score: 1
    the lack of ftpd and httpd

    Why would these be missing? I don't recall which FTP server it comes with - wuftpd I think - but definitely comes with Apache. I installed ProFTPd on Mac OS X Server once; aside from a bug in ProFTPd (it wasn't very happy about 32-bit UIDs) it worked fine.

    nothing for media playback except for the proprietary QT4 player (hopefully optimized for OSX)

    Nothing? What rock have you been hiding under? Yes, it's optimized (in fact, it's a new player that's been completely rewritten, for Cocoa I believe).

    and a TCP-IP stack that's about as stable as a tall stack of dimes.

    Isn't it the same TCP/IP stack that FreeBSD uses? Correct me if I'm wrong here....

    All of this adds up to an unpleasant unix experience.

    You don't sound like you've used it; perhaps you should, before you pass judgement?

    Probably the best bet for now is to stick with LinuxPPC, something not blocked by Steve Jobs' arrogance

    Unless you run it on an RS-6000....

    --

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  198. Re:Splitting servers. by be-fan · · Score: 2

    Sure it might be. Since it's a messaging architecture, it doesn't matter what program handles the messages. However, splitting up BSD was probably too much work for the first release, and UNIX isn't exactly designed to be split up that way (tons of calls inbetween the different layres, which must be replaced by messaging.)

    --
    A deep unwavering belief is a sure sign you're missing something...
  199. If I get some extra cash... by Geccoman · · Score: 1

    I'll be tempted to buy a mac now. I've always avoided them like the plague, but now... Oh baby! C'mon, this is pretty cool, and I think I'd enjoy playing around with it.

    --
    I'm on a chair.
  200. Apple pie by Graymalkin · · Score: 2

    I just ordered my OS X beta, I'm really anxious to do some hardcore geek stuff with it. I've been a huge supporter of OS X since it was Rhapsody (which was quite a while ago). I've become pensive as late though, is Apple going to start repeating its past mistakes? I've started shakinmg my head at them for all the product lines and variations of said product lines. Its cheap and easy to produce two different versions of a machine built on the same chassis but it becomes increasingly difficult to built 4, 5 or 6 versions of a machine built on the same chassis (and have it be profitable). Harken back to the days of the obfuscated number days when a 7200 may or may not have been newer than a 6900 and you got really confused when you found out the Powerbook 5400 was only a year different from the 3400. Are they letting their success get to their collective heads? I hope not. This not only goes for strange naming schemes but what about market targets. Apple now has a Unix based OS that can handle some of the more demanding environments thats only a couple years ago Sun, IBM, and SGI dominated in. Are we going to see the iMac become the only box we can afford because the normal G4 line is an exclusive club only for corporations with large budgets (some might argue thats already the case)? It makes me wonder.

    --
    I'm a loner Dottie, a Rebel.
  201. Does Mac OS X have package management? by King+Babar · · Score: 3
    I guess it would be too much to ask for Mac OS X to use rpm (although I'm not sure why), but I would be thrilled to hear that there is a real package management scheme built into Mac OS X. Is there? A real problem with the Mac OS X of old is that it's waaay to easy to scatter installed software all over the place. And I'd like a dollar for every *extra* copy of telnet or Word I've seen installed on a publicly available Mac through the years...

    A real package system would also make it so convenient to upgrade the system, especially during the beta cycle. Right now, there is apparently significant missing functionality in the beta (no airport, no USB printing) that could presumably be "dropped in" as it arrives.

    --

    Babar