The Chromium project decided that the EXT family of filesystems are surplus to requirements, but has bowed to pressure and signalled it is willing to reverse the decision.
As detailed in this thread, the project's developers feel that as Chromium is intended for consumer devices, the ability to read external media formatted with the EXT 2, EXT 3 and EXT 4 filesystems is not a feature it is felt necessary to maintain in future versions of Chrome OS.
For the past year Google developers have been looking at dropping support for EXT* file-systems from ChromeOS while only today it's making the rounds on the Internet and of course Linux fans are enraged.
While ChromeOS is based on Linux and EXT4 continues to be the most widely used Linux file-system and still is used by default on most Linux distributions, Google developers are dropping support for EXT2/EXT3/EXT4 file-systems from their ChromeOS user-interface.
The legal fracas started when Google copied certain elements—names, declaration, and header lines—of the Java APIs in Android, and Oracle sued. A San Francisco federal judge largely sided with Google in 2012, saying that the code in question could not be copyrighted. But the federal appeals court reversed, and ruled that the "declaring code and the structure, sequence, and organization of the API packages are entitled to copyright protection.
AH Google Logo Colored 1.6Each year Google facilitates contests and mentorships to help students from all over the world gain valuable experience in the field of open source code development. Google has recently revealed some of the information regarding their upcoming Code-In and Summer of Code events. The Code-In will begin this upcoming December and last until mid- January. The Summer of Code will begin in May of 2015 and last until August. According to their official statement regarding these programs, Google states that “we are passionate about introducing students to open source software development. Since 2005, the Open Source Programs team at Google has worked with over 10,000 students and over 485 open source projects in a variety of fields to create more code for us all.”
The performance of the device is about acceptable (unfortunately, I do not have any comparison in this device class). Even when typing this blog post in the visual wordpress editor, I notice some sluggishness. Opening the app launcher or loading the new tab page while music is playing makes the music stop for or skip a few ms (20-50ms if I had to guess). Running a benchmark in parallel or browsing does not usually cause this stuttering, though.
This last feature isn’t for the novice users that just buy Chromebooks for their simplicity. But this is World Beyond Windows, where I tout the benefits of Linux, so I can’t leave it out.
Flip the developer mode switch (it’s in software now, but it used to be a hardware switch) and you can get full access to your Chromebook’s internals. You can install a full desktop Linux system (like Ubuntu) alongside your Chrome OS system. Flip over to the Linux system when you want to do some work with traditional desktop apps and powerful terminal commands.
A report from The Information (subscription required) claims that Google tried to buy Cyanogen, Inc, the maker of the custom Android ROM CyanogenMod. According to the report, Cyanogen's chief executive told shareholders that Sundar Pichai, the head of Chrome and Android at Google, met with the company and "expressed interest in acquiring the firm." The report says Cyanogen Inc. declined the offer, saying that it was still growing.
It's unclear what Google would want to do with Cyanogen. The company basically does the same software work any other OEM does: it takes AOSP, customizes it, and ports it to devices. It doesn't have a ton of features that replicate Google services, so without a Google Play license, it's just as poor as any other AOSP-derived Android distribution. Buying Cyanogen would give Google an in-house Android distribution and a team of engineers, both of which it already has in abundance. We suppose the plan could be to buy it and shut it down, but we're not sure what that would accomplish, either.
Google posted a developer overview for Android Auto, offering guidelines for designing extensions to existing Android apps for customized IVI interactions.
Google announced Android Auto with relatively few details at Google I/O in June, following the formation of an Open Automotive Alliance (OAA) in January. These related efforts are designed to standardize integration with Android devices and in-vehicle infotainment (IVI) systems, as opposed to designing an Android IVI stack that runs the whole show. In some ways, Android Auto is similar to the Car Connectivity Consortium’s MirrorLink technology and Apple’s CarPlay.
Bringing Android apps to Chrome OS pushes the two platforms closer together. This sets the stage for Google to merge them completely down the road to have one OS for both mobile and desktop. This is similar to what Microsoft has done with Windows 8, but Google has the advantage of doing it with two existing solid bases that already run well on mobile devices.
Google may not intend to merge the two OSes into one, but they've set the stage to make it easier. They will likely keep sharing features between the two in any event, making both OSes more appealing.