Bugs Fixed and Created
While Tiger is mostly a feature release of OS X, there are a handful of bugs that are fixed, but unfortunately, also created with the updated OS.In my review of the mobile experience of Panther, I complained about how I could never get the Keychain manager to remember my user names and passwords when connecting to any of my Windows shares. It turns out that as long as I sent the password as plain text in the connection request, I'd never get asked for a user name and password again - but that's obviously not the most desirable solution.
In Tiger, the password problem is thankfully fixed - I can connect to any of my Windows shares without having to keep on reminding the Keychain manager to remember my user name and password.
Further indication of Tiger's hurried release is the fact that Quartz 2D Extreme, the complete handling of UI rendering and compositing by the GPU, is not enabled in the release version of OS X Tiger. As such, users of Quartz 2D Extreme supported GPUs gain no performance benefits in Tiger as the CPU is still left to handle all UI rendering and the GPU handles all compositing after the CPU renders the interfaces to textures in AGP memory. The only benefit modern day GPUs offer in Tiger (other than their improved performance in 3D applications) is that there are certain visual effects that are only enabled if you have a GPU that supports Tiger's Core Image. For example, when dropping a widget onto the Dashboard, you get a very nice ripply-wave effect on GPUs that support Core Image; and on those that don't, there's no effect. But from a performance standpoint, there's no benefit to either ATI's Radeon X800 XT Mac Edition or NVIDIA's GeForce 6800 Ultra DDL.
Although it's most definitely an issue related to meeting Tiger's 1H'05 release schedule, I've always thought that Quartz 2D Extreme was best paired with PCI Express. Given that Quartz 2D Extreme requires that all UI elements are rendered by the GPU, including every last character that appears on the screen, you can expect the size of your local frame buffer to play quite a major role in performance. Obviously, not everything will be stored locally to the GPU, and thus, there will be times when the GPU is rendering or compositing data that is located within system memory, which at this stage means that the GPU has to go over a very slow AGP 8X bus (2.1GB/s) to get to the data that it needs. With PCI Express, the GPU to system memory bandwidth is significantly increased, which has enabled technologies such as NVIDIA's Turbo Cache to gain a foothold, where things like AGP GART could not. Although it's unthinkable that Apple would revise Quartz 2D Extreme to be a PCI Express-only technology, the fact of the matter is that it should be much better paired with a PCI Express based G5.
Tiger also seems rushed in the sense that it's not a drastic shift to 64-bit computing; Tiger adds the ability for individual processes to have access to more than 4GB of memory. As can be expected, any process using the 64-bit memory space can only talk to 64-bit libraries, which at present, doesn't include any UI libraries. The end result is that you can have a 64-bit process, but it has to talk to a 32-bit UI process. There are even more limitations beyond this, but the basic impression that I get from Tiger is that Apple is taking a much more transitional approach to the move to a full 64-bit OS than Microsoft. In fact, if it weren't for AMD, I wouldn't be too surprised if Microsoft's move to 64-bit would be much more similar to Apple's. The reality of the situation is that for the majority of users, 64-bit memory addressability isn't going to be a necessity for another few years still. Instead of focusing a lot of attention on 64-bit today, Apple appears to be making a transition towards the goal of making the Mac OS a full 64-bit OS, but with Tiger, we are far from there yet. Next week, you will be able to read my impressions of Windows XP x64 Edition, and from my experience with that, desktop users aren't missing anything from Tiger, being somewhat limited in its "64-bitness".
So, what are these bugs to which I keep alluding in Tiger? For starters, applications do crash in Tiger (which happened in Panther as well), but now, Tiger allows you to "Reopen" the application after telling you that it's crashed - how nice of it, right? Well, the problem is that occasionally, after re-opening an application that just crashed, Tiger will pop up a window and ask you if you want to keep the new settings that have been applied for the application that you're using. What this appears to do is tell the application to revert to its default settings, but the question clearly doesn't word it like that. The bug thickens, however; sometimes clicking "yes" or "no" is not sufficient enough, and more and more copies of the dialog box will appear. This is a problem that I started noticing in some of the later ADC betas, but I figured it would just get fixed on its own. While it doesn't happen nearly as much as it used to, it definitely does happen even in the final build of Tiger. The only solution to the problem is to hit Cmd + Q to quit out of the application after you've quickly hit "yes" or "no" a bunch of times to clear the stack of dialog boxes. It's annoying, but luckily, I haven't had it happen to me too often.
Then, there's a new bug with Dock magnification that wasn't present in Panther. I'll talk about this one in greater detail in the section on what's new in Finder. And there are some minor bugs related to Dashboard and some of its individual widgets that I'll also go over later in the article.
Tiger is a lot more polished than it was during any stage of the beta program, but I would hardly call it a finished product ready for retail release. One aspect of the entire Mac OS X experience has been that everything just seems to work the way it should, but with a buggy OS (regardless of how minor many of the bugs are), that experience is challenged. Given the amount of time that Apple invested in touting not only Tiger's 1H'05 release date, but taunting Microsoft's delays with Longhorn, it's not surprising that aspects of Tiger appear rushed. When I first heard rumors that OS X 10.4.1 was being worked on immediately after releasing Tiger to manufacturing, I feared that this may happen. The good news is that hopefully, 10.4.1 will address these issues and hopefully with the team hard at work at it, it will be out sooner rather than later. But waiting for a patch to an OS before calling it final is usually something that we do in the Windows world, not something that Apple needs to be copying.
Facebook
Twitter
RSS
55 Comments
View All Comments
pecosbill - Monday, May 16, 2005 - link
As for your comments on the bugs in the initial release, I couldnt' agree with you more. Apple seems to have taken a page from Microsoft whereby only critical bugs are fixed for a .0 release. The other thing to consider is Apple relelased new hardware around the same time. My new 2.3DP G5 came with Tiger pre-installed. Apple used to have a strict tie between hardware and OS so any delay in Tiger would delay the hardware. I'm rather sure that has decreased now, but they may rather not support the older version of the OS on newer hardware as that raises costs due to compatibility testing requirements.pecosbill - Monday, May 16, 2005 - link
msva124 - Thursday, May 5, 2005 - link
>NeXT and NeXT step succeeded in the markets where it succeeded.In other news, among stocks that went up yesterday, stocks were up.
JAS - Thursday, May 5, 2005 - link
OS 10.4 has already exceeded my expectations.I was a little hesitant to install the new OS on my two Macs until the first update (10.4.1) is released. But today, I installed Tiger on a secondary drive in my dual processor G4 desktop Mac. I was pleased with the boost in overall system performance and did not encounter any software incompatibilities. So, I installed 10.4 on my G4 iBook, too. No problems there.
The first improvements I noticed are with Safari and Finder operations. Dashboard, Spotlight and the new iChat AV are very cool. I just played a high-definition QuickTime movie trailer for the first time. The image quality is spectacular on my Cinema Display.
I've upgraded QuickTime 7 to "Pro." I like how you can now record audio directly within QuickTime.
Although there's room for improvement in certain areas, I think Apple has done a fabulous job with Tiger. I'm looking forward to seeing what the incremental 10.4 updates will bring over time.
CindyRodriguez - Wednesday, May 4, 2005 - link
Ah, I almost forgot:"The "foundation" for OS X was kind of forced into play, you know...;) And, it was years late and initially very lacking in promised features (many of which it still lacks.) "
You really have no idea what you are talking about do you?
How was it forced into play? Because Apple chose it over BeOS? Because Apple recompiled OpenStep for PowerPC? Because Apple came up with Carbon libraries to seamlessly run classic Mac OS Software in OS X natively with almost zero changes to code? Man did they force that sucker in.
What I really wanted to ask you was, what features are still missing? What was promised at the purchase of NeXT but hasn't been delived yet?
Finally, how was it years late? You are specifically talking about the NeXT/OpenStep core as far as I can tell. Are you talking about the first OS X Server release which was way more NeXT than the current OS X distribution (which has a FreeBSD core)? Or are you just talking out your butt again and confusing Copeland with NeXT and FreeBSD?
Considering that Apple bought an OS that didn't even have SMP support because a MAJOR library in the development environment wasn't threadsafe and they almost completely reworked it into the basis of today's OS X in a couple years.. I think that's pretty damn timely, don't you?
CindyRodriguez - Wednesday, May 4, 2005 - link
WaltC:Do you believe all the crap you write?
How many times to people have to point out to you that MICROSOFT was the one who started all the Tiger/Longhorn comparisons? Blame freaking Jim Alchin for comparing his vaporware to Apple's soon to ship OS. (BTW, last time I heard, WinFS was scrapped)
Also, NeXT didn't "fail". it was bought by Apple. It certainly wasn't the company it was intended to be when Apple bought it but it wasn't out of business.
"Oh yes--I suppose that's why the board fired him in '85...;) "
That was an internal power struggle that Jobs lost. I'm not even sure what your point was? Perhaps you wanted to point out how well Apple did after Jobs left?
"Both NeXt and NeXTstep failed commercially as I recall. The "foundation" for OS X was kind of forced into play, you know...;) And, it was years late and initially very lacking in promised features (many of which it still lacks.) "
Um, no. NeXT and NeXT step succeeded in the markets where it succeeded. I bet that's hard for you to grasp but let me break it down. NeXT and OpenStep specifically provided a great development environment and it took of in industries that had a lot of internal custom code. From what I had heard, NeXT, NeXTstep and OpenStep were still very pervasive in the Chicago Stock Exchange well well after the heyday of NeXT pretty much up until Apple's buyout. (OS2 actually had a similar but smaller phenomenon)
"Ah, yes, the RDF again...;) The truth of course is that *nobody knows* what Longhorn will be since Longhorn is a long way out. I see nothing wrong with a Tiger-x64 comparison because MS is *shipping* x64. Pretty simple, really. "
Hmn, good point. I KID. It really was a dumb point.
Microsoft just held a week long conference called WinHEC that focused on guess what? Come on walt, Guess. Do It.
YES!! The focused heavily on Longhorn. In fact, I've hearn no real news out of it other than Longhorn. Gee, I wonder how people (like Jim Alchin) can even compare Longhorn to Tiger considering how tight lipped Microsoft is being about Longhorn features. I mean, aside from the regular info, the early build to developers, and the week long Longhorn love fest a couple weeks ago, we know absolutely nothing about it.
On the other hand, there is the Windows64 comparison argument. Of course, that's pretty dumb too since I don't know of a single feature difference between XP64 and XP-SP2 aside from 64bit libraries. There's also that problem where MS won't even release XP64 for retail sales because driver support is still so crappy.
Other than those few point and all the other ones covered by a dozen other people, I found your comments very enlightening.
Cindy.
rsfinn - Wednesday, May 4, 2005 - link
From page 2: "With Macs, since there's no exposed boot menu, you have to hold down the "c" key while starting your machine to tell it to boot from whatever is in the CD/DVD drive."This works, but most users will never do this -- they'll insert the DVD and double-click the icon labeled "Install Mac OS X". This will set the computer to boot off the DVD and put up a dialog with a "Restart" button. After the installation is finished, the computer will be reset to boot off the partition on which Tiger was installed. No muss, no fuss.
rsfinn - Wednesday, May 4, 2005 - link
From page 3: "I definitely didn't see a single build that was released to developers that was 100% bug free ... with no public beta, and if the bugs aren't getting fixed in the developer release, then who's there to tell Apple when stuff isn't working right in Tiger?"Well, you, Anand, for one. "Beta" is supposed to mean "early access so developers can test the OS against their applications and report problems". Did you report any of the problems you saw in those prerelease builds? Or did you join the developer program just to get early access to the next cool thing?
I'm picking on Anand here to point out this wider misconception about beta software -- even public betas; as a software developer myself it's annoying to me that most people think "public beta" means "I get to play with it for free". If people don't report problems, how can they get fixed?
WaltC - Tuesday, May 3, 2005 - link
#39 "Most of what you said is ridiculous."That's only because you don't really understand what I said at all...;)
#39 "First of all, Apple's market share is growing. Of course other platforms sales aren't Apples sales. But most other sales aren't either Apple/Sun, etc."
Apple's current market share--growing or not--is still ~80% below what it was a decade ago, in terms of percentage. One significant sign of this is the fact there are very few if any Mac-only development houses left in the world today. As I pointed out, the market as a whole is still growing and the fact is that *everybody's* unit numbers are rising because of it. Increased unit sales only counts for increases in market share when they exceed the growth of the market as a whole.
#39" This is mostly an Apple/Wintel market. Sun is only servers and Apple doesn't compete much in their space yet. Apple's server sales are increasing, but are only now ramping up. Except in the scientific Unix space, Apples server sales would be against Windows servers. They don't yet have the breath to compete in the higher areas yet."
Yes, in the Apple/Wintel market it's Wintel ~97%, Apple ~3%.
#39 "Otherwise, it's Apple vs. MS."
Impossible, since the vast bulk of Apple's earnings come from its hardware sales, and MS doesn't sell personal computers of any type (unless you want to count xBox, which would be silly, imo.)
#39 Sure, other pc companies, or rather company (Dell) are growing, but that takes sales away from each other. Apple's increase in marketshare takes away from the Windows market itself. If Dell takes sale from Gateway, it's still a sale for MS. That's the point."
First you say it's an Apple/Wintel market, then you say that every Apple sale is a bite out of Wintel, and then you say that people buying Wintel instead of Apple doesn't even affect Apple sales--which seems to me very much an RDF sentiment if I've ever heard one. If you think a great number of people do not consider and then reject Apple in favor of going Wintel, you are definitely an RDF sufferer...;)
#39 "I suppose that Apple is taking away a few Linux sale as well, but it's almost all MS's."
Have you ever stopped to consider how many Linux sales take bites out of the Apple? For you folks it's always a one-way street where Apple gains but never loses...;)
#39 "All AMD did was to finally come out with better processors that they could actually make, rather than just announce, and then NOT make."
'All AMD did...'--as if it was trivial...;) All AMD did was face a juggernaut with little more than a slingshot for a long time--and manage to win, over and over again. Heh...;) You're funny. The only company you don't trivialize is, of course, Apple...;)
#39 "Apple does directly compete with MS on the OS front. Apple has always had different hardware. When Apple went to the 68000 rather than the 8088 way back when, there were few arguments that the 68000 was not a better chip. Apple simply went on through from there."
You do not understand that an Apple OS *requires* and Apple-branded box *exclusively*. A MS OS will run on boxes manufactured by hundreds of companies around the world--and none of those boxes are made and sold by MS. It's very simple. That's precisely why its a ~97% to 3% market share split, if you haven't figured it out.
39 "If Apple were to change to an x86, then every program would have to be redone. That would be almost impossible for the many Mac developers out there . It's just like the Itanium. Little software development has been done for it. Why should Apple be caught in that trap?"
Itanium is a cpu. OS X is software. FYI, the foundation for OS X, NeXTStep, has *already* been done for x86--years before OS X shipped. "The many Mac developers out there" (heh) could still develop for the Mac since presumably Apple would still sell Macs while releasing an x86 version of its OS *at the same time* which might well attract *many more developers* than Apple presently has.
Last, as noted, the split is *already* ~3% Apple versus 97% x86--so the current situation is not *much different* from the poor Itanium allegory you tried to use, is it?
msva124 - Monday, May 2, 2005 - link
Sorry, it was a dumb mistake. I don't think you are a troll anymore.>If Apple isn't taking away from the Windows market, then which market is it taking away from?
Every sale made by apple doesn't necessarily take away someone else's. There are many users who are more or less satisfied with their current setup of 1 PC, yet decide to go ahead and buy a Mac to complement it. Had Apple not existed, they wouldn't have bought another PC, they would have just stuck with their current setup. So in this case, Apple gains one sale, but PC makers do not lose any. Obviously this is not the case all of the time. The situation is more complex than saying "for every sale made by apple, pc makers lose a sale" or vice versa.