That's a valid comparison - 2008 vs 2010 (versus the stupid VS6 comparison) - and one I agree with in many respects - especially UI responsiveness.
However, paging-in after idle-time is pretty similar, in my experience for both 2008 and 2010 (2008 fares worse for large solutions - especially if they have web projects in there). Build times are actually faster for VS 2010 (especially if you're on x64 - where it can use multiple cores). Symbol-loading when attaching to a process to debug is way faster for VS 2010 than in 2008. Detaching from a process also seems to have less negative consequences - VS 2008 just crashed in many cases.
However, VS 2010 is way too chatty in debug trace outputs. Also, slightly slower in parsing includes for IntelliSense after project load (not so during build though, funnily enough).
However, paging-in after idle-time is pretty similar, in my experience for both 2008 and 2010 (2008 fares worse for large solutions - especially if they have web projects in there). Build times are actually faster for VS 2010 (especially if you're on x64 - where it can use multiple cores). Symbol-loading when attaching to a process to debug is way faster for VS 2010 than in 2008. Detaching from a process also seems to have less negative consequences - VS 2008 just crashed in many cases.
However, VS 2010 is way too chatty in debug trace outputs. Also, slightly slower in parsing includes for IntelliSense after project load (not so during build though, funnily enough).