Google Archive

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.

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.

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.

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.

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

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.

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.

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.

Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.

Recently, our Google AdWords campaigns were suspended without warning. This was the second time that I have encountered this situation. This time, however, timing spoke volumes.

I had several interviews where I voiced concerns about the data gathering and ad targeting practices - in particular, those of Google and Facebook. They collect and aggregate far too much personal information from their users. I see this as a very serious, democracy-threatening problem, as the vast targeting opportunities offered by Google and Facebook are not only good for very targeted marketing, but also for tailored propaganda. The idea of the Internet turning into a battlefield of propaganda is very far away from the ideal.

Two days after my thoughts were published in an article by Wired, we found out that all the campaigns under our Google AdWords account were suspended - without prior warning. Was this just a coincidence? Or was it deliberate, a way of sending us a message?

In the last year while talking to respected security-focused engineers & developers, I've come to fully appreciate Google's Chrome OS design. The architecture benefited from a modern view of threat modeling and real-world attacks. For example, Trusted Platform Module (TPM) hardware chips are built into every Chromebook and deeply incorporated into the OS. The design documents go into some detail on the specific protections that TPM provides, particularly around critical encryption functions.

I also learned that Chromebook is the daily driver for many of Google's own senior developers and security engineers. In short, the combination of the underlying Chromebook hardware with the OS architecture makes for a pretty compelling secure development environment.

It's pretty neat to consider the possibility of pre-travel "power washing" (resetting everything clean to factory settings) on an inexpensive Chromebook and later securely restore over the air once at my destination. Since there is a wide range in Chromebook prices, the engineering challenge here was to find something powerful enough to comfortably use exclusively for several days of coding, writing, and presenting, but also cheap enough that should it get lost/stolen/damaged, I wouldn't lose too much sleep. The threat model here does not include recovery from physical tampering; if the machine were somehow confiscated or otherwise out of my custody, I could treat it as a burner and move on.

Google's director of public policy Leslie Miller said the CfA's report was "highly misleading" and accused it of inflating the numbers by attributing funding to Google when it actually came from associations to which Google belongs.

Miller also points out the non-profit's own transparency issues, given that the CfA's only known backer is Oracle.

Google operates a little-known program to harness the brain power of university researchers to help sway opinion and public policy, cultivating financial relationships with professors at campuses from Harvard University to the University of California, Berkeley.

Over the past decade, Google has helped finance hundreds of research papers to defend against regulatory challenges of its market dominance, paying $5,000 to $400,000 for the work, The Wall Street Journal found.

Google is stopping one of the most controversial advertising formats: ads inside Gmail that scan users' email contents. The decision didn't come from Google's ad team, but from its cloud unit, which is angling to sign up more corporate customers.

Alphabet Inc.'s Google Cloud sells a package of office software, called G Suite, that competes with market leader Microsoft Corp. Paying Gmail users never received the email-scanning ads like the free version of the program, but some business customers were confused by the distinction and its privacy implications, said Diane Greene, Google's senior vice president of cloud. "What we're going to do is make it unambiguous," she said.