Can someone finally put the setting to disallow third-party cookies back?

Don't you mean "loosing"?

I love my Microsoft Natural 4000 keyboard except for the truly worthless zoom toggle right in the middle. If they were to replace that with a pointing stick (or even trackball) I would be in heaven. (The back/forward buttons could be left/right click instead.)

In general I agree, but that's what RTC wake-on-clock is for (combined with idle shutdown or S3 sleep).

Microsoft tools (+ReSharper) are now as nice as tools for Java, ASP.NET is as good as any Java web framework, and WPF totally kills SWING on the client.

I don't do much GUI programming in either, so I'll concede the third point, but I've used both Eclipse and Visual Studio for years, and trialed ReSharper, and Eclipse is still far better. ASP.NET is nice, and easier to get started with, but still not as good as putting together some of the best Java tools, mainly Spring Web. WAR deployments are better than the (non-existent) .NET model, and the wealth of free libraries for Java (Jakarta, Codehaus, etc) still beats what's available for .NET.

With VPDAU, that problem is solved for recent NVidia cards. Myth .22 (should be out soon) supports this.

Too bad Casino's appears so often!

You could also use UnxUtils or GNU win32, which can just be unzipped and put in the path. Cygwin is overkill, I feel.

I think everyone is missing my point. Clearly stupid people can write whatever they want. Obviously unit tests help in this regard, but still don't prevent it. My original point is that, contrary to what Bruce said, duck typing does not help maintainability. You and several others keep harping on this point of moronic implementation, which has nothing to do with my original point. In no way am I saying that just because Java has interfaces can you assume that implementation will be correct or you can change things and it will still work. That's just so idiotic I didn't even think anyone would take my comments that way. Strong, static typing makes it easier to figure out how some (not all) changes will affect other code in a way that Ruby's dynamic typing does not allow. That includes unit test code. This helps a person maintain and change code more easily, especially if the person has not worked on the code before.