[id-android] WTI: Artikel Menarik Tentang Google Dalam Memaknai Arti Dari Sifat Keterbukaan Android (CNET)
*What Google really means when it calls Android 'open'* Google loves to woo app makers to Android by whispering the sweet sounds of openness and open source in their ears. While that's not entirely accurate, they heed the call for good reasons. Is Android fully open? Well, no, but quasi-open gets most developers to exactly where they want to be. (Credit: CNET) The gooey center of Google's pitch to developers to make apps and services for Android is a series of terms easily misunderstood, but central to Android's flexibility and success. Every once in a while, Android http://www.cnet.com/android-atlas/terminology discussions flare up like a stomach ulcer for Google. They center on Android's nature as a development platform, which in turn affects the variety and breadth of Android apps -- from Minecraft to Pandora to the latest Flappy Bird copycats -- that you can download, and how up-to-date they are. Is Android truly open-source? Can you fork Android? What does Google mean when it talks about Android's openness? The latest debate was sparked by recently discovered documents that revealhttp://online.wsj.com/news/articles/SB10001424052702304888404579378850231234912?mg=reno64-wsjurl=http%3A%2F%2Fonline.wsj.com%2Farticle%2FSB10001424052702304888404579378850231234912.htmlstringent restrictions on device makers that want access to Google's search engine, the video service YouTube, and more than a million apps found in the Google Play app store. European antitrust authorities are looking at whether Google has unfairly taken advantage of Android's position to push its own services and apps, according to The Wall Street Journal. The question of how you define 'openness' depends on what you want 'openness' to mean. --Avi Greengart, analyst The source, if you will, of Android's problems is its open source nature and a fundamental misunderstanding of what Google is doing with Android. So let's take a look at what we're really talking about when we talk about open source and openness. Openness is both a lure for developers, who want to create freely, and a trap that Google has built for itself. It's a term that the company uses to describe its approach to Android, but because it's a fairly common term it's come to mean different things to different people. As such, it's highly dependent on their interests. The question of how you define 'openness' depends on what you want 'openness' to mean, said Avi Greengart, an analyst at Current Analysis. Do you want to be part of the process to define the software from the outset? Do you want to create a phone that exemplifies the best of Android and Google services together? Google's approach to Android development and the Android ecosystem promotes an atypical definition of the terms. The easier one to explain is how Android relates to open source. Historically, open source coding projects large and small have been developed and managed by communities open to all. Firefoxhttp://www.cnet.com/firefox-3/and Linux are prime examples of that. The Android Open Source Project, or AOSP, is the Android code made available to all. Linux is the basis for Android, but Android has a key difference. It's developed behind closed doors at Google, and then once new versions are ready, they're made available to the public. It's the biggest and possibly the only open-source project developed this way. There's often a short delay between a new Android version being completed and when the code is made public, and there's rarely any public input on Android code before release. Open and openness in the Android world are a bit more nebulous. Google's argument is that Android is open because the code is opened to all, because Google doesn't charge for the platform, and because developers have access to it all. The only restriction is on Google services, for which the company demands that phone makers conform to certain specifications. Google's take on Android is that they make it as open as possible. Dianne Hackborn, a tech lead on Android at Google who has worked on Android since its early days, recently commented at length on Android development, openness, and how AOSP relates to Android with Google services integratedhttp://arstechnica.com/information-technology/2014/02/neither-microsoft-nokia-nor-anyone-else-should-fork-android-its-unforkable/?comments=1start=80. One of the things that is interesting about platforms today versus the traditional desktop is that these cloud services are becoming increasingly central to the core platform experience, she said. This presents a special challenge to an open-source platform, which can't really provide such cloud services as part of the standard platform implementation. The tension between the quasi-open-source operating system and access to proprietary cloud services, including programming hooks called Application Programming Interfaces (APIs), and encompassing Google apps such as the Play Store, Google Music, and Google
Re: [id-android] WTI: Artikel Menarik Tentang Google Dalam Memaknai Arti Dari Sifat Keterbukaan Android (CNET)
Nice reading, om Alv. Take out saya kok malah berasa ada hidden business agenda yah dari pembuat artikel ini. Mungkin butuh baca beberapa kali untuk benar-benar paham. On Feb 15, 2014 5:49 AM, Alvin Tedjasukmana alvin.tedjasukm...@gmail.com wrote: *What Google really means when it calls Android 'open'* Google loves to woo app makers to Android by whispering the sweet sounds of openness and open source in their ears. While that's not entirely accurate, they heed the call for good reasons. Is Android fully open? Well, no, but quasi-open gets most developers to exactly where they want to be. (Credit: CNET) The gooey center of Google's pitch to developers to make apps and services for Android is a series of terms easily misunderstood, but central to Android's flexibility and success. Every once in a while, Android http://www.cnet.com/android-atlas/terminology discussions flare up like a stomach ulcer for Google. They center on Android's nature as a development platform, which in turn affects the variety and breadth of Android apps -- from Minecraft to Pandora to the latest Flappy Bird copycats -- that you can download, and how up-to-date they are. Is Android truly open-source? Can you fork Android? What does Google mean when it talks about Android's openness? The latest debate was sparked by recently discovered documents that revealhttp://online.wsj.com/news/articles/SB10001424052702304888404579378850231234912?mg=reno64-wsjurl=http%3A%2F%2Fonline.wsj.com%2Farticle%2FSB10001424052702304888404579378850231234912.htmlstringent restrictions on device makers that want access to Google's search engine, the video service YouTube, and more than a million apps found in the Google Play app store. European antitrust authorities are looking at whether Google has unfairly taken advantage of Android's position to push its own services and apps, according to The Wall Street Journal. The question of how you define 'openness' depends on what you want 'openness' to mean. --Avi Greengart, analyst The source, if you will, of Android's problems is its open source nature and a fundamental misunderstanding of what Google is doing with Android. So let's take a look at what we're really talking about when we talk about open source and openness. Openness is both a lure for developers, who want to create freely, and a trap that Google has built for itself. It's a term that the company uses to describe its approach to Android, but because it's a fairly common term it's come to mean different things to different people. As such, it's highly dependent on their interests. The question of how you define 'openness' depends on what you want 'openness' to mean, said Avi Greengart, an analyst at Current Analysis. Do you want to be part of the process to define the software from the outset? Do you want to create a phone that exemplifies the best of Android and Google services together? Google's approach to Android development and the Android ecosystem promotes an atypical definition of the terms. The easier one to explain is how Android relates to open source. Historically, open source coding projects large and small have been developed and managed by communities open to all. Firefoxhttp://www.cnet.com/firefox-3/and Linux are prime examples of that. The Android Open Source Project, or AOSP, is the Android code made available to all. Linux is the basis for Android, but Android has a key difference. It's developed behind closed doors at Google, and then once new versions are ready, they're made available to the public. It's the biggest and possibly the only open-source project developed this way. There's often a short delay between a new Android version being completed and when the code is made public, and there's rarely any public input on Android code before release. Open and openness in the Android world are a bit more nebulous. Google's argument is that Android is open because the code is opened to all, because Google doesn't charge for the platform, and because developers have access to it all. The only restriction is on Google services, for which the company demands that phone makers conform to certain specifications. Google's take on Android is that they make it as open as possible. Dianne Hackborn, a tech lead on Android at Google who has worked on Android since its early days, recently commented at length on Android development, openness, and how AOSP relates to Android with Google services integratedhttp://arstechnica.com/information-technology/2014/02/neither-microsoft-nokia-nor-anyone-else-should-fork-android-its-unforkable/?comments=1start=80. One of the things that is interesting about platforms today versus the traditional desktop is that these cloud services are becoming increasingly central to the core platform experience, she said. This presents a special challenge to an open-source platform, which can't really provide
