Breaking ObjectSpaces out of .NET Framework

I noticed a string of posts today about breaking out ObjectSpaces from Whidbey (I happened to see Paul Wilson's first). That's an interesting development.

I guess I can understand why. It really does tie a major feature to a specific database, and doing so would probably fuel an already hot fire about Microsoft and bundling. As long as it's still available, I guess I can't say I'm really bothered one way or another.

O/R Mapping is fascinating to me. Personally though, I happen to think you may get better performing code if you have some kind of code generation tool writes classes that map to data. I don't have much experience with code generation, but it sounds like a neat idea. That said, O/R mappers offer you a great deal more flexibility in terms of keeping your database schema more fluid when you're prototyping or taking the guerrilla approach to writing code (which I'm guilty of doing).