Windows.. it's like coming home! 3381

That laptop was simply broken. Mine does not get hot; the warmth is barely perceptible.

I think Apple does have a problem, perhaps due to the thinness of their laptops making proper cooling hard, or perhaps due to an aversion to fan noise.

snip

Well, I trust that when Intel-Mac games come out, they will have less of a performance problem- but I expect there will still be few available, and those ports of old Windows games.

I do not see what you mean by this.

I thought that was so when OS X became dominant; but now have another. And don't kid yourself, this transition has a while to play out yet.

Getting the hardware out there is important, and Apple has done that very fast, but that's just the first step.

It shows a lack of commitment to their own platform.

I could do that, or I could just buy a Windows laptop, and not have to use a beta bootloader.

That is a large topic. The short version of the answer is the C++ follows in the footsteps of Simula-67; Objective-C in the footsteps of Smalltalk.

This has extensive and surprising remifications; much of what a C++ takes for granted is wrong in Objective-C. And vice-versa.

That is what makes going from one to the other mind-expanding.

They are available; but you also get C# or VB.NET if you want them.

And there are other choices from other vendors, too.

Yes. It's flawed. But it still has better memory management than Objective-C-Cocoa has today.

I do not say that VB 6 had *good* memory management; it hadn't. The good stuff doesn't use reference counting, which is slow, bloated, thread-hostile, and leaky.

But at least VB 6 did the refcount busywork automatically.

System services will very likely be done in C, full stop; anything else wants too much runtime support.

Enterprise apps are often done in higher level languages like Objective-C. But Java, VB, and C# are all more common choices for this role.

C++ can do almost anything, as long as you are in userspace, but it is difficult.

Indeed not. But Objective-C produces slow code unless you go out of your way to avoid it. If you don't do something, you'll get lots of objects separately allocated. The allocator is slow, and you also have more messaging.

This can be overcome, but you have to put in the sweat to do it.

snip

Now now. You can get a fairly nice IDE for free download from MS these days. And the error handling is top-notch.

snip- Mac UI Consistancy

What about it?

While Windows programmers *can* implement a UI that looks like OS 9, they don't. There's no reason why they would do that.

The reason you see this on Macs is that those programs were at one time Mac OS 9 programs, and were ported to Mac OS X.

Sure, they could have redesiged the UI for Aqua, but that's a lot to ask and you don't usually see it.

snip

I did. Compare 'get info' dialogs in iTunes with the inspectors in Keynote, for one example.

snip

That's is, I think, just a program launcher. I prefer the start menu for this. XP doesn't really offer any kind of application switcher; that's why they call it "Windows". :D

Expose is very nifty, but while it is infinitely more cool than the taskbar, I find it less useful. I can see how another user, with different apps, would have the exact opposite experience however.

When the dock is very small, the icons in it are also very small and hard to hit. The taskbar does not behave like that.

Think of it this way: The whole dock moves as items are added and removed from it.

You have to look to see where your icons are before clicking them (in the Dock) because they move. You can't just remember the position.

Yes. It is the Apple menu that is not.

snip

And I would still not use it much. :D