Slashdot Mirror


With 'Virgin' Developers, Microsoft Could Fork Android

colinneagle writes "Amid all the talk about Microsoft forking Android for a smartphone OS, one suggestion involves a look back to Microsoft's DOS days. Microsoft DOS was designed per IBM's specification to run exclusively on IBM's PC hardware platforms. Phoenix Technologies employed software developers it nicknamed 'virgins,' who hadn't been exposed to IBM's systems, to create a software layer between Microsoft's DOS system and PCs built by IBM's competitors. This helped Microsoft avoid infringing on IBM's patents or copyrights, and subsequently helped fuel the explosive growth of PC clones. Microsoft could use the same approach to 'clone' the proprietary Android components in its own Android fork. This would prevent copyright infringement while giving Microsoft access to Google Play apps, as well as Android's massive base of developers." Microsoft (or anyone) could generate a lot of goodwill by completely replacing the proprietary bits of Android; good thing that doing so is a work in progress (and open-source, too), thanks to Replicant. (Practically speaking, though, couldn't Google just make access to the Play Store harder, if Microsoft were to create an Android-alike OS? Even now, many devices running Android variants don't have access to it.)

2 of 241 comments (clear)

  1. Author has obviously no clue at all by Anonymous Coward · · Score: 5, Insightful

    The Phonix bios clean-room implementation was necessary because - d'oh! - Phonix couldn't legaly use the IBM bios implementation. However, Microsoft can use the Android implementation. It's open source for FSM's sake. They can even verbosly copy the various Google APIs, APIs are not copyrightable after all. Google fought that out with Oracle.

    The author of this fine article has obviously no clue what he's talking about.

    1. Re:Author has obviously no clue at all by Billly+Gates · · Score: 5, Interesting

      No it is open like MacOSX is open.

      Google has things locked very tight on Android which will make compatibility difficult and a constantly changing targeting if MS were dumb enough to make an Android fork.

      Windows Phone would turn into a mobile version of OS/2 which is used by few and developers say "Oh it runs Android. Lets just target that only and ignore MS we will get both platforms etc", but in reality Google changes AOSP apis and viola it breaks on Windows Phone.

      Windows Phone is not a bad OS even if it is spouted here as the anti Christ from people who actually never ran it. If it were not made by Microsoft I think people would like it here seriously.