XmlDocument read from Network Stream

[Yechezkal Gutfreund]

BTW: Measure, Measure, Measure takes Time and $$. Much of this could have
been solved even without Micrososft opening up the source. If MS would
simplly have an option for increased documentation (an very high level
description of the algorithm each DotNet method uses) and some of the chief
data structures, this would create a much more transparent system, and
really help those of us who are very comfortable with code and algorithms
(And who else uses an API anyway?)

 

[Jon Skeet [C# MVP]]

BTW: Measure, Measure, Measure takes Time and $$.

Yes, but any company which isn't reckoning on performance measurements
as part of its budget for developing software on mobile devices is
kidding themselves to start with.

Much of this could have
been solved even without Micrososft opening up the source. If MS would
simplly have an option for increased documentation (an very high level
description of the algorithm each DotNet method uses) and some of the chief
data structures, this would create a much more transparent system, and
really help those of us who are very comfortable with code and algorithms
(And who else uses an API anyway?)

On the other hand, it would mean MS tying themselves to those
algorithms. You should always write to the interface, not the
implementation - what if a bug is found which can be fixed, but only by
breaking the time guarantees made in such a set of documentation?

I'm quite happy with things the way they are - although the
documentation could certainly be improved in other ways.