I love my Mac!

[Nothinman]

For my searching last year or so, i couldnt find any type of caching for osx, besides keeping programs in memory until you 'quit'. Pretty much what nothinman said.

I mean copout because obviously they knew about the technology, and obviously they will move that way eventually (maybe). So by releasing another OS (snow) without this feature or a reworked/better, was a copout.

Well, it's not like OS X evicts the binary as soon as you quit so there's still some caching. There's just no "intelligent" daemon watching your habits and preloading things it thinks you might want.

 

[sourceninja]

That sucks but is a pretty special case. Now that you mention it, I think VMware Workstation had the same limitation last time I used it, but that was years ago and on Windows so who knows.

Why not do the PHP stuff directly on OS X? I would imagine it could be setup close enough to copy over without any changes needed.

I used to do that, however it added cruft. I had to install my own version of php because the supplied version of PHP 5.3 no longer supports old-password hashing with mysql (and our mysql admin is slow on the uptake). On top of that, I had to replicate my setup on my home computer as well (I don't always feel like packing up my work computer and taking it home). That means pear, oracle modules (pdo, oci) and a bunch of other junk (our standard libraries, etc).

So our main web server is virtual, I just cloned it, converted it, and changed the host name. Placed it on my home machine and work machine, then deleted all the production files not related to my job. I can develop there, then move to our 'test' server for approval. Now everything works great and it's isolated from my system. Plus that means I can do snapshots and rollbacks if I want to test how the next version of php might effect our scripts.

Honestly, I'd love to just develop directly on the test server, but not many ide's are designed to debug and unit test on a remote device.