@Toyface19 The fonts do make an impact when launching certain applications, namely TenFourFox. More specifically, TFF parses through system fonts while initializing, which can compound startup times. So, the less fonts there are, the quicker it loads.
That's what I'm trying to figure out now. Generally, I tried to keep to a "don't remove if it's an unknown" development model because there was a fair amount of components in the system which I couldn't find any documentation for, so they were left in, but there were a couple of exceptions to this.
Unless my memory has already failed me through the course of only a year, I don't know what the VSP framework relates to, but it sounds suspiciously similar to "VMX", otherwise commonly known as AltiVec, so that's definitely subject to removal.
Otherwise, the only other things I could imagine might have anything to remotely do with hardware acceleration / technology leveraging would probably be XgridInterface and XgridFoundation, however I recall them to relate to resource clustering and are only actually useful for data center usages, for instance with hardware like the XServe.
If it strikes your interest, here's one of the resources I used during development:
Introduces OS X and its technologies.
developer.apple.com
So far, I'm getting the feeling that it might be best to go with a split product availability, with one being meant to strip the system to the minimum for old and unsupported machines to run better, and another to simply optimize it for newer ones without removing any functionality. That way, there is no compromise for any group.
