Google Brushes Off "Outside" Android Devs...Again
The turmoil that began just over a month ago with a mis-addressed email has boiled over again for Google, after the company issued what was termed "verbal silence" in reply to a petition from more than 200 Android developers.
The original uproar began in mid-July when Google Developer Advocate David McLaughlin accidentally sent an email to the public Android developers list revealing that the company had been providing the contestants in the Android Developer Challenge with updated SDKs — under a non-disclosure agreement — while other developers were forced to work with badly outdated materials. In response to this revelation, an Android developer from Germany, Nicolas Gramlich, drafted a petition calling on Google to provide updates to the SDK as well as increased information about the platform's progress, and began circulating it among Android developers.
The current brouhaha erupted as a result of Google's response to that petition. After sending the petition, complete with 245 signatures, to Google's Android Advocate, Gramlich received an all-but-nonexistent reply. The two-sentence response, which Gramlich subsequently posted to the Android developers forum, reportedly reads:
Thanks for taking the time to send this. — David
Exactly who David is, or what his function within Google might be, was not indicated, though a reasonable guess would be David McLaughlin, the Developer Advocate who set the initial firestorm off with his overeager emailing. What doesn't require any guessing, however, is what the feeling is among the Android developers, who have now been brushed off a second time.
Update: Google has released an updated SDK along with a roadmap for future development.
Justin Ryan is a Contributing Editor for Linux Journal.
Fast/Flexible Linux OS Recovery
On Demand Now
In this live one-hour webinar, learn how to enhance your existing backup strategies for complete disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible full-system recovery solution for UNIX and Linux systems.
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
|Working with Command Arguments||May 28, 2016|
|Secure Desktops with Qubes: Installation||May 28, 2016|
|CentOS 6.8 Released||May 27, 2016|
|Secure Desktops with Qubes: Introduction||May 27, 2016|
|Chris Birchall's Re-Engineering Legacy Software (Manning Publications)||May 26, 2016|
|ServersCheck's Thermal Imaging Camera Sensor||May 25, 2016|
- Secure Desktops with Qubes: Introduction
- Working with Command Arguments
- Secure Desktops with Qubes: Installation
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- CentOS 6.8 Released
- The Italian Army Switches to LibreOffice
- Linux Mint 18
- Chris Birchall's Re-Engineering Legacy Software (Manning Publications)
- ServersCheck's Thermal Imaging Camera Sensor
- Petros Koutoupis' RapidDisk
Until recently, IBM’s Power Platform was looked upon as being the system that hosted IBM’s flavor of UNIX and proprietary operating system called IBM i. These servers often are found in medium-size businesses running ERP, CRM and financials for on-premise customers. By enabling the Power platform to run the Linux OS, IBM now has positioned Power to be the platform of choice for those already running Linux that are facing scalability issues, especially customers looking at analytics, big data or cloud computing.
￼Running Linux on IBM’s Power hardware offers some obvious benefits, including improved processing speed and memory bandwidth, inherent security, and simpler deployment and management. But if you look beyond the impressive architecture, you’ll also find an open ecosystem that has given rise to a strong, innovative community, as well as an inventory of system and network management applications that really help leverage the benefits offered by running Linux on Power.Get the Guide