Best Practice: FCP Project locations

I love Apple, but it seems after five generations of FCP, they still don't get how users would like to store FCP data.

Does anyone working out there think FCP's confusing method is brilliant and desirable?

Ideally, what I would like to see is this: Let's have a system drive that stores all my OS(s), applications, and users. Let's keep this drive pristine and not write any other unnessisary stuff to it. It just seems to have less risk of corruption that way, and is easily backed up once a month or so, since it should only chage with software updates and the like.

Then, I have a projects drive that contains all my documents, images, all the client data, project data neatly stored by project name/number -- one folder that has everything in it related to that project, sans the massive media files.

Then, a raid or some other such massive drive that holds all my massive video and audio files -- the renders, all that jazz.

Backing up or archiving the project is a simple matter of burning the project folder to a DVD or DLT or some other long term storage. If I need to go back to it later, just pop the disk back in, retrieve the project folder and all the other stuff, open it up, redigitize the media from tape, and I'm back in business.

This is what I want. But FCP wants to put the project data on my system drive, in my user/doccuments/FCP documents/....and my media split into who knows how many folders all over. Geez, Apple, have you ever actually worked in the biz? If so, surely you must know how insane this arrangement is in what we like to call "the real world"

What are you guys doing that you find works well. I'm reading that some people are saying, just don't fight FCP and use the defaults. I say, screw that!

Thanks!