In regards to your first argument, Microsoft, at l...

2009-08-05T10:53:52.283-04:00

In regards to your first argument, Microsoft, at least at the time partial classes were introduced, was still stuck in the boneheaded mindset of source control by exclusive checkout of files. So problem #1 is they introduced a language feature to cover a bad design of their source control tools; problem #2 is they introduced it also to cover for a bad code generation design.

It's part of an "out of sight, out of mind" fallacy that Microsoft falls into time and a again: they look at things that really are simple and see that simple things have an austere interface, and then try to make their overly complex things "simple" by hiding the complexity under a rug. But they're mistaking the effect for the cause, trying to emulate the effects of simplicity without actually making anything simpler at all. You can see the effect in the way that every redesign of the look and feel of Office or Media player just hides important menu items without actually making them unneeded, or in the way that every Windows programming advance merely hides the complexity in the software stack underneath it.

Comments on cheaphack: Review and Analysis of C# Part 1: Partial Definiti...

In regards to your first argument, Microsoft, at l...