Sorry, momentarily confused Wine and Mono. Wine has never been legally challenged by Microsoft and the development of it has been done clean-room, leaving MS with no legal recourse unless they can demonstrate otherwise. Personally, I don't think they care at all about the existence of wine at this point.
MS has basically gifted the Win32 and
I see these as being two pretty different things, though. Wine is an implementation of Win32 (and
Personally, I believe that either of them should be allowed to be reverse engineered, but they're still somewhat different.
Having had personal technical experience with both Java ME and Android, I gotta say that from a technology point of view, Java ME was a complete and total dead-end. It was far, far different from vanilla desktop/server java than Android is and therefore had practically zero notice or integration with the Java ecosystem. It was designed to work within the restrictions of devices that had single or double-digit CPU MHz and RAM MBs. It was modelled around Java 1.1, with almost no new language features or APIs. RIM used it as the basis for Blackberry and as a developer, I can tell you it was a decision they regretted.
Android is essentially vanilla Java with only the most esoteric of APIs removed from it, and then device-specific APIs placed on top of it. You can use 95% of existing java desktop/server libraries without any modification. If Google was given the option of using Java ME absolutely for free, or developing their own language and APIs, I guarantee they would have made their own because there would have been a riot among their software developers who would have been forced to essentially develop all of the libraries and google apps using the software equivalent of alphabet blocks and duplo. The additional "device profiles" that were subsequently released were too little, too late and hardly any of them were adopted into devices. I can't imagine any situation where Google would have paid Sun or Oracle for a Java ME license.
You know that Kim Stanley Robinson and Spider Robinson aren't related, right?
How does a tool that allows you to re-work your existing iOS or Android source projects into Win10 projects compare to a tool that allows you to convert a document from 1-2-3 or WP into Excel/Word? Or rather, how could it possibly lock a software developer into the Windows platform? This is more like a life-support tactic to allow developers to publish to mobile Windows with minimal effort, with the hope that the platform catches enough traction that developers would start developing native Windows 10 mobile apps. This is identical to what Blackberry did with BB10 to allow developers to publish Android apps that supported it (which I've done at my work). That certainly did absolutely nothing to lock me into the BB10 platform (though it did not make me want to develop for the platform any more than I did).
Why would they want to do this? MS providing a "reworking"/"publishing" tool that lets you easily port iOS and Android apps to Win10 means that more developers are targeting non-MS platforms as their primary platforms. This sounds more like MS is signalling, "We haven't been very successful with this, so we're going to follow your lead for now." There's been a pretty radical culture change in the DevTools/Frameworks/Runtimes teams at Microsoft, signalled by the fact that all of their core runtimes and web frameworks are 100% open source (APL2), published on GitHub (https://github.com/aspnet) and are directly accepting and responding to issue reports and pull requests on these projects. Their new DNX runtime (in preview right now) targets Windows, Linux and MacOS (through Wine, which they are contributing to) and (almost) all of their example code for the new ASPNET5 frameworks is developable and deployable on all three platforms.
3 years ago I would never imagine myself ever recommending any MS development tools to anybody, but here I am now
Btw, Visual Studio 2015 Pro is now 100% free for small organizations or open source projects (branded as Community edition).
they have no problme in programming
Nope. No problme at all, I'm sure they'll see their typo.