Linked by Kroc Camen on Tue 17th May 2011 12:05 UTC
Permalink for comment 473704
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2006-05-30
I think, for iOS, the more tricky aspect of this is the Mono Runtime itself. It's LGPL (EEEK!!) unless commercially licensed (as it was in MonoTouch.) That means that for Miguel's new venture, they need to Commercially license Mono Runtime from Attachmate to enable them to statically link it to an iOS executable. Do you see a bit of an issue here? I do. I'm not really going to go in to insane speculation mode, but to Commercially license a runtime from your nemesis - isn't this dangerous? Basically, Attachmate would be in direct competition if they continue to sell MonoTouch. So they could easily revoke the license or block it.
No Miguel is a resourceful guy, so I'm hoping they'll just create their own Runtime in the course of this. Then license than as BSD. And we'll all be free of the BS that surrounds staticly linking the Mono Runtime to any exe on any platform