The thing is, Apple did try to take advantage of the 10.1 Big Honkin' Update issue to make a little bank on it.
In reply to simX, you have some valid points, but a couple of those you mentioned are not available due to technical reasons. RAM Disks are tricky to efficiently implement with the type of VM-always-on paged memory management now used. It can be done, but you either lose out on performance elsewhere in the system, or your lose out on the boost it gives you. Apple programmers have to work that one out fairly carefully. Maybe they could take a clue or two from the 3rd party *nix programmers that took a stab at it and see how they tried to do it, and how successful they were.
The issue of installing selective parts is a valid one, but there are some issues there over inter-connectivity, and predicting future hardware additions. Unless you want to start going through the process of installing drivers for every new piece of hardware you install, the kexts should remain where they are. If you try to remove frameworks, what happens to the apps that use em? If you try to remove the core set of unix apps X installs, what happens the parts of the system that needs them? Before Apple can truly give REAL customizable system install options, they need to find a way around this problem, and I hope that an 'Add New Hardware Wizard' and whatnot IS NOT THE ANSWER. I really hate having to slap the Windows CD in for trival drivers, and would gladly throw a few MB away to not deal with it.
I agree the issues you mentioned HAVE to be resolved, but this is a new environment, and requires new ways of doing the same things we used to take for granted in some cases (spring-loaded folders isn't one of these cases, and should have been implemented by now in my mind, even with the column view issue). Not only do we have to worry about keeping functionality, we have to ask HOW we can keep it in a new environment like this one. Afterall, it was the crappy memory manager in Classic MacOS that allowed the RAM Disk to be so easy, since you could turn VM off. It was the kludge of a system folder that kept it mobile and customizable, and unstable.
Let us hope 10.2 makes a step towards a compromise of some sorts, and addresses the issues that can properly be addressed at this time. I seriously doubt 10.2 will be making us shell out any more than they tried taking from us with 10.1, as it seems with the mark of X, development has geared more towards getting everything to a point where they can move forward with something truly new, rather than putting the finishing touches on the initial version of X.