| |||||||||||||
|
| |||||||||||||
Has already happened ;)Has already happened ;)Posted Jun 24, 2005 9:07 UTC (Fri) by NAR (subscriber, #1313)In reply to: Has already happened ;) by pkolloch Parent article: Microsoft Puts Roadblock in Front of Open-Sourcing Avalon and Indigo (eWeek) do not want to clone the API anymore. Instead they want to provide similar functionality in a library that runs in Mono and the original .Net environment. And thus breaking compatibility with the Microsoft libraries...
(Log in to post comments)
Breaking Compatability Posted Jun 24, 2005 10:20 UTC (Fri) by pkolloch (subscriber, #21709) [Link] Yes, obviously, and I outlined above that I do not care.
Has already happened ;) Posted Jun 25, 2005 6:33 UTC (Sat) by lacostej (subscriber, #2760) [Link] Except if they provide a compatibility layer for Microsoft libraries, something that allows to code for the compatibility layer and use Microsoft libraries + layer or mono lib underneath :)
With a transition tool to ease migration. Not sure how technically this is feasible, but that would be fun, turning the problem the other way around.
|
|
||||||||||||