Keep OSNews alive by becoming a Patreon, by donating through Ko-Fi, or by buying merch!

Google Archive

Linux apps on Chrome OS: an overview

Here's all you need to know about Google's year-long secretive development of Linux app functionality in Chrome OS, also known as Project Crostini.

In a nutshell, it's a way to run regular Linux applications on Chrome OS without compromising security or enabling developer mode. The (not yet available) official setting states that it's to "Run Linux tools, editors, and IDEs on your Chromebook."

Crostini is a culmination of several years of development that enabled the functionality to run securely enough to meet Chrome OS's high-security standards. To understand why it's only just appearing, it's best to look at what came before.

This should make easy to manage, safe, and secure ChromeBooks infinitely more attractive to developers.

Google launches major Gmail redesign

Email is a necessity for most of us. We use it to stay in touch with colleagues and friends, keep up with the latest news, manage to-dos at home or at work - we just can't live without it. Today we announced major improvements to Gmail on the web to help people be more productive at work. Here's a quick look at how the new Gmail can help you accomplish more from your inbox.

A major redesign of the Gmail web interface is now available for testing.

The Google Assistant is going global

Android users are all around the world, so from the start, our goal has been to bring the Assistant to as many people, languages, and locations as possible. The Assistant is already available in eight languages, and by the end of the year it will be available in more than 30 languages, reaching 95 percent of all eligible Android phones worldwide. In the next few months, we’ll bring the Assistant to Danish, Dutch, Hindi, Indonesian, Norwegian, Swedish and Thai on Android phones and iPhones, and we’ll add more languages on more devices throughout the year.

We’re also making the Assistant multilingual later this year, so families or individuals that speak more than one language can speak naturally to the Assistant. With this new feature, the Assistant will be able to understand you in multiple languages fluently. If you prefer to speak German at work, but French at home, your Assistant is right there with you. Multilingual will first be available in English, French and German, with support for more languages coming over time.

This is a decent improvement, but progress on the multilingual front is still quite slow. I understand this is a hard and difficult problem to solve, but if this issue was in any way related to increasing ad revenue, Google would've cracked it 5 years ago.

Chrome to start blocking annoying ads

The web is an incredible asset. It's an engine for innovation, a platform for sharing, and a universal gateway to information. When we built Chrome, we wanted to create a way for people to interact with the magic that is the web, without the browser getting in the way. We created a browser that took up minimal space on your screen, made the omnibar so you could quickly search or get directly to a website, and built our pop-up blocker to help you avoid unwanted content. Since then we’ve also added features such as Safe Browsing, pausing autoplay Flash and more - all aimed at protecting your experience of the web.

Your feedback has always played a critical part in the development of Chrome. This feedback has shown that a big source of frustration is annoying ads: video ads that play at full blast or giant pop-ups where you can’t seem to find the exit icon. These ads are designed to be disruptive and often stand in the way of people using their browsers for their intended purpose - connecting them to content and information. It's clear that annoying ads degrade what we all love about the web. That's why starting on February 15, Chrome will stop showing all ads on sites that repeatedly display these most disruptive ads after they've been flagged.

Good news for those still not using an adblocker, and bad news for sites that repeatedly display annoying ads.

The insane amount of backward compatibility in Google Maps

I still keep a couple of my favorite old smartphones. Sometimes I use one of them as my primary device for fun. Phones are among the fastest evolving markets, even a year makes a whole lot of differences. One of the biggest challenges with using old phones is the software: they don’t run modern software. And old software isn’t compatible with new websites, frameworks, encryption standards, APIs. Use an old device, and you will find yourself unable to get anything done. Every app crashes or complains that it can’t connect to the server. Even with Apple who is doing a fantastic job of keeping their phones updated, you may notice that many sites and apps have started dropping support for the iPhone 5, which is still a totally capable device.

But there is always an unlikely app that consistently works on all of my devices, regardless of their OS and how old they are: Google Maps.

I have a whole slew of old PDAs and phones, and even something as simple as getting them online through wireless internet is a major hassle, because they don't support the more advanced encryption protocols. Even if you do manage to get them online, they often won't support IMAP or or they'll lack some key email protocol settings. The fact that Google Maps apparently keeps on working is fascinating.

The shallowness of Google Translate

Such a development would cause a soul-shattering upheaval in my mental life. Although I fully understand the fascination of trying to get machines to translate well, I am not in the least eager to see human translators replaced by inanimate machines. Indeed, the idea frightens and revolts me. To my mind, translation is an incredibly subtle art that draws constantly on one's many years of experience in life, and on one's creative imagination. If, some "fine" day, human translators were to become relics of the past, my respect for the human mind would be profoundly shaken, and the shock would leave me reeling with terrible confusion and immense, permanent sadness.

As a translator myself, I can indeed confirm Google Translate is complete and utter garbage, but the idea that I would "mourn" the end of translators seems outlandish to me. The unstoppable march of technology has eliminated countless jobs over the course of human existence, and if translators are next, I don't see any reason to mourn the end of my occupation. Of course, it'd suck for me personally, but that's about it.

That being said, I'm not afraid of running out of work any time soon. Google Translate's results are pretty terrible, and they only seem to be getting worse for me, instead of getting better. There's no doubt in my mind that machine translation will eventually get good enough, but I think it'll take at least another 20 years, if not more, to get there.

Google’s Fuchsia OS on the Pixelbook: it works!

So after the recent news that the Fuchsia team picked the Chrome OS-powered Google Pixelbook as a supported device, we jumped at the chance to get it up and running. And after a little elbow grease, it actually booted. Now, we're not just running the system UI on top of Android like last time, we're running Fuchsia directly on a piece of hardware!

This means it's finally time for a deep dive on what Fuchsia looks like in early 2018. Our usual in-development OS testing caveats apply: Fuchsia only started development in 2016 and probably has several years of development time ahead of it. Everything can - and probably will - change between now and release (if a release ever even happens). Google won't even officially acknowledge the OS exists - Fuchsia is a bunch of code sitting on fuchsia.googlesource.com.

This is quite exciting, and I'm definitely jealous I can't justify buying a Pixelbook just for this. Not that I could - as with everything Google, it's not available here.

Google memory loss

Tim Bray, former Google employee, currently working at Amazon, writes:

I think Google has stopped indexing the older parts of the Web. I think I can prove it. Google’s competition is doing better.

It's an interesting theory for sure, but it seems hard to back this up with any tangible evidence. How would you even test this? You can pick specific web sites to test this with, but that will always be an incredibly small - infinitesimally, unbelievably small - subset of web sites, and there's no way to extrapolate any of that to the web as a whole. To make matters worse, Google tailors search results to the information they have on you, making this even harder.

Google Fuchsia for Pixelbook

We've been talking about Google's mysterious Fuchsia operating system for a while now, and today, we have a new piece of the puzzle. It's a small piece, for sure, but with Google being so incredibly secretive about the whole thing, we take what we can get. As it turns out, Google has added support for its Pixelbook to Fuchsia, and added a page on how to prepare the Pixelbook for Fuchsia installation, and you can check the how-to commit for information about the installation itself.

Still a far cry from anything even remotely tangible about where Fuchsia is going, but even a slow drip can eventually fill a bucket.

Android Parallel Tasks incoming with Chrome OS 64

Android applications, running on either Android itself or on Chrome OS, pause whenever they're not in focus. While this makes sense on a phone, this doesn't make a whole lot of sense on desktop machines such as Chromebooks. As such, Google is addressing this shortcoming with Parallel Tasks.

With that in mind, the expected behavior of an open app is that it would remain active and running even when the user clicks to another window. Coming from Windows, Linux, or Mac OS, this is what users expect and it is a bit confusing unless you understand what is happening.

Parallel tasks on Android allow the OS to keep everything running and open until you pause the activity or close the app down. Again, with Chrome OS, this is much easier to manage. Just click the "X" on the app and it is closed. Simple.

Nothing groundbreaking in and of itself, obviously, but a hugely important 'feature' to have on a laptop or desktop.

Google does not know multilingual people exist

It's time to address a longstanding issue with Google, and as these things often go, it has to do with Silicon Valley not knowing multilingual people are a thing.

A long, long time ago, searching for stuff on Google in different languages was a breeze. If you typed www.google.nl in your address bar, you went to Dutch Google. If you typed www.google.com, you went to English Google. If you typed www.google.de, you went to German Google. You may notice a pattern here - the country code determined your Google Search language. Crude, but effective.

Years ago, however, Google, ever on the lookout to make its users' lives easier, determined, in its endless wisdom, that it would be a great idea to automatically determine your search language based on your location. Slightly more recently, Google seems to have started using not your location, but the information it has on you in your Google account to determine the language you wish to search in when you load Google Search, and on top of that, it tries to guess your search language based on the query you entered.

Regardless of whether I go to www.google.nl or to www.google.com, Google standardises to Dutch. The language menu in Tools is entirely useless, since it only gives me the option to search in "Every language" or "Only pages written in Dutch". When I type in a longer, clearly English query, it will switch to showing English results for said query. However, with shorter queries, single-word queries, brands, or other terms that might transcend a specific language, Google simply doesn't know what to do, and it becomes a game of Guess What Language This Query Is Parsed As.

As I've detailed before, Silicon Valley doesn't get out much, so they don't realise hundreds of millions of people around the world lead multilingual lives, speaking and searching in several different languages on a daily basis. Many Americans speak both Spanish and English on a daily basis, for instance, and dozens of millions of Europeans speak both their native language as well as English. Especially younger European generations have friends from all over the world, and it's likely they converse in today's lingua franca.

Of course, for me personally, the situation is even more dire. I am a translator, and especially when working on more complex translations, I need to alternate between English and Dutch searches several times a minute. I may need to check how often a term is used, what it means exactly, if a technical term is perhaps left untranslated in Dutch, and so on. I need to be able to explicitly tell Google which language to search in.

In its blind, unfettered devotion to machine learning and artificial intelligence, Google has made it pretty much impossible for me to use, you know, Google.

Meanwhile, DuckDuckGo has a really neat little switch right at the top of its search results, which I can click to switch between English and Dutch - I don't even have to retype the query or reload the site from the address bar. The dropdown menu next to it gives me access to every single other language DuckDuckGo is available in. It's difficult to overstate how this feature has turned web search from a deeply frustrating experience into the frictionless effort it's always supposed to have been.

This tiny, simple, elegant little feature is what has drawn me towards using DuckDuckGo. I'm willing to accept slightly less accurate search results if it means I don't have to fight with my search engine every single day to get it to search in the language I want it to.

I will continue to harp on Silicon Valley for barely even paying lip service to multilingual users, because it frustrates our entire user experience on a daily basis. To make matters worse, virtually all popular tech media consist of Americans who only speak English, assuring that this issue will never get the attention it needs.

Google adds Fuchsia support to Apple’s Swift

Google's in-development operating system, named 'Fuchsia,' first appeared over a year ago. It's quite different from Android and Chrome OS, as it runs on top of the real-time 'Magenta' kernel instead of Linux. According to recent code commits, Google is working on Fuchsia OS support for the Swift programming language.

There's a tiny error in this summary form AndroidPolice - Fuchsia's kernel has been renamed to Zircon.

All this has been playing out late last week and over the weekend - Google is now working on Swift, and some took this to mean Google forked Apple's programming language, while in reality, it just created a staging ground for Google to work on Swift, pushing changes upstream to the official Swift project when necessary - as confirmed by Chris Lattner, creator of Swift, who used to work at Apple, but now works at Google.

Zac Bowling, a Google engineer working on Fuchsia, then highlighted a pull request that Google pushed to the main Swift repository: Swift support for Fuchsia. He also mentioned a few upcoming pull requests:

FYI, in the pipeline after this we will have some PRs related to:

  • adding ARM64 support for the Fuchsia SDK
  • fixing cross-compiling issues for targeting BSD, Linux and Fuchsia targets from a Darwin toolchain
  • adding support for using lld for linking specific SDK stdlibs (part of getting a Darwin toolchain capable of cross compiling to other targets)
  • supporting unit tests on Fuchsia

Regarding Fuchsia's purpose, this is yet another little puff of smoke. Sadly, we still haven't found the fire.

Waymo’s self-driving cars on public roads – without a driver

Waymo recently hosted a number of journalists at its private Castle testing compound, and treated us to rides with no safety driver behind the wheel - now, the former Google self-driving car company is going farther still, however, launching public road tests of its autonomous Chrysler Pacifica minivans with no safety driver on board.

The tests aren't limited to one or two routes, either; the test area where the truly driverless trials are being conducted is in Chandler, Arizona (part of the greater Phoenix metro area), and the cars are able to go anywhere within this defined space. It’s hard to understate the importance of this milestone: Waymo is operating at full Level 4 autonomy, sharing public roads with human-driven cars and pedestrians, with no one at the wheel able to take over in case things don't go as planned.

All my friends live at least an hour's drive away from where I live (assuming no traffic, which is a big assumption in The Netherlands). That's not a long drive by standards of large countries, but for us, it is, and since it basically comes down to a boring drive over a few boring highways in a boring part of the country, it's mind-numbingly tedious.

I can't wait until I can just sit down on the backseat of my car, tell it to drive to Amsterdam or wherever else my friends live, and just chill for an hour with some YouTube or webbrowsing. I know we're not there yet, but I hope I can at least experience that at one point in my life.

Replacing exploit-ridden firmware with a Linux kernel

Two weeks ago, security researchers managed to disable the Intel Management Engine, and last week, Google held a talk at the Open Source Summit (née LinuxCon) in which they unveiled their plans to completely (well, almost completely) replace every bit of code between the operating system you know about (Windows, Linux, BSD, whatever) and the bare metal x86 processor (Intel-only, for now).

With the WikiLeaks release of the vault7 material, the security of the UEFI (Unified Extensible Firmware Interface) firmware used in most PCs and laptops is once again a concern. UEFI is a proprietary and closed-source operating system, with a codebase almost as large as the Linux kernel, that runs when the system is powered on and continues to run after it boots the OS (hence its designation as a "Ring -2 hypervisor"). It is a great place to hide exploits since it never stops running, and these exploits are undetectable by kernels and programs.

Our answer to this is NERF (Non-Extensible Reduced Firmware), an open source software system developed at Google to replace almost all of UEFI firmware with a tiny Linux kernel and initramfs. The initramfs file system contains an init and command line utilities from the u-root project (http://u-root.tk/), which are written in the Go language.

Both the slides from the talk and the video are available.

Google Pixelbook review: emperor of Chrome

Dieter Bohn:

When I think about whether the Pixelbook could reasonably replace a MacBook or a Windows laptop, my gut says that, for most people, the answer is "no." To solve the "last 10 percent" on a Pixelbook, you really have to be very savvy about how to navigate the different computing paradigms of Chrome and Android to make the whole thing work - and even then, it's not easy. Unless you're an expert in the ways of both the web and Android, it shouldn't be your only computer.

If I were Apple or Microsoft, I would be thinking a lot about the generation of students who are savvy with Chromebooks and Android apps, and who might just want the same thing they're used to from their classroom, just in a much nicer package. I don't know that it'll happen this year, though.

Honestly, I think the iPad Pro is a better comparison. On both devices, you can get quite a lot more done than you'd expect, but you have to deeply understand how the platform works to get there. And if you're debating between them, here's the TL;DR: the iPad Pro has better apps, is a tablet-first device, and has a worse web browser. The Pixelbook has worse apps, is a laptop-first device, and has a better web browser.

Dieter Bohn hits the nail on the head here - devices like the iPad Pro or the Pixelbook aren't so much about converting traditional longtime desktop/laptop users - they're about making sure that kids currently growing up with iOS and Android/Chrome OS devices in their pocket or at school have a powerful, all-purpose computing device they already know how to work with and that they already like for the future. It's similar to how people wanted to have the same computer at home as they were using at work - IBM-compatible PCs with DOS and later Windows.

The fact that the iPad Pro and Pixelbook are already as good as they are should really worry Microsoft, most of all.

Is Chrome OS ready to be a tablet OS?

The Pixelbook has a lot in common with the previous Chromebooks that came directly from Google, with a high price tag and a spec sheet to match, but the Pixelbook will showcase the two newest enhancements to Chrome OS with stylus support and a hinge that allows for fold-over convertible use as a tablet. Neither of these things is new (convertible laptop designs have been a Windows staple for ages) but both are new for Google.

Including these features in Chrome and putting them on a high-priced Chromebook aimed squarely at developers and enthusiasts means Google really wants them to become a natural part of the Chromebook experience, and ultimately part of the web experience. So we have to ask, is Chrome finally ready to be a replacement for your tablet?

The answer is a mixed bag. It seems like answers are always that way. And Google needs to lead by example, then get everyone else on board.

Earlier this year, I replaced my aunt's aging Windows Vista (...) laptop with a Chromebook - a nice, solid, aluminium laptop with a good screen, solid trackpad, and amazing battery life. Since I set it up for her, I got to use it for a week before sending it off to my parents, who also used it for a week, after which we sent it to my aunt. All of us - my aunt, my parents, myself - were impressed with just how effortless of a machine it was. No fuss, no fiddling, no extraneous, outdated junk from 40 years of desktop computing getting in the way of browsing, e-mailing, and working with some simple documents.

Chrome OS is a great platform for a large group of non-demanding users, which is why I'm baffled by Google trying to sell us these upscale, fancy Chromebooks with insane amounts of power, and now, apparently, with stylus support and tablet mode? This feels exactly like the kind of extraneous, useless features that will only confuse and get in the way of the kind of people I personally think Chromebooks are great for.

Who is this upcoming Pixelbook for?

Google buys large part of HTC’s smartphone team

Rick Osterloh, Google's senior vice president of hardware, writes:

About a year and a half ago, I joined Google to pursue my dream job to create compelling hardware products, built with Google's smarts at their core. As a first step, we brought together various consumer hardware-related efforts and established a single hardware organization within the company. Our team's goal is to offer the best Google experience - across hardware, software and services - to people around the world. Last fall, we introduced our first family of Made by Google products, including Pixel smartphones, Google Home, Google Wifi, Daydream View and Chromecast Ultra, and we're preparing to unveil our second generation of products on October 4. We're excited about the 2017 lineup, but even more inspired by what's in store over the next five, 10, even 20 years. Creating beautiful products that people rely on every single day is a journey, and we are investing for the long run.

That's why we've signed an agreement with HTC, a leader in consumer electronics, that will fuel even more product innovation in the years ahead. With this agreement, a team of HTC talent will join Google as part of the hardware organization. These future fellow Googlers are amazing folks we've already been working with closely on the Pixel smartphone line, and we're excited to see what we can do together as one team. The deal also includes a non-exclusive license for HTC intellectual property.

This may elicit some flashbacks to Google buying Motorola, but said purchase was more about patents than it was about the company's hardware business - and even after selling Motorola, it turned out this was actually a pretty good deal. Google's sale of Motorola supposedly was part of a series of deals with Samsung, which included a patent-sharing agreement and Samsung promising to stick closer to stock Android.

It seems like Google is feeling more confident now, and is willing to risk agitating Samsung by investing in their own hardware capabilities.