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.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide