Miguel de Icaza-4 wrote: > > If you need cross platform APIs, then do not use any APIs that are not > implemented by Mono. It is that simple. > I know. That's besides the point though, because you couldn't possibly tell that to Microsoft. Or, that would no doubt be the perception to say the least.
You work with people who know Mono inside out. But believe me, it really isn't good for Mono for there to be more unimplemented .NET components. It just makes both .NET and Mono look flimsy, and certainly as that becomes the case, Microsoft's devs will become more and more careless as well. > As with any other open source project, if you need something that is not > implemented by it, and you absolutely must have it, you can always > implement it. Either yourself, or a third party, but you can implement > it. > > My suggestion is to stay on the safe side and use Mono implemented APIs, > and even the Mono stack. > I know, although I don't think anyone has the resources or energy to implement anything more than a quick hack most of the time. In any case, thanks for taking the time to chat. I'm still not convinced that the name switch is a good move, and it doesn't seem like you disagree with me on that, seeing that you seem to agree with me for the most part, intentionally or not. By the way, if you don't mind me breaking the mailing list etiquette a little (I bet it's there for this exact reason), great work on Mono. I love watching it grow and become more and more useful. -- View this message in context: http://www.nabble.com/%22.NET-3.0%22-misnomer-tf2092941.html#a5793561 Sent from the Mono - General forum at Nabble.com. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
