Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Apple Businesses

Another Look At OS X 274

mduell writes: "Apple has been close to their golden master copy of OS X for a week or so, but they've still been making nightly builds to squash the rest of the bugs. These last minute copies have all sported a "Build 4K78" in their info window, and many of them have been leaked to outside sources. Reviewers who got their hands on the system wrote extensively about how 4K78 was horrible, yet today resellers across the world received boxed copies marked as 4K78. This article explains what happened, as well as explains how many bugs to expect, and why Apple dropped the ball on a few features (like DVD)."
This discussion has been archived. No new comments can be posted.

Another Look At OSX

Comments Filter:
  • by Anonymous Coward
    OMG yer dumb!

    PPC processors are at 733 MHz, not 500...

    BeOS and cloners are enemies? WHO CARES. All 4 ppl will be pissed... didn't seem to matter for the last few years, did it?

    Motorola layed off worker from it CELL PHONE division. Shit!! No Apple cell phones, what will we do!?!?

    Yes, everyone does GUI and mice. I'm missing your point. Did you just wake from a 15 year slumber?

    Marketing decor... Hmmm.. but EVERYONE does GUIs nowadays.... shit, and they're not marketting mice.... or cell phones either!!! What good are they! Yes, that has done WONDERS for Windows, hasn't it, troll.

    Soin case you missed everything from the past few years, Apple is offering an alternative OS based on the most stable and powerful OS that exists. They have added a userfriendly interface to this power, something many have tried to do with only moderate success, in such a way as to make it usable by children and not just hardcore hackers. They have opened part of the source, while keeping some propriety code so that they could make profit, which allows them to cut margins a little on hardware. I love Linux, but how much does the _company_ Linux(tm) make?

    Someone moderate this ilinformed idiot down...
  • by crayz ( 1056 ) on Friday March 23, 2001 @03:09AM (#345221) Homepage
    If true, then why do people get the same checksum for the final and the RC that was shipped to devs? And why do some with the dev version say it's fast, and some with the final say it's dog-slow(slower than the PB!), if the final is so much different(I know you're not saying "so much" different, but if they removed the debug code and fixed a few remaining bugs...)
  • by crayz ( 1056 ) on Friday March 23, 2001 @02:35AM (#345222) Homepage
    That article is BS. The retail version is bit by bit, byte by byte identical to 4K78 shipped to devs. Here is a post from MacNN forums explaining the situation(was a reply to the same article):
    -----
    No this is wrong, and I've already contacted the author. The article about 4K78 couldn't be more wrong. There was one single, unique build of 4K78 and that's it. The Developer RC CD and the final Retail CD have identical bytecounts, checksums, creation and modification dates, etc. Apple/NeXT's versioning system had ONE unique build number per build, and that is it. Between builds, there can be modifications and builds of components, but each full build with an associated build designation is the only one there is. Now: there were some 4K78's floating around the net that had been imaged with Disk Copy rather than Toast that won't show proper sizes and dates. But any properly created images and/or actual, official CDs will all be identical. There are NO CHANGES, in any way, from the Developer RC CD to today's Retail CD. I don't know how more pointedly to put it. Some people actually go so far as to say Apple is tricking you by making the Retail CD "look like" the Developer RC, even though it's really different. You have to be fucking kidding me. The bottom line is Apple does not have dozens, several, or even two builds of 4K78. There is one, and it was accepted as RC, accepted as GM, and accepted for manufacuring. There WERE NOT daily builds of OS X after RC was declared. 4K78, in its single incarnation, was the end of the line. If people want to *believe* that the Retail 4K78 is different from the RC 4K78, great. But it's not true. Posting articles like this further confuses the issue. The MAIN reason 4K78 was left in was so that people could see FOR SURE that the Retail was the same as the RC: that's the WHOLE PURPOSE of a build number - to uniquely and certainly identify a build. It started out with people being convinced that there were 4K8* series builds (there were never, and never will be, 4K8* builds. Future OS X development will happen in totally different build trees with different versioning, milestones, etc.), with people wanting to believe there was something oh-so-much-better than OS X 4K78. Then, when people were finally convinced that what was in the boxes was 4K78, build number in the About Box and all, they said "maybe Jobs will announce something on the 21st". When nothing was announced on the 21st, they started grasping at straws, making up ridiculous stories about how there were many many different 4K78's and the developer 4K78 was an internal debug version and the retail version is some magical optimized version rebuilt several times, yet still maintains the 4K78 designation and was even designed to LOOK identical to the developer RC to throw people off, with fake checksums and all?? It defies logic. And well it should, because none of it is true. 4K78 is 4K78 is 4K78, period. What's in peoples' boxes this Saturday is identical in every way to what developers received 3 weeks ago. And it's a great release; enjoy.

    PS - Doesn't anyone realize what a support nightmare having multiple builds with the same build number would be. That's just rediculous. For the LAST TIME: any (legitimately obtained) copy of 4K78 is the same as ANY other 4K78.

    THE MAC OS X DEVELOPER RELEASE CANDIDATE 4K78 CD IS IDENTICAL IN EVERY WAY TO THE MAC OS X 10.0 RETAIL 4K78 CD. THERE ARE NO DIFFERENCES WHATSOVER.

    The author of the article was kind enough to respond, and conceded that it was just a "theory", i.e. he hasn't compare the CDs himself. Additionally, he's more referring to illegally obtained builds of of hotline and carracho, which could be fake, improperly imaged, etc. All REAL 4K78's out there, i.e. ones obtained legitimately from Apple, are CERTAIN to be identical.
  • by Aaron ( 1233 ) on Friday March 23, 2001 @06:21AM (#345225) Homepage
    OSX has two local filesystems (let's just leave the network out of this).

    UFS: The traditional UNIX filesystems. This FS is case sensitive and act's like UFS is supposed to act. Apple had to do some clever (or not so clever) hacks to get UFS to invisibly support Mac resource forks (ala .AppleDouble type folders, I don't know exactly how it works, I use HFS+)

    HFS+: The third version of the Macintosh filesystem, this FS is NOT case sensitive, but is case aware. Thus README and readme would be the same file. However, since the FS is case aware, it keeps the case you want. (REaDMe would remain REaDMe). Apple had to do some clever kernel hacks here too, since HFS+ does not support hard links either.
    --
    Though I use a Macintosh, I am not a mac-bigot. I just hate Windoze.
  • well, come on, a "bug" can be anything from sloppy code causing a deadlock to a misspelling in a dialog box, to, one guy thinks that the software should behave differently, etc.

    There's no such thing as a perfect software release. Not everyone will agree on the definition of perfection.

    Win2k had 63k bugs? No shit! It's a HUGE fucking product, it's an OS. (I've also read that a large percentage of the 63,000 bugs figure was simply some sloppy cleanup of the bug database, and that going through it thoroughly left fewer than 5000 actual open issues).

    That said, software is a continuously evolving critter, and just like Homo Sapiens is not the last word in evolution (just the latest), you can't say the same of any given release.

    Now; what IS *wrong* (evil, unethical, bad, stupid) is revving software, without versioning. I don't think that's the case with what's going on with OS X. It takes a stupid stupid organization to do something like that. As someone else said, it's a support nightmare. I've worked for a company that was too spineless to change the version number of their product with each release. Some releases were free patches, collections of bugfixes. 1990's version of the "service pack" in my mind, that's just spineless. It's Marketing hijacking the version numbers for their own purposes, when version numbers are freakin engineering tools for chrisssakes. That's just plain stupid. Support had to write a tool that would checksum all of our files and dump a report that the customer could email us, JUST so we could tell what fucking version they were running.

    That said, I think that Microsoft may have actually hit on something good. The "year" version number. Windows 2000, is the brand name of the OS, and should not be used in any engineering sense to identify the specific OS you're running. Just what you want to buy off the shelf. Close enough. If it's not the right actual version, you just update it over the web. Versioning and updating retail inventory at brick&mortar is just a waste of time. I remember that being the reason why that company didn't want to version their products, because they didn't want 10000 boxes of "not the latest stuff" sent back from the distributors. They also didn't want it to be public knowledge that we had 8 patches in a 6 month period.

    So the brand-name mechanism used by Microsoft is pretty good - unfortunately, it's not applied in any rational way to the "engineering version" that you see in the System control panel, or tech support tools. It's build such and such, service pack X. I believe that is wrong, and it's something that's trying to be a lie, and not even succeeding at that. A service pack should rev the version number of the OS, and that's all.
  • Heh!

    Well, it would be easy to modify that yourself, with Slash 2.0, on your own site. You'd have to ask Rob if we would want it on Slashdot, I'd guess no ...
  • Wow. Wow. You really think that with market share in the single digits, Unix (which does not count existing MacOS share - OS X gets to start at zero) won the OS wars.

    Man, what a pyrrhic victory that must be. We win with oh,let's call it 5% to be generous, and Windows lost with ~90% to be stingy. Yeah, I bet Bill cries all the way to the bank.

    Windows, and the stuff that runs under it is too attractive for chip manufacturers to ignore as we move to 64 bits. If it can't run on them, no one's going to bother trying to sell them anyway. (except possibly as servers, where Unix has a chance, but is still getting encroached upon by Windows) And sooner or later they will succeed, just as they manged to move over to 32 bits from 16.

    The OS wars are indeed over, but the winner is the platform that natively runs Windows software. (which doesn't have to be Windows exclusively, but will be as long as MS is intact)
  • Some of his stuff is a bit skewed, in that he purposely made the alternative he did not like harder. For command keys the placement of the necessary shift key was awkward and often he used the top-row function keys, both of which are the slowest to type. I also complain a lot about his dismissal of contextual pop-up menus and insistance that top-of-screen pull down menus are faster, because he refused to test pop-up menus where they pop up with the mouse already pointing at the last item that was chosen (which imho makes it many many times faster than any pull-down menu system).

    However he has many good points as well. Just ranting that not everything he says should be taken as gospel...

  • I am not being contradictary. What I am saying is that the file system should have NO "case insensitive rules". This is extremely simple to describe and thus unless the programmer is a total idiot the program will agree with the file system as to what filenames are unique.

    Once this horrid problem is solved, the program is free to make up any rules it wants to map stuff typed by the user to file names. My best example is that they can now do spelling correction reliably, something that nobody in their right mind would put into a file system, but something I consider equivalent to case matching.

  • by spitzak ( 4019 ) on Friday March 23, 2001 @10:22AM (#345242) Homepage
    Steve Jobs has something against multi-button mice, I think he had a bad experience in his childhood where he pressed the wrong button. It appears he has been fighting his engineers on this ever since.

    This is most evident in the NeXT, which had a 2-button mouse. There was a control-panel "preference" that said "make the buttons act alike". This made the right-mouse button act like the left one so it was a single button. The machine shipped with this mode set by default.

    The really odd thing about it was the implementation: turning on this mode actually changed the "server" (similar to an X server) so that clicking the right mouse button returned an event indistinguisable from a left button. It was not done inside the NeXTStep code which ran in user space, which would seem to be the obvious implementation. Unlike everything else on the server (like keyboard mapping!), you could not change it with PostScript code, and only a program with suid privleges could change the setting (and even then it was undocumented). As far as I can tell, every other preference on the control panel was done simply in user space by NeXTStep.

    He really really wanted to make sure it was impossible to write a program that used the right button, and was willing to make bad software design just to enforce it!

  • by spitzak ( 4019 ) on Friday March 23, 2001 @10:33AM (#345243) Homepage
    In general the problem is that programs may scan the directory in order to determine if they are going to write over a file and fail to detect if they are. This is a serious problem even if the program is aware that the file system is case insensitive, because the program's idea of what letters match may be different than the file systems (especially true for Unicode filenames!)

    For this reason I have said many many times here that file systems should be case sensitive, in fact the file system should just treat filenames as strings of bytes and only an identical stream of bytes will identify the same file (thus if UTF-8 is used, only a single encoding of a name works even though the UTFUnicode mapping is not really 1:1). Only by using such a scheme can the file systems be fast and free of security holes.

    The problem is, many people seem to think that if the file system is case sensitive, that the user has to type filenames with the correct case. This is false, there is no reason that user-level programs cannot do their own case-insensitive search for a matching file (they could also do more complex things like spelling correction).

    I'm not sure why so many otherwise bright people are under this delusion, but it is causing a great deal of trouble.

    It is good to see that Apple is supporting a case-dependent file system. It would be interesting to see their user-level solutions to making this user friendly, perhaps when (if?) they do it it will wake up all the idiot FS designers and NT defenders out there.

  • YOU should go back and read The Mythical Man Month. What the poster was saying is that this is precisely the kind of problem that _is_ solvable by third parties. If the interface is there, more people will have it done faster. If the problem is architectural, _then_ more people will not make it go faster, which is precisely what the poster was saying. There are jobs which are very parallel, like driver-writing. Architectural jobs, however, are not. If I have X parallel jobs, then I can always get improvements with up to X number of people. For a stable system, driver-writing does not require the communication bottleneck that is described in the Mythical Man Month.
  • Most of these are their own fault. As far as #2, all of the terrible hardware configurations to support are a result of their own making - like Plug-N-Play and WinModems. Older stuff doesn't need to be supported, especially since Win2K only supports 64Meg machines.

    Given all of that, look at how far the Wine people have come with many, many fewer programmers. Their task is essentially the same as Win2K's.

    One of the problems with all of this is that everyone is trying to push out large, bulky, crappy software. It _is_ too big to do right all-at-once. They fact that they are trying is proving either their ignorance or their contempt for their customers. Why not incrementally improve? Ask Bill Gates. He'll tell you "bugfixes don't sell software". They can't take any of their 2 Billion in _profit_ and fix your
    bugs. Not to mention that you are the one who gave them 2 billion dollars, but that's a different story. Everyone would be much happier if all of IT people stopped "innovating" and just made something that worked. STOP ADDING FEATURES!
    Think of every technology that someone has had to add compatibility for, and ask yourself, "was that technology really necessary? Did it help someone out?" Like WP file formats. I applaud SodiPodi for using the industry standard file format, rather than creating their own and importing/exporting. If someone makes something simplistic, everyone says, "it doesn't do X!" Well who cares! It works. It works well. If we start there, and _slowly_ add things, then we will have a true technology infrastructure, and not this bumpy road. This is another reason I love free software, because while commercial software can only sell "innovation", free software places value on bugfixing (not that free software packages are bug-free, but that what a company would pay for would be the support and fixing, not the innovation). Anyway, I'll end my rant here.
  • Actually, no. The Wine team has essentially the same task. The fact that they are building on existing kernels is pretty irrelevant, given that Microsoft was too (I'm sure MS had to modify the NT kernle, but actually the Wine team has patches for the Linux kernel). The major task with Win2K, at least the reason stated for the delays, was that they were having trouble getting the Win32 API working with their kernel. The fact that the Wine team has been generally successful with such a small team shows how well they've done. Win2K was also just re-implementing an existing design with the win32 subsystem, which was the majority of their headaches. I have done quite a deal of design and coding. I am fully aware of what it takes.
  • First of all, cars have bugs.

    Second of all Linux probably has more than 63,000 bugs if you look at what ships from distributors. It's just that people classify bugs differently.

    If I have a window that leaves artifacts if I move it around, that's a bug, even if they go away the next time something is moved over them. In fact, that may be several bugs, especially if it occurs at the driver level (it may happen on 20 drivers, so that's 20 bugs).

    If Mozilla shifts an image one pixel to the left too far, that's a bug, even though anyone but the most hardcore testers may ever notice it.

    Linux people tend to misunderstand what a bug is. We're used to dealing with and complaining about major bugs. Then when someone says, "the O.S. has 63,000 bugs" we think it has 63,000 major bugs. But that just isn't true. Bugs can also be potential race conditions that have never been exploited, or potential memory leaks that have never been looked at.

    For example, if I'm programming, and I'm not sure if something I'm doing will cause a memory leak, I should add that as a bug. If the program is "notepad", there's no reason to ever even examine that bug, simply because notepad isn't a long-running app that will be affected by memory leaks.

    Anyway, I agree that software has too many bugs, and that its the fault of both the distributor for not testing and the consumer for not demanding better. However, I do think you should take any bug count with a grain of salt because many of them refer to conditions that most people may not think of as bugs.
  • that is, there may be some technical reason that these things can't be done on the current release of Mac OS X.

    Technically, the reason is they don't have a large enough number of eyeballs and hands to do the OS, DVD, CD, and all this shit all at the same time by the marketing/morale/fanbase-driven early release date.

    Closed-source software companies, unfortunately, don't have the freedom to release software "when it's done", particularly after they've bought ads declaring a certain date, told the investors they'd release on a certain date, etc..

    Insinuating Mach + BSD can't handle CD burning or DVD playback (technically, not legally) is kinda unreasonable, if only because I'm sure someone can port cdrecord at the very least :p

    Your Working Boy,
    - Otis (GAIM: OtisWild)
  • On the article that was linked he refers us to another related article he has written. You can go directly there by clicking here [artificialcheese.com]. The second one is a worthwhile read too. Everyone should check it out.
  • Yeah, I noticed that too. Too many of you!

    Fixed it though. Hopefully it'll stay up for good.
  • That's the thing. You're again comparing the developer CD to the final CD. The people who complained about it being slow and not working on certain computers were most likely using internal Apple builds that were never publicly released. If you have checksum verifications proving that your developer CD is the same as your final CD, that's fine with me. All I'm saying in the article is that lots of people downloaded bad bootlegged builds of 4K78, and got VERY confused when they found out 4K78 was the copy appearing on the shelves.
  • by batobin ( 10158 ) on Friday March 23, 2001 @01:59AM (#345264) Homepage
    I don't think the author is proposing a "none is better than some" plan. He is merely saying that it's better to have an almost flawless overall system, missing a few specific features, than have an overall crappy system. In a situation such as Apple's, these are indeed the only two choices of the matter.
  • by batobin ( 10158 ) on Friday March 23, 2001 @03:00AM (#345265) Homepage
    The thing is that they're NOT fixing bugs right now. They neglected to include a few features (like DVD) in order to meet deadline, but still nail all the bugs. Personally, I'm glad they chose this route.
  • by batobin ( 10158 ) on Friday March 23, 2001 @02:58AM (#345266) Homepage
    True, the person who wrote that contacted me, but he wrote that statement before we got our discussion resolved. We came to the conclusion that he was not aware of the 4K78 builds that I was referring to, only of the 4K78 build that he received in the mail.

    The truth is that there are multiple 4K78 builds out there, and every Apple employee I've talked to acknowledges this. The person who wrote that comment only saw two of the copies going around, and assumed they were all the same. This is strictly untrue.
  • Despite the tone of occasional disappointement at "missing" features (so write it or port the Linux version,) I'm glad to see that /.-ers are more concerned about the new qualities of the OS than its short comings.

    Jobs was right. Just like Apple became the largest unit sales seller of RISC machines within one year of the introduction of the PPC boxes, Apple will become the largest unit sale seller of Unix boxes within one year of the introduction of OS X.

    That's twice Apple has accomplished a complete change of supporting architecture without throwing the baby out with the bath water.

    M$ must be feeling a little ill after failing at least twice to get off the x86. The coming 64 bit machines (needed to handle biometric information to turn packets on the 'net "black," and make life much, much harder for the "script-kiddies,") will wipe M$ off the map.

    The OS Wars are over. Unix won.
  • This is a golden opportunity, these next few months, while major developers take some time to roll out the big applications to show the power of Open-Source and free software.

    Imagine what market/mindshare inroads can be made, if while waiting for an OS X version of Photoshop, Apple users, eager to try out some native OS X software, download and start playing with GIMP for Mac [macgimp.org]. Or maybe Abiword [abiword.com] will get a build of OS X into their hands?

    Hopefully soon it will be as common to see apps all packed up for OS X as it is to find an .RPM today...

    W
    -------------------

  • This was also a feature in Mac OS 9, btw.
  • What, like the Audis that used to have the sudden unwanted acceleration problem?

    It turned out that the "sudden unwanted acceleration problem" was most likely due to having the brake and the gas slightly too close to each other. It was, depending on your opinion, operator error or a user interface bug.

    People think about UI as minor issues, but in the case of the Audi 9000S, it was pretty serious. Kinda funny, that.

    -jon

  • If it were just a matter of driver support, it could have been solved by throwing contractors at the problem.

    Welcome to Brooks' Law. It says "adding more developers to a late software project makes it later." If you don't understand why this is true, then you aren't qualified to open your yap about why Mac OS X is missing DVD playback and CD burning.

    -jon

  • I'm just curious, how does one interpret Apple's version numbers? I'm used to Microsoft's four number scheme (for example, I'm using IE version 5.00.2920.00) and Linux's three number scheme (Linux 2.4.2)

  • What the heck kind of modern "multimedia" system doesn't have DVD and CD-RW support???

    Neither Windows or Linux have otu of the box support for both.


    MOVE 'ZIG'.
  • No, this statement is true. Windows XP is not a released product, and Videolan does not allow you to play DVD's.

    The fact of the matter is that there is no other released product that will do what you are criticising Mac OS X about.

    Ridiculous.


    MOVE 'ZIG'.
  • by SuperKendall ( 25149 ) on Friday March 23, 2001 @06:51AM (#345282)
    Your answer is not quite right - I plan to get an OSX box for Java work as well, and possibly one as a server.

    Why? One simple reason is that at the core, Mach (which is what OSX is built around) offers light-weight threads which should mesh better with the threads Java uses than Linux or BSD alone would.

    Also, from what I've read it seems like there is much better Java integration throughout the system (like a Java Coco (sp?) API) so I stand a better chance of being able to customize some of the UI using Java.

    Also, a last point unrelated to Java is that I simply have to offer what support I can to an OS that offers a sane standard package management structure. I think that for everyday use, OSX will require a bit less of my time to work with than Linux. Not that I still wont have other boxes that run Linux, I just plan to do most of my work in OSX.
  • by SuperKendall ( 25149 ) on Friday March 23, 2001 @07:50AM (#345283)
    I think there needs to be a new moderation category for ill-informed repetitive posts like this - "Nuke". It would take all five moderation points to perform, and could only be done once a month. The effect would be the removal of the post, the canceling of the user account and/or IP that generated the post, and removal of all other messages from that poster/IP. It would also launch an IRC bot that would make constant disparaging remarks about the user in a variety of forums.

    Then, we would cease to hear from people that do not realize the mac supports USB mice and thus three button mice - with wheels.

    A side note - the Mac ALSO supports single button mice, so it is actually superior to just about anything else by virtue of supporting a wider range of mice. Can you imagine trying to use a single button mouse in X? I guess you don't care about usability of systems at all, yet another reason why we need a NUKE moderation.

  • by Bimble ( 28588 ) on Friday March 23, 2001 @05:54AM (#345284) Homepage

    I couldn't find any info in the article if there is no support for DVD or just no DVD player bundled.

    No player - I've been using the OS X Beta on a G4 with a DVD-ROM drive, and had no problem accessing DvDs. You can always dual-boot with Mac OS 9 to play DVDs until OS X gets that feature - it's not hard to do (just install Mac OS 9 on a separate drive or partition). I know I'll be dual-booting to the classic Mac OS for a while anyway, since not all hardware is going to be supported in Mac OS X for a while, and I'm sure a lot of 3D-accelerated games will play better under straight Mac OS 9 without going through the compatibility layer.


  • Cygwin & MPW is the answer to heterogenious networking and collaboration?

    Let me remind you, we are the minority. It's about being able to work and co-habitate with Windows users that makes an alternative OS possible for me. (Maybe in your job this isn't an issue, but for mine it is...)

    It's not just about file sharing and running Lynx in a windows Cygwin unix prompt. It's about being able to track modifications on a word document thats been passed around to 5 people hammering down a project. Things like that, unfortunately, lock me into having to have -a- windows machine to do activities such as this.

    I have a DUAL PIII 800 with Ultra SCSI 166 and plenty of ram... but VMWARE still isn't a great solution FOR ME (disclaimers apply). It's just slow. I like native apps.

    But again, why would I want to run Cygwin?

    Stability of Windows with the applications of Linux? XWin32 is a much better solution anyway.




    --------------------
    Would you like a Python based alternative to PHP/ASP/JSP?
  • .. because you will spend MANY MANY hours using it and it will definately affect your day.

    Your arguments are very valid.. probably just comes down to choice. I work 8 hours a day (at least) on my machine developing / adminstrating / planning along with the normal day to day office application requirements.

    If I am going to be spending more time on this machine than I do sleep, why not have a nice one that I like and enjoy.

    I don't give up anything, my linux box is still within kicking distance of my G4, but $1,500 for a OSX system which runs very quick and gives me all I need.

    I could save $200-300 (if I build the machine myself) on semi-equivilant hardware, but why? I will treat myself to something that I enjoy using.


    --------------------
    Would you like a Python based alternative to PHP/ASP/JSP?

  • I can use MS Office / Explorer, etc from the Mac, I can't use those on my Linux box unless I boot into Windows.

    I find myself more productive in the Mac Interface than I do in KDE as well. Just about having everything in one place. (Though you can do the same thing using 2 Intel boxes and XWin32 on windows.. but then you are stuck using Windows as your primary workstation, which I am trying to avoid.


    --------------------
    Would you like a Python based alternative to PHP/ASP/JSP?
  • by Pengo ( 28814 ) on Friday March 23, 2001 @01:04AM (#345289) Journal

    I have build 4k73 (very close to final version) and it has a tool in the control panel that you can have it fetch updates from Apple. It is added to the cron automatically if you wish and it will look for updates every night or every friday for example.


    --------------------
    Would you like a Python based alternative to PHP/ASP/JSP?
  • by Pengo ( 28814 ) on Friday March 23, 2001 @01:14AM (#345290) Journal

    I have been using it for about 4 weeks (Got build 4k73 when it was first released).

    With exception of a the occasional IE crash (not OS crash) the system ran without a hitch. I had it on a iBook which is a relatively slow and old machine. (Especially when compared to my Dual PIII 800 SCSI 166 running Debian SID with KDE).

    I am not one of those people that need DVD playback. I have a DVD player and TV for that. I just need good Java support and a decient terminal and X windows. OSX gives me all of that.

    My G4 just arived this week and now all I need to do is buy a Gigabit ethernet for my Linux box and I have one of the coolest development environments I could ask for. (Linux apps for server and Java profiler...) I was able to get JBuilder 4.0 Enterprise for Windows actually working on OSX. :) (Just had to create a few sym-links and worked like a charm!)

    I was quickly able to get wget, vim, Lynx, Python and Perl working fine on the machine and was quite comfortable. As far as the Unix side of things, the only problem people might find is that the directory structure is a LITTLE bit different than what you are used to. (Still has /etc /usr/local /usr.. etc).. user directories sit in /Users/* (instead of home or /usr/local/home).. but again, you can just symlink your way back to a comfortable shell experience.

    But the nice thing is now I can run Photoshop, JBuilder, IE, Mozilla, Netscape, iMovie (Which is actually a DAMN cool program ..

    But OSX most importantly stays out of my way and just lets me work. :) Thats nice.

    Also the fact that Apple is packaging everything needed to do full development is pretty neat. They are starting to learn that they will get market acceptance with empowerment of the programmer.

    I am also happy that OSX allows me to very openly work in a heterogenious environment as Windows and the old MacOS seem to do the exact opposite. I see it as Linux, BSD, etc just gained a great ally. ;-)


    --------------------
    Would you like a Python based alternative to PHP/ASP/JSP?
  • I'd like to see my Swing app with the Aqua Look and Feel. Is it right that one is only allowed to use it under Mac OS X (although it should be simple to use it anywhere else)? Is there a place where I can download the necessary classes? I don't want to distribute my code, just take a look at it.
  • I couldn't find any info in the article if there is no support for DVD or just no DVD player bundled. To me, it's a big difference. If it's just "no DVD player", then it's kinda funny how people are crying about it. Meanwhile, when Microsoft bundles a web browser, *THAT* is a reason to cry about. Hmm.. So which is it? Should stuff be bundled or not? Ok, sorry, sorry, I know there were other issues invovled, like killing Netscape and integrating it so deep into the OS that you couldn't separate them without a surgical operation. I just couldn't resist. But seriously, if it's just that there is no player, then it's no big deal IMHO. If there is no support for DVD drives, then THAT is bad, tho I imagine that it won't be long before you can download those from their web site anyway.

    In any case, if I owned a Mac, which I don't, I wouldn't get the first version of Mac OS X in any case. I'd wait for Mac OS X.0.5 or whatever, some 6-12 months after the release of this initial version.
  • I understand the sympathy you are expressing here. But, in the real world, where so many of us live, that's just the way it is.

    Of course, every publisher aspires to perfection. Never forget, however, that the perfect is the enemy of the good. No Q/A process is limited to assuring installation and updating -- everyone checks everything. But checking doesn't fix bugs, fixing bugs doesn't fix bugs.

    The reality is that operating systems don't work. Never has, never will. Many work well enough, and some are excellent. Pretending otherwise gets you to whining about something that never will, and never can be.

    Which is why its hard to take this kind of criticism seriously.
  • That may be true for Linux, but a commercial OS (like OS X) has to have as few bugs as possible.

    Exactly which company has ever complied with this standard, even for applications? Certainly, no major release of any Apple, Macintosh, IBM or other operating system with which I have worked has come close to that standard.

    The perfect is the enemy of the good. You will wait forever if you insist on these ludicrous and unrealistic expectations.

    Of course software should be bug-free. It can't be. Of course software should have as few bugs "as possible?" What is possible? Do we mean as few bugs as are possible after all testing and programming can be accomplished, without any desire to release a product on time? Or do we mean as few bugs as are possible after a reasonable Q/A process has identified known and outstanding problems?

    EVERY major release of MacOS was feature-incomplete and had bugs. So what? Same is true of Microsoft, who couldn't even pretend the 3.X versions of Windows constituted an operating system, let alone a feature-complete bug-free (so far as possible) system. Windoze ME had 64K plus KNOWN bugs at release.

    As I said, it is hard to take this kind of criticism seriously. Use REAL-WORLD standards, in REAL-WORLD environments, and call spades spades.

    That said, this release of OS X is not really intended for the average consumer (whatever that means); it's meant for people who pretty much know what they're doing with a computer. Those types will be much more likely to download OS updates than most, but it's still a falsity to say that the OS X CD's job is to "serve as a vehicle to reduce the amount of time/bandwidth necessary to install the software."
    That said, this release of OS X is not really intended for the average consumer (whatever that means); it's meant for people who pretty much know what they're doing with a computer. Those types will be much more likely to download OS updates than most, but it's still a falsity to say that the OS X CD's job is to "serve as a vehicle to reduce the amount of time/bandwidth necessary to install the software."

    Reasonable people may differ on this point. Time will tell. So far as I can tell, even the public beta was, infinitely more accessible than any unix distribution that has ever existed.
  • That may be true for Linux, but a commercial OS (like OS X) has to have as few bugs as possible.

    Exactly which company has ever complied with this standard, even for applications? Certainly, no major release of any Apple, Macintosh, IBM or other operating system with which I have worked has come close to that standard.

    The perfect is the enemy of the good. You will wait forever if you insist on these ludicrous and unrealistic expectations.

    Of course software should be bug-free. It can't be. Of course software should have as few bugs "as possible?" What is possible? Do we mean as few bugs as are possible after all testing and programming can be accomplished, without any desire to release a product on time? Or do we mean as few bugs as are possible after a reasonable Q/A process has identified known and outstanding problems?

    EVERY major release of MacOS was feature-incomplete and had bugs. So what? Same is true of Microsoft, who couldn't even pretend the 3.X versions of Windows constituted an operating system, let alone a feature-complete bug-free (so far as possible) system. Windoze ME had 64K plus KNOWN bugs at release.

    As I said, it is hard to take this kind of criticism seriously. Use REAL-WORLD standards, in REAL-WORLD environments, and call spades spades.

    That said, this release of OS X is not really intended for the average consumer (whatever that means); it's meant for people who pretty much know what they're doing with a computer. Those types will be much more likely to download OS updates than most, but it's still a falsity to say that the OS X CD's job is to "serve as a vehicle to reduce the amount of time/bandwidth necessary to install the software."


    Reasonable people may differ on this point. Time will tell. So far as I can tell, even the public beta was, infinitely more accessible than any unix distribution that has ever existed.
  • What, a distribution CD-Rom for buggy software? First, all software of any complexity has bugs -- always. There are only three kinds of programs, those with bugs you knows about, those with bugs you don't know about, and those with both.

    Fixes to software do not change this. A fix of a bug you know about can at best change a type A or type C program to a type B program.

    Nobody has been in this business for very long who does not understand this.

    So, the question isn't whether the distro is buggy -- the question is whether the distro works well enough that known bugs can be repaired by updaters, ideally through the network. If we can install it, boot it, get online, download the updaters, and run them, the distro did its job.

    Physical distros serve two purposes -- (1) to serve as a token of ownership; and (2) to serve as a vehicle to reduce the amount of time/bandwidth necessary to install the software.

    I assume OSX, as delivered, will be a type C program. It will have bugs and megabugs. I also presume that Apple did sufficient Q/A to assure that the installation and updating processes will work. If so, thats all that it needs to be.

    To the naysayers, what is the alternative? Can anyone suggest a fully-tested on-time bug-free distribution CD?
  • Here's two things that I will get out of OS X;
    1. I can use some killer Mac apps that I won't have for a long, long time on my un*x machine; ProTools, FinalCut, PhotoShop (I have a hard time with Gimp's interface). This means a machine I can have at home that doesn't scare my wife and doesn't disgust me.
    2. I work with a programmer who does a lot of Java programming under Windows. Finally, I will be able to throw out Samba and just give him NFS mounts, and I won't experience any more skunky permissions errors, user mapping due to his weird NT setup, etc. And, my graphics folks can do the same, so I can throw out netatalk. Two big filesharing apps out the window.
    I find it weird that you can't imagine a Java programmer using Photoshop, ProTools, etc. You must hang around some pretty boring, limited people. And I don't think that because I use an xterm, I'm not making use of the graphics subsystem. If I can mouse over and see what's going on in a minimized terminal window, I am. I 've still not figured out how to manage the titles on my xterms properly so I can do this in WindowMaker.

    Boss of nothin. Big deal.
    Son, go get daddy's hard plastic eyes.
  • While I hate microsoft with a passion, you have to remember the tremendous problem they are trying to solve.

    They have to write an OS with the following criteria:
    1) support for legacy apps (meaning old APIs and all of their little quirks)
    2) support every conceivable combination of the bizarre and increasingly crappy pc architecture
    3) eliminate all bugs from a 40 million line codebase

    I don't care how many developers you throw at this problem, you'll never get it 100% right, and it's amazing Microsoft can do as well as they do.

    Doug
  • by EasyTarget ( 43516 ) on Friday March 23, 2001 @02:03AM (#345306) Journal
    Bugs in an installation media don't really bother me.

    They should, the vendor has your purchase now, what guarantee do you have they will fix the bugs?

    I work for the Technical Support division of a major (multi-platform) vendor. We do this shit all the time, release stuff to satisfy a marketing schedule, then decide to drop fixes that -really, really- should have been in the released product.

    All the time we (as customers) accept buggy products with a promise to 'fix it in a service pack', companies will not improve the fundamental reliability of their products and release practices.

    EZ
  • Is the Java support full-fledged? Until Mac OS X, MacOS has always been behind the Java boat, so we always have to be limited by the version of VM MacOS supports, and bend over backwards to accomodate any idiosynchrasies. If modern Java support on Mac OS is finally now non-vapor, Mac clients have immediately jumped from the end of the pack, straight to the top, in being both Unix, *and* Mac. In this ideal world, we program more towards Mac OS X, and then we have "free" *nix versions...or we can program to *nix and get "free" Mac OS applications. Windows becomes the ugly duckling then...although Windows support is currently the best...so I guess the world of Java development looks an order of magnitude more cheery ;)
  • "Has the software industry really sunk this low?"

    It's always been this low.

    "Has the meaning of software "release" and "purchase" become this perverted?"

    Yes, actually it has. Into a "service", "support", "widget frosting". How do you think companies are making money off "free" software?

    "Are we really expected to just accept that anything we buy is a work in progress?"

    Yup. Unless of course you are willing to 1) wait forever for the company to put out a "perfect" product and then 2) be totally satisfied that the product will never ever reveal a bug (being "perfect" of course), and so you will never ever need any type of support. Unless you have an infinate lifespan, it is infeasible to wait for software to be "perfected". Releases are just snapshots in time of a fairly stable state.

    "I honestly can't believe there are people out there who think that since you can't catch every bug, you aren't responsible for the quality of your software."

    Who said just because you can't catch every bug you are not responsible for the quality of your software? You are responsible...that's what bugfixes, patches, and, imagine this - newer releases - are for.

    You are clearly living on another planet if you think software is something you can just manufacture on an assembly line, slap an "inspected by #57" sticker on, and shove to the customer as a final, "perfect" product.
  • oh for fuck sake man. You can just hold the apple key to do the second mouse button. I do it all the time when using the Mac's at work. For people who tout that they would rather "learn to use the command line" than be "instantly able to use a GUI" most geeks refuse to learn anything about the Mac before they start dissing it.
  • Comment removed based on user account deletion
  • by bnenning ( 58349 ) on Friday March 23, 2001 @08:05AM (#345314)
    Is the Java support full-fledged?

    Darwin/BSD (capsize) (ttyp2)


    login: brian
    Password:
    Welcome to Darwin!
    [capsize:~] brian% java -version
    java version "1.3.0"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.3)
    Java HotSpot(TM) Client VM (build 1.3.0, mixed mode)
    It's a full 1.3 VM, and it comes with javac and the other command line tools. At my company we have a team of developers working on a complex Swing app using lots of Java 2 features. Last week we installed it on my Powerbook with OS X as a test (we got the developer release early) and it worked perfectly, including rendering the Swing widgets in Aqua.

    Until Mac OS X, MacOS has always been behind the Java boat, so we always have to be limited by the version of VM MacOS supports, and bend over backwards to accomodate any idiosynchrasies. If modern Java support on Mac OS is finally now non-vapor, Mac clients have immediately jumped from the end of the pack, straight to the top, in being both Unix, *and* Mac.

    Exactly. Remember, classic Mac OS has a terrible architecture; I was impressed that Apple could get Java working on it at all. With OS X's Unix foundation Java support will be an order of magnitude better.

  • BSD UNIX just moved onto the desktop, which is pretty cool.

    I already run Linux on my iMac, but X doesn't seem to run too well on it, and OSX looks like it might just be worth the trip down to the warez channel.

    When they replace my Linux-runnin' P3-500 at work i will look pretty seriously at a GeForce3-equipped G4.

    Since most of my software development is done with Java, OpenGL/SDL, and Perl, it seems that this machine will deliver the goods as an affordable 3D workstation.

    Plus it runs Lightwave and Photoshop, which means i can finally kick my Windows habit permanently.

    I just don't understand how anyone can possibly say this is, in any way, a bad thing for Linux, UNIX, Apple, Sun and least of all the users of the new system.

  • To me, these statements seem to clash:

    "the program's idea of what letters match may be different than the file systems"

    "there is no reason that user-level programs cannot do their own case-insensitive search for a matching file".

  • Isn't the /. crowd the one so obsessed with diversity? Besides, BeOS isn't based on *NIX either.

    PS> Yea, I know BeOS isn't major, but does RedHat have a contract with Sony? [benews.com]
  • I wasn't trolling. Linux 2.4 IS a better system than Mach/FreeBSD 3.2. First, Mach is a pretty crappy microkernel. Second, FreeBSD 3.2 is several years out of date, and FreeBSD 4.0 is a much better system. I don't know how Linux 2.4 stands up to FreeBSD 4.0, but I know that they are close, which suggests that 3.2 couldn't compare to Linux 2.4.
  • by be-fan ( 61476 ) on Friday March 23, 2001 @02:16PM (#345319)
    I don't know how much sense porting OS-X to Linux would make. Altough Linux 2.4 is a much better system than Mach/FreeBSD 3.2, by taking out BSD and Mach, you get rid of much of OS X. Maybe you're thinking of porting Quartz, Aqua, and OpenStep to Linux? In that case, you won't be happy to hear that all of the above are closed source, and thus will not run on x86 unless Apple ports it.
  • What do you get out of OS X that you don't have in Linux...

    MS-Office, Photoshop and a hundred other graphics applications, and a better graphics subsystem than X while also retaining the ability to run X and just about every other Linux app around (including the exact same JDK as Linux).

    DB
  • Sorry, you're going to have to wait for MSIE to go to Cocoa, not Carbon to have a prayer of getting MSIE on even PPC Linux and even then you are going to have to get a very advanced gnustep running that mimics the vagaries of Cocoa.

    DB
  • "DVD playback and CD burning are so integral to Apple's current marketing that their lack suggests a deeper problem -- that is, there may be some technical reason that these things can't be done on the current release of Mac OS X. If it were just a matter of driver support, it could have been solved by throwing contractors at the problem. It may be something more architectural, something that was realized too late and that would have ripple effects throughout the system. "

    Ah, throw contractors at a problem, Hah! With that attitude you probably think that 9 women can make a baby in a month. Try to dig up and read "The Mythical Man Month". It might wake you up.

    DB
  • $1000 gets you the professional burner package which gives you the ability to burn commercial level disks. The MPAA would still have hives if it doesn't have some sort of copy protection.

    DB
  • What I'm saying is that if the very drivers are the problem (as some of the rumor sites are saying), throwing more workers at that problem isn't likely to fix it. In fact past experience in the industry has shown that you are actually likely to get a slowdown as people have to take time to get the new people up to speed instead of coding. There's a religious war, but it's not OS specific.

    DB
  • I sort of doubt that Apple to this point has any major drivers that don't already have teams on them. Some of the drivers were done in time, others were not. To add people to a particular driver team in order to speed it up so that cd/rw drives have a generalized driver is going to get you sub par results in terms of efficiency perhaps to the point where adding people makes the code come out later.

    In your terms, I have X parallel jobs with X parallel teams on them. Y% of those teams are behind schedule so I should add people to those teams that fall in group Y and I will get an arithmetical improvement in efficiency. Bzzt, that's a recipe for disaster and very much the subject of "The Mythical Man Month".

    DB
  • interview [cnet.com] Jef basically pans the OS, although he is obviously a complete idiot.
  • Read what I said. I'm not saying I could care less about bugs. What I said was: I am not concerned with trying to keep my installation media current with the latest patches and fixes. I install the raw OS then patch/update.

    IE, every time a new NT service pack comes out (what is this last one, the eighth?) I don't re-burn my install CD to overwrite the source files with the newer SP version. I just go ahead and install SP0/1/2 and then when I'm all done install SP4/5/6. Ditto for the critical updates/hotfixes/security bulletins. I head over to the update server and check off everything except that f'in Media Player 7.

    It saves me time, it saves me CD, it saves me hassle. The only thing I need to carry around with me on CD is enough of the OS to connect to the Internet and from there I can pull down whatever else I need. That is what Apple should be focusing on, in my opinion.

    - JoeShmoe

  • See my above response. [slashdot.org]

    http://slashdot.org/comments.pl?sid=01/03/23/030 22 8&cid=102

    - JoeShmoe
  • by JoeShmoe ( 90109 ) <askjoeshmoe@hotmail.com> on Friday March 23, 2001 @01:00AM (#345337)
    I'm curious what kind of update/package system OS X uses...I have searched and not found word one about it. I assume since it is UNIX, it can use whatever current standards (RPM?) there are but this seems like a feature Steve Jobs would be hot to get his hands into.

    Bugs in an installation media don't really bother me. God knows I'd have to be insane to leave any version of Windows the way it comes on CD (My most recent NT4 CDs are still just SP1!). So then why not push out the OS X CD on the due date and then throw out nightly "recommended updates" until its working the way it should?

    - JoeShmoe

  • talk about a lot of hot air about nothing! Journalists writing about what other journalists said in connection to a story about a pre-release piece of software.

    We'll all be able to see for ourselves what the shipping version of OS X is like within a matter of hours. Some of the journalists, posters, and rabid pro and anti-Macheads will be proven correct, while some will be proven wrong.

    Life will go on. The sun will rise in the morning and set in the evening.

  • And who the heck is the "Open source Initiative" When did they become the be all end all of defining what is and isnt Open source? Heck i could start up my own "Open Source Liscence Standard Committe" and declare that the APSL is the one and only true open source liscence on earth, and ESR and RMS can eat my shorts. The point is, regardless of liscence, if you go to apple you can download the source for darwin, binaries for darwin, you can modify the code and recompile it as much as you want, play around with it, add features if you want etc. Maybe the exact wording of the liscence isnt what your standards committe wants, so they dont certify it. If it looks like a duck, and quacks like a duck, im gonna call it a duck.

  • Or Install Toast. My roommate has a Beige G3 and is looking into OS X "real soon". He's hoping that it is good enough to keep him on the Mac Platform. It's pulling me in as soon as I can afford one of the TiBooks.

    However, Toast, which is apparently a large CD-Burning and CD-Imaging program, has an OS-X version?

    It is an application that wasn't written yet because Apple want's it done right. Also, the Apple DVD and CD-burning software isn't run-of-the-mill stuff like their shitty Windows/Linux counterparts, it is an integrated system that allows drag-and-drop CD-burning, etc.

    Expect the final versions to rock.

    Just because the "built-in" software on the PC sucks doesn't mean that the Mac ones do.

    Alex
  • Hey! What TDi problems? I love my TDi, read Fred's forums, etc - I have not heard of anything THAT serious...

    What is the issue?

  • OK, sure OS X doesn't have DVD and a few other things that didn't get quite finished in time for the March 24th deadline. Apple *had* to meet that deadline, they have a complete rewrite of their operating systems and what do operating systems need? Programs. Developers needed to have a deadline too. If Apple had said "sometime 2001" developers wouldn't have done anything, but come tomorrow quite a few people are going to be running OS X and these people want cabronized and coca apps. I think it's great that Apple decided to concentrate on making the core of OS X better and OS 9.1 better for Classic comptibilty then work on something trivial like a DVD player. I would not be happy if I heard "Yeah, some older applications won't run under the Classic environment, but we do have DVD!"

  • You're suggesting that PowerPC machines, most of which are in the 200-500 MHz range (if they're to be supported), are going to have difficulty giving a CD burning or DVD playing process enough CPU time in a pre-emptive environment?

    Hogwash... if you can burn CDs on Linux with a P133, you'll sure as hell be able to do it on MacOS. As for DVDs, I may be wrong, but I don't think Apple ever shipped any system with a DVD player that didn't run at least 300 MHz. And even then, they had hardware decoders.

    If it's not ready, it's because it's not ready. Not because the hardware - which is easily among the best in its class - can't handle it when running a BSD OS.

    --

  • The 233 iMacs [apple.com] did not offer DVD-ROM drives as an option.

    The first iMac to offer DVD was the 400 MHz iMac DV [lowendmac.com], which, as a matter of fact, did offer hardware MPEG-2 decoding through its ATI Rage 128 VR graphics.

    --

  • The 'UDF' fileformat _does_ mount however, and you can see the files xxx.vob lying all over the place.

    Then somebody can write a player app, or a format translation utility (which is easier, because it doesn't have to be real-time.)

  • by Animats ( 122034 ) on Friday March 23, 2001 @08:22AM (#345357) Homepage
    Perhaps the reason that MacOS X doesn't have a DVD player is related to CSS. Maybe they haven't been able to obfusicate the crypto system and the region lock key well enough. Too many people know how to find out what a UNIX program is doing.

    Does MacOS X have a DVD driver at all? Can you access the drive? Maybe someone will write a third-party player.

  • Ah, but the point is that folks shouldn't HAVE to read the 'big websites' to get features that were promised to be in the main package. It's kinda like Ford saying 'On our new SUV, the brakes ship disabled, by default, but anybody who finds 'How To Enable The Brakes' on our website can easily enable them themselves. Fine for an enthusiast, a swift kick to the Jimmy for commercial software. Don't forget, these are Mac users; the entire point of the OS is supposed to be that it goes; they don't have to think, they're artists, rebels, different, you know, the whole schtick. This is, after all, the same computer company that pulled several years of profitablity simply by colouring their cases....
  • Ever take a screenshot in a DVD player? you get a window with a green screen.
    That means you're using a hardware decoder with a passthrough, most likely. Most, if not all, Windows based software decoders allow for screenshots. With hardware based, you'd need a special program to get the shot from the MPEG 2 card, instead of the video card.
  • did offer hardware MPEG-2 decoding through its ATI Rage 128 VR graphics.
    Hardware assist, not hardware decoding. Big difference.
  • What, like the Audis that used to have the sudden unwanted acceleration problem?
  • If and when a DVD player turns up I hope it's better than the piece of junk given out with MacOS 9.

    The old player refuses to run if you have MacBugs installed. Talk about paranoid!

  • Physical distros serve two purposes -- (1) to serve as a token of ownership; and (2) to serve as a vehicle to reduce the amount of time/bandwidth necessary to install the software.

    That may be true for Linux, but a commercial OS (like OS X) has to have as few bugs as possible. Most users never run any updates at all. Major bugs and even missing features will stay in the OS for a long time, even if there is an update available. Microsoft and Apple both try hard to get more people to keep their software updated (using tools such as the Software Update control panel), but it is very hard to teach most people that there is more to the OS than the CD.

    That said, this release of OS X is not really intended for the average consumer (whatever that means); it's meant for people who pretty much know what they're doing with a computer. Those types will be much more likely to download OS updates than most, but it's still a falsity to say that the OS X CD's job is to "serve as a vehicle to reduce the amount of time/bandwidth necessary to install the software."

  • In my case at least, whats attracting me to the new Macs is the recently-unveiled iMovie software and SmartDrive hardware that means you can master your own DVDs that will play in normal machines. This is really cool, groundbreaking stuff, but if it doesn't work yet in OSX then I won't be buying one till its fixed.

    Mind you, they must have known about this for a while; newly bought Macs with this stuff won't be shipping with OSX installed intil June/July, so thats about when I'd expect to see a complete feature set available.
  • I think the Aqua PLAF calls into the Appearance Manager (native code), so it probably isn't portable.
  • Last time I checked, it was "pax". And don't get me started on this, please, as pax have, well, some rough corners... (like replacing carefully symbolic links by real hierarchies, or changing permission on directories unrelated to the install at hand)

    Cheers,

    --fred
  • This is not an attack on Apple, Microsoft or anyone else specifically, but a complaint about software in general. Why is it that we would never buy a car with 63000 known defects, but Windows 2000 is acceptable because 'all software has bugs'. All software has bugs because the majority of it was written without enough forethought, too many dithering managers, users and coders and because writing a quick hack is easier than doing the job properly. No wonder IT is held in so much contempt by the common man. The product is late, incomplete and full of annoying bugs and bad ideas, and then the provider says 'well we'll fix it in the next service pack'. Not good enough.
  • It wasn't an attack on Microsoft per se, as Linux distros are perfect either. I'm just sick of having to use software that doesn't work properly. There are very few new cars that break down every day, but too many new programs do. I'm not just talking about operating systems, I'm talking about the whole ethos of releasing shit and calling it a diamond. Here's 2 examples then from each side, and remember, I'm being vendor-neutral here:

    1)Windows 2000 is 4 years late and doesn't work properly.
    2) A company I used to work for successfully migrated their legacy mainframe systems to SAP in 9 months with no major issues. The users, management and SAP are all amazed and delighted.

    So if example 2 can produce the goods with nothing but minor errors, why can't the world's largest software house in the world with all the efficiencies of economies of scale that economists are always talking about produce something that works. This goes for every late project, bad application and buggy driver. Excuses aren't good enough. Example 2 planned and defined their requirements properly and produced well-written code. The testers then went through it with a fine toothcomb and shifted the rest of the showstopper bugs.
    Most projects don't do this, but give me one good reason why not. PHB stupidity is an excuse for a bad system, not for clumsy code. A bad system with good, well-documented code can be improved upon far more easily than a good system with bad, obscure code.
    Just as a disclaimer, I try to practice what I rant but I'm by no means anything better than average. I just try to think of the poor sap who'll have to maintain my code in a year's time, rather than just doing what's easiest at the time.
  • But then had Microsoft done it right in the first place then their job would be a great deal easier and their customers would benefit. What you're saying there is exactly why I'm sick of working in IT. The whole policy of 'produce a worthless piece of crap according political or marketing considerations. Then spend the next decade patching and hacking the code' makes me want to scream. There's a fundamental problem at every level of our industry which can be mitigated somewhat by coders writing good, well-commented code. The PHB effect is nothing compared to the bad programmer effect. Don't take this as an attack on Microsoft in particular because, as much as I dislike them, they are far from the only offender.
  • Not entirely true with DVD Studio Pro (Apple's other DVD Mastering Product) which will let you change around the VBR (Variable Bit Rate) encoding and quality levels, allowing you to tweak your DVD to a fare-thee-well. So, if you don't mind VHS quality...how about 12 hours of video?

    Want to see the entire first season of Babylon 5 on a DVD? Hack your Tivo to interface with a Mac w/ DVD Studio Pro.

  • As far as I'm concerned the problem here is that the software is non-Free

    I really don't mean to feed the trolls, so I will accept your proposition at face value, and suggest that you check out Apple's OpenSource project [apple.com], and the release of the source and documentation of the underpinnings of the OS.

    Yes, I understand the difference between Darwin, which is free and opensource, and Quartz and the other userland stuff, which is neither. However, I am assuming for the sake of argument that you sincerely didn't realize that an important part of OS X was, in fact, opensource and beer-free.
  • I know your post is a bit ranty but I for one didn't know that MACs supported 3 button mice. Once I read, "USB" I thought, "but of course", until that point I thought they were all 1 button.

    I'm glad Nuke doesn't exist or else you wouldn't have had chance to put this bit of FUD to rest, for me at least.

  • In general the problem is that programs may scan the directory in order to determine if they are going to write over a file and fail to detect if they are. This is a serious problem even if the program is aware that the file system is case insensitive, because the program's idea of what letters match may be different than the file systems (especially true for Unicode filenames!)
    Programs which do that are poorly written. A program should always ask the filesystem if a file exists. The program is never qualified to make that judgement. Ok, that's an exaggeration, specific filesystems may guarantee cetain behaviour.
  • by TheOutlawTorn ( 192318 ) on Friday March 23, 2001 @01:25AM (#345397)
    If using Linux (and participating in the community) for 5+ years now has taught me anything about OS development, it's that there is always more to do, whether it's adding support for new technologies, improving SMP, debugging, etc. Regardless of the bugs currently present in OSX, I still consider it to be a huge step forward for Apple, just as I considered the 2.4 kernel (bugs and all) to be a huge step forward for the Linux community.

    Besides, I'd rather see Apple release OSX 1.01 two weeks from now, than wait 6 months for the first "service pack", eh?
  • All your base are belong to Apple!

    You're not seeing something clearly. Hardware architecture (x86 vs PPC) has no bearing to the price of Apple hardware.

    If, miraculously, Apple had adopted Intel instead of Motorola, their boxen would still be the same price; not because the parts are cheaper or more stock, but because Apple dedicates engineering resources to motherboard design, case design, style, look, and feel. Why do you think that if Apple adopted Intel that OS X would run under stock Intel hardware? I'd think you would *still* need an Apple motherboard, and Apple chipset, an Apple rom and bios, etc.

    Geek dating! [bunnyhop.com]
  • Except that to the 'OoB' consumer, Apple PPC is the same as Apple x86. To the 'hackers', one would not be able to buy an Apple x86 board any more than they could buy an Apple PPC board, and an Epox or MSI or Intel motherboard would be as useful to a hacker then as those boards are to the hacker today.

    People still wouldn't be able to run OS X on a Tyan motherboard, any more than they can or can't today.

    I can't even begin to talk about 'wasted' R&D expenditures, though.

    Geek dating! [bunnyhop.com]
  • Actually, Yeah. In fact, Classic MacOS did as well [ucla.edu]. With OS X being SMP-enabled at the kernel, the clusters should be able to make full use of the hardware now.
  • The file system is not case-sensitive, but case preserving.
    It rembers the case - so if a file is called Readme.txt it will remain capitalised this way. But if you type rm readme.TXT the file will be deleted.
  • This release of Mac OS X does not support DHCP Relay. FreeBSD does, more recent distros of Linux do, Mac OS 9 does (!), as do all versions of Windows.
  • ADC member so they shipped it to me today - Don't think I am allowed to say much about it but it's much more stable then the PB and also faster. Have Netbeans running , OmniWeb (eats IE alive) ..sharity .. it's 11pm and all is well =). You could definatly do worse .. and let;s not forget what sort of change in Mac direction this actually is .. Imagine the next windows being Solaris ..
    --

Behind every great computer sits a skinny little geek.

Working...