[Mono-list] ".NET 3.0" misnomer
Miguel de Icaza
miguel at ximian.com
Mon Aug 14 01:42:10 EDT 2006
> I don't feel any better then.
> From a developer standpoint as well as an end-user standpoint, I don't know
> whether I'm supposed to expect .NET to have much of a future outside
> Windows, in part or in whole. Until the answer to whether or not WinFX will
> be implemented on Mono is a "yes", I never will know.
If you need cross platform APIs, then do not use any APIs that are not
implemented by Mono. It is that simple.
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
My suggestion is to stay on the safe side and use Mono implemented APIs,
and even the Mono stack.
> If things like LinQ aren't reliant on 3.0, then show that in the name for
> God's sake! If you haven't noticed yet, that's what I'm petitioning for.
Linq does not depend on any of the extras in 3.0, it does not depend on
Avalon, does not depend on Workflow, does not depend on Infocard and
does not depend on Indigo (or whatever names they have this week).
More information about the Mono-list