Design for Distribution

An excellent blog by Tim ewald here : I refuse to let the angle brackets fall where they may! . I love it. It does NOT matter what the current wire protocol/messaging technology is. You need to design close to the wire upwords. You cannot ignore it. DCOM screwed many poor developers because of the "COM on a longer wire" thinking.

The sad thing is that most developers are falling to the same trap with the new IDEs. I think finally, in VS.NET 2005 there is this huge push to make developers understand the things that happens underneath the covers. I think that will be the reason for a massive developer migration from other technologies. (that and sun finally setting).

Sometimes, I think, windows developers have been having it a bit too easy. I am fairly confident anybody who has written C++ socket code will realize the complexity of the task that DCOM is trying to accomplish. But, After hiding such things from developers for a long time, Microsoft has decided to hand the power back to developers. Of course, this means, you can still shoot yourself in the foot. But earlier you would be shooting in the dark but now.. (that was a bit over the top)..