In his latest post, Shawn talks about how to priorize and optimize things when dealing with different kind of programming, plus he opens the x-files of his life and reveals some dirty secrets of his past.
From Shawn's post: "... This is one of the reasons I like having a content pipeline that separates build time data processing from my runtime game code. The more computations I can move from my game into a custom content processor, the less product code I have to write. Processors are internal utilities that only ever have to run on my computer, so I can get away with all kinds of shortcuts that would never be acceptable if I was doing this processing as part of my shipping game code. ...".
I agree. What is more, for those of you who may think that the content processor could turn out to obstruct the creation of a game editor (say, for the PC platform) by using the XNA Framework, I'm afraid that you are forgeting something: "MS Build" console application and the "XNA Content Builder Application" comes to the rescue when you need to import content "on-the-fly" (unless of course you decide to make your own "dynamic" loader).Cheers!