No, this is not yet another rant about missing the Mustang in Leopard. The unofficial Apple weblog writes about the iComet, which is a picture of a comet in the shape of the Apple logo.
If we go, then at least we go out with style: Armageddon, designed by Apple in California.
I’ve eschewed downloading the Java 6 developer preview from Apple’s Developer Center since it was over a year old. And with Leopard around the corner, where is the much needed love for Java coming from Apple? Remember that OS X would be the number one Java development platform?
300 new features, but no mention of Java. I’d really hate to take James Gosling’s route and resort to using other operating systems to be able to continue to work for my company (we’re already deploying to Java 6).
The only quote I could find about Java on the Apple Leopard developer site was:
“You can even use 64-bit Java on capable Intel processors.”
Where’s the love?!?
It seems that the update delivered yesterday by Apple has fixed the memory and hick-up problems I mentioned earlier. Today I have been able to just work with the manuscript without pulling my hair out in agony.
Though the jury is still out, I don’t see any strange behavior anymore in the activity monitor regarding pages. On with the book!
I just wrote about my troubles with Pages and trying to write for Wicket in Action. Apple support is really quick: my blog entry was not up for longer than 8 hours, and they apparently already have fixed it!
About Pages 3.0.1
This update primarily addresses issues with change tracking and performance.
I already figured it had to do with change tracking, as before we sent the documents to our editor, we had nothing to complain about performance. However, when we received our feedback, it came in a Word document that had change tracking on.
Installing the upgrade as we speak! Thanks to John Gruber for his update on Daring Fireball.
The new Pages in iWork’08 seems to have some uncomfortable bugs: it claims quite a lot of memory, hogs the CPU, and often freezes my whole OS X GUI. To put it mildly: I have to restart Pages several times a day to make it usable.
It looks like the memory management of Pages 3 is b0rked. While I’m typing this, Pages is trying to shut down (now for over a minute!). It is using one core of my CoreDuo, and about 70-80% of the time it is spending time in the kernel, increasing the real memory usage (now 471 MB).
The shutdown has now finished, in over 5 minutes!!! AAAARGH.