Comments

OrigamiCar wrote:

PLEASE - enough with starting every sentence with 'So...'.

I know this seems to be the Microsoft way, but in this video almost every sentence Jennifer says begins so it.
Normally I don't notice these kind of things, but it was really off putting for me!
Sorry to rant - interesting information, but the delivery just grated on me.

I've heard its a northwestern thing.

When did WPF get to 3.5? I thought it was 1.0.

The problem with the reliability monitor is that its kind of useless if you use your machine for development work.  My own programs are crashing, and I'm debugging them, and the more I debug my code the lower my reliability index becomes.  Is there anyway to better configure the reliability monitor for a development machine, such as ignoring certain app crashes, etc?

I wish there was a way to explicitly select paths for the Backup tools to backup.  It's hard to find a balance between the files I want backed up and space usage by just picking generic file types.  I ended up just creating a scheduled task that runs "robocopy /mir" once a week, which works fine.

The problem I see with this compositing technology is it creates a large problem in order to solve a very small problem.  You now need entirely new display drivers throwing out the old ones that have had years to stabalize, application compatibility takes a hit especially screen readers, and you need a complex and potentially unstable system to actually do the compositing.  All of these problems just to fix the issue of rare drawing artifacts and add a bit of eye candy.  It doesn't seem worth it.

Hopefully Microsoft has bigger plans for DWM 2.0 and something more intuitive than the infamous Flip 3D.

I wish this sort of thing existed back when I was trying to make games in QuickBasic.  Everyone has it easy today.

Congrats on the RTM guys!

Totally agree with Jim on the memory usage, 2+ gigs is the way to go.

Memory usage gets really high here to the point where my machine starts thrashing. (1 gig of RAM)

ZippyV wrote:

I know Windows is not a realtime os but why does it have the 'realtime' thread priority? When and why should this priority ever be used?

I've also seen it called "critical" priority. I think it's basically saying "this isn't realtime but its as close as you're going to get."

I'd say working with as a team is definitely important but so is developer privacy. Considering developers are going to be spending most of their time debugging, I'd say some privacy and the ability to shut off distractions is going to be pretty important. The last thing you want when you're debugging, and going deep into the call stack, is someone coming in and disrupting your concentration.