. I do actually have komodo edit on the mac too,
but, I like to run my editor next to my browser,
and, I'm quite convinced that a browser in a virtual machine
is still safer than any browser directly on the mac;
simply because the malware has 2 hoops to jump through
before it can get to the host kernel,
unless it knows of a vmware hole .
. when I first ran VirtualBox I was really excited about
openware that would protect me from browser malware .
. but VirtualBox was not ready;
and, it made me have your exact sentiments:
"( Running an entire Linux [OS] on top of Mac OS X
is a resource hog ...) -- it crawled;
but do I actually have to buy vmware?!
. VMWare, on the other hand,
not only had a lightning fast mouse action,
it also had a working usb connection;
and, it was very stable on Leapard
(can't recall VirtualBox's record on that count).
. I have been following both the VMWare and Apple threads
on this total hard freeze,
and some other people here have claimed
the same thing I did:
a new version of kernel or kext caused the
hidden flaws in the hardware to become obvious .
. some claimed to fix the flaw by
rolling back to Leapard,
others by going back to earlier versions vmware,
and some by replacing the mother board or graphics card .
. multi-threading is notoriously hard,
and today's GCD is massively multi-threaded
by way of the grossly complicated GPU cores .
. my point has been,
a pre-emptive OS is a pretty simple concept;
so, why can't we have one?
. if an OS is really rock solid,
it should never be the case that an app can
cause a hard freeze; an app is just a task,
and the task supervisor should always be
making a routine visit to the user's gui task;
so, vmware or any other app
has nothing to do with it:
in a solid OS, an app's kext should not even be
capable of tying up the thread supervisor .
. what they need to do is replace mach with the L4,
and not bloat the task manager .
(again, I'm no expert, I'm looking for
verification of my hunches 🙂).