a plethora or responses to mono.
GNOME’s Miguel de Icaza on .NET:
“He feels that the design goals behind .NET and Bonobo were very similar, but he thinks the .NET component model is better. “One problem is that Bonobo has a lot more overhead than .NET. .NET is pretty slim when it comes to the size of the components and things that you can expose.” When asked if he would see himself moving away from Bonobo, de Icaza replied: “Bonobo’s interfaces are okay for what they do, which are compound documents and embedding of controls. There are better ways of defining components and writing components than writing them in CORBA IDL. If I can write a component by implementing an interface in C#, I would much rather create the component in C# than with existing Bonobo.” Nonetheless, he can see both approaches being compatible.”
“The first clue should be that Microsoft is not protecting the source of the .NET runtime, in fact they’re publishing it, under some constraints, but if you want to see how they do it, they say there will be no mysteries and no poison pills. So they’re making it not impossible to clone. Why are they being so generous? (A little sarcasm, sorry.) ”
” Further if you can get all the services by coming to Miguel or you or me, plus freedom of choice, some part of the market is going to go for that. I’d argue it’s the most important part — independent developers.”
“Freedom of choice is good for everybody. (Forced freedom is the same as no freedom). Things go faster and spread more quickly when a lock down from a single vendor is thwarted. Redirected vendors are helpless to stop it. Because the vendor being redirected makes money-or in the case of AOL continues to spread their client around-and there isn’t a damn thing they can do about somebody redirecting the data flow. Redirection is tough to thwart by the most litigious vendor. A vendor really serious about stopping redirection will end up damaging themselves the most. This usually keeps litigation to a minimum.”
“.NET seemed to me like an upgrade for Win32 developers: they had the same problems we had when dealing with APIs that have been designed over many years, a great deal of inconsistency. So I want to have some of this new “fresh air” available for building my own applications.
”