PowerBook Performance for Java Development?
brasten wants to get to the core of this issue: "I'm in the market for a new development notebook. I would like to jump into the Apple world and pick up a PowerBook. However, compiling very large Java applications of course takes some time, and so raw processing speed is a factor. I have been unable to find solid data on how fast a 1.33GHz PowerBook runs against the modern x86-based notebooks. Does anybody have any information that could help me compare?"
If so, consider using a (100 Mb/s) network share,
eg, based on a nearby desktop, as work- & target-
logical drives.
I agree-- the moderation system is broken.
Even more so because if you ever talk about how the moderation system is broken, you are never allowed to moderate again!
The site is for linux weenies and linux weenies only. Anything related to mac is slanted, and any non-critical-of-apple post is moderated down.
After all, Apple doesn't release their code under GPL, therefore they are evil.
Yeah, and you guys panned the ipod too: http://apple.slashdot.org/article.pl?sid=01/10/23
I don't understand why anyone would bother running Linux on a Mac. For $99 you can purchase Mac OS X and get real live tech support for problems that (probably won't) pop up. There's a lot of technical reasons you should run Mac OS instead of Linux.
Linux has its origins on IA32, Intel's 32-bit architecture. Every platform Linux has migrated to since then has been beset with porting problems Linux runs 32% more efficiently on Intel than PowerPC. This is very telling as PowerPC is in general much faster per clock than Intel. Somewhere in the translation from PowerPC to IA32 something got lost.
Mac OS is 100% native for PowerPC. The Mach kernel has been optimized for the G3, G4, and 970 since Apple began writing the operating system back in 1996. Why choose a hacked and kludged OS from another platform when you can have an environment tailor-made for the system you'll be running it on? Mac OS certainly isn't plagued by same driver problems Linux is (in)famous for.
In Linux, the development model is highly irrational: anyone is allowed to submit patches, and one man (Linus Torvalds) sorts through gigabyte after gigabyte of amateurish code, attempting to integrate it into the kernel. Apple's model is much more modern and decisive: the code for the low levels of Mac OS is available for anyone to download and modify, while the more complex parts of the system (QuickTime and OpenGL) are kept closed-source so those that know better the Apple programmers are the only ones allowed to tinker.
The results because of these differing development models are clear. Apple released a major update to the OS once a year, and releases about five minor updates to the OS, as well as several dozen security patches and driver updates, in the interim. Since March of 2001 we've gone from 10.0 to 10.2.5! Linux is still stuck at some sort of bizarre "in-between" 2.5 kernel patch and won't move on to 2.6 until well after Apple has released Mac OS 10.3.
It's not hard to see the difference here is a bunch of kids playing with source code instead of doing their homework vs. highly qualified professionals pushing their skills to the limits. The Mac OS user benefits.
I don't even think I have to touch on this. While Linux offers several GUIs from GNOME, KDE, and Enlightenment, Apple offers only one. But here we have a case of quality vs. quantity. Apple controls the GUI for its operating system while anyone can hack and modify the various Linux GUIs as they please. This has led to a lack of desktop standards and a whole lot of bickering and flame wars over human interface guidelines. Most of the GUIs for Linux are simply poor knock-offs of the Windows 95 interface.
Apple's Aqua and QuickTime graphical interfaces are faster, more elegant, and very consistent. A Mac user can sit down at any Mac and (assuming someone hasn't installed Linux) get right to work. With Linux, it's hit or miss as to whether the user will know what to do when he logs in! Getting work done is the most important aspect of a computer. After all, it is just a tool. Linux fails in this area miserably you're forced to edit and tinker and kludge and hack to make things perfect. A Mac allowes you to just sit down and roll up your sleeves and get some work done. I don't have time to play at my job.
I've used Linux before and the headache of downloading drivers and libraries and making sure the versions all sync up are too mucvh to handle, especiallly considering one has to compile these applications. On a Mac, I mount a disk image and drag the .app file to /Applications, and I'm done. Hell, most software for Mac even installs it there for you.
To put this last point in perspective, let's look at a recent task I perf