Google Archive

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.

Google renames Fuchia’s Magenta kernel to Zircon

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.

Google changed the name for this project from Magenta to Zircon, which seems like an opportune time to highlight it.

Google: it is time to return to not being evil

Jon von Tetzchner, CEO of Vivalvi (and former CEO of Opera):

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?

Large technology companies have an immense amount of control over and influence on our society, far more than they - or anyone else, for that matter - care to admit. We're way past the point where governments should step in and start to correct this dangerous situation. It's time for another breakup of the Bell System. It's time we, as society, take a long, hard look at corporations - in tech and elsewhere - and ask ourselves if we really want to be subject to the control of organisations we effectively have no democratic control over.

I'm not a proponent of nationalisation, but I am a proponent of breaking up Google, Facebook, Amazon, Apple, Microsoft, and possibly others (I'm sticking to technology for now) to severely limit their power and influence. The products and services these companies create have become too important and too vital to the functioning of our society, and they should be treated as such.

It wouldn't be the first time we, as society, decide a certain product has become too vital to leave in corporations' unrestricted hands.

Introducing Chrome Enterprise

Since we launched Chrome OS in 2009, our goal has been to build the simplest, fastest, and most secure operating system possible. And we've been inspired by all the ways we've seen businesses embrace Chrome, from Chromebooks in the office, to shared Chrome devices in the field, to signage and kiosks for customer engagement in retail. But with so many different business needs - not to mention so many different devices - companies have also told us they want a single, cost-effective solution that gives them the flexibility and control to keep their employees connected. That's why today we're announcing Chrome Enterprise.

Chrome Enterprise offers a host of features, including access to enterprise app storefronts,  deep security controls, 24/7 support, as well as integration with cloud and on-premise management tools, VMware Workspace ONE and Microsoft Active Directory.

Chrome OS keeps marching on.

My $169 development Chromebook

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.

Interesting guide on how to turn an inexpensive Chromebook into a burner developer device safe for international travel.

Google denies funding biased research

It turns out we got played. The WSJ report that Google was funding research specifically to influence lawmakers for its own benefit seems to have been an Oracle-created hit job.

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.

I should've checked the source of the actual report - and specifically, its funding - and I did not. My apologies. While this certainly doesn't magically mean Google is a saint, it does cast this specific report in a very, very different light.

Google Glass 2.0 is a startling second act

What they didn't know was that Alphabet was commissioning a small group to develop a version for the workplace. The team lives in Alphabet's X division, where Glass was first developed as a passion project of Google cofounder Sergey Brin. Now the focus was on making a practical workplace tool that saves time and money. Announced today, it is called Glass Enterprise Edition.

That's what Erickson wears every day. She works for AGCO, an agricultural equipment manufacturer that is an early adopter of Glass EE. For about two years, Glass EE has been quietly in use in dozens of workplaces, slipping under the radar of gadget bloggers, analysts, and self-appointed futurists. Yes, the population of those using the vaunted consumer version of Glass has dwindled, tired of being driven out of lounges by cocktail-fork-wielding patrons fearing unwelcome YouTube cameos. Meanwhile, Alphabet has been selling hundreds of units of EE, an improved version of the product that originally shipped in a so-called Explorer Edition in 2013. Companies testing EE - including giants like GE, Boeing, DHL, and Volkswagen - have measured huge gains in productivity and noticeable improvements in quality. What started as pilot projects are now morphing into plans for widespread adoption in these corporations. Other businesses, like medical practices, are introducing Enterprise Edition in their workplaces to transform previously cumbersome tasks.

They obviously followed my advice from way back in 2014, well before the Enterprise Edition was announced. Totally.

In all seriousness, this is the perfect market for devices like Glass. I don't feel like these kinds of devices have much of a place in our personal lives, but in our professional lives it can improve safety quite a bit by giving people access to information that would otherwise require them to look away from what they are doing.

Inside Google’s academic influence campaign

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.

This is some next-level manipulation. I wasn't kidding when I said we, as a society, need to look at the amount of power we have let corporations gather up. This kind of influence isn't healthy for society.

Google to stop scanning e-mail for ads

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.

Good move, and in the current climate, Google really couldn't continue this practice - automated algorithms or no.

Google hires prominent Apple SoC architect

Google has hired a veteran chip architect away from Apple and is now looking to build its own chips for future versions of its flagship Pixel phone, Variety has learned from sources familiar with the hire. Manu Gulati, who had been spearheading Apple's own chip developments for close to eight years, joined Google in the last few weeks. He publicly announced the job change on his Linkedin profile Tuesday morning, stating that he now works as Google's Lead SoC Architect.

Unsurprising, since Google publicly stated that they were going to build their own silicon for the Pixel way back in October 2016. Google has reportedly also made a deal with LG for displays. It doesn't take rocket science to figure out Google is taking this whole Pixel thing a lot more serious than the glorified rebrand HTC phone that is the first Pixel seems to illustrate.

Chrome gets ad blocker by default

Chrome has always focused on giving users the best possible experience browsing the web. For example, Chrome, like other browsers, prevents pop-ups in new tabs based on the fact that they are annoying. Today, we have an even better understanding of the types of experiences that bother users when it comes to unwanted advertising. New public, consumer-driven research done by the Coalition for Better Ads in creating the Better Ads Standards outlines a number of these experiences, such as full-page ad interstitials, ads that unexpectedly play sound, and flashing ads. In dialog with the Coalition and other industry groups, we plan to have Chrome stop showing ads (including those owned or served by Google) on websites that are not compliant with the Better Ads Standards starting in early 2018.

Interesting that this will also block Google's ads. I'll still feel more comfortable with third party blockers, though.

Google starts tracking offline shopping

Google already monitors online shopping - but now it's also keeping an eye on what people buy in physical stores as it tries to sell more digital advertising.

The Internet giant said Tuesday that a new tool will track how much money people spend in merchants' bricks-and-mortar stores after clicking on their digital ads.

The analysis will be done by matching the combined ad clicks of people who are logged into Google services with their collective purchases on credit and debit cards. Google says it won't be able to examine the specific items bought or how much a specific individual spent.

Well, this seems like something our politicians should prevent. This is such a terrible idea.

At Google, an employee-run mail list tracks harassment complaints

At most companies, if you think you've witnessed sexual harassment, sexism, bigotry or racism, there s one way to get it addressed: going to human resources. At Google, there's another way to air your grievance: submitting your complaint to an employee-run message board that's curated into a weekly email.

The list, called "Yes, at Google," is a grassroots effort to collect anonymous submissions at Google and parent Alphabet Inc. and communicate them across the company, according to five current employees who receive the emails. "Yes, at Google" tracks allegations of unwelcome behavior at work in an attempt to make the company more inclusive, said the employees, who did not want to be named because they were not authorized to speak about internal company matters. Since starting in October, more than 15,000 employees - 20 percent of the company's workforce - have subscribed, according to two of those people.

Google management is aware of the list. "We work really hard to promote and preserve a culture of respect and inclusion," a Google spokesperson said in a statement. "Our employees have numerous ways to raise issues - both negative and positive - with us, including through grassroots transparency efforts like this one. We take concerns seriously and take appropriate measures to address them."

This is a great initiative, and adds a ton of accountability into the reporting process for these matters. I wonder if you could complain if your brand new headquarters has every amenity from a huge gym to a massive wellness centre (...what even?), but no daycare.

“Kill Google AMP before it kills the web”

These, in my view, don't go far enough in stating the problem and I feel this needs to be said very clearly: Google's AMP is bad - bad in a potentially web-destroying way. Google AMP is bad news for how the web is built, it's bad news for publishers of credible online content, and it's bad news for consumers of that content. Google AMP is only good for one party: Google. Google, and possibly, purveyors of fake news.

I haven't encountered enough AMP pages in my browsing time to really form an informed opinion on it, but as a matter of principle, I'm against it. At the same time, however, all of us know that modern websites are really, really terrible. It's why so many of us use ad blockers (on top of privacy concerns, of course) - to make the modern web browsing experience bearable. In that sense, AMP serves a similar role.

Simply put: if everyone created news websites and blogs as fast and light as, say, OSNews, we wouldn't need AMP or ad blockers for speed purposes (you might still want an ad blocker for privacy reasons, of course).

On a related note, something funny happened regarding this specific article. Yesterday, John Gruber wrote:

But other than loading fast, AMP sucks. It implements its own scrolling behavior on iOS, which feels unnatural, and even worse, it breaks the decade-old system-wide iOS behavior of being able to tap the status bar to scroll to the top of any scrollable view.

Setting aside the sulphuric irony of a fervent Apple fan crusading for openness, it turns out that AMP is not implementing its own scrolling at all - the AMP team actually found a bug in Safari, reported it to Apple, and then Apple replied with stating they are switching the whole of Safari over to what Gruber perceived as AMP's own scrolling behaviour:

With respect to scrolling: We (AMP team) filed a bug with Apple about that (we didn't implement scrolling ourselves, just use a div with overflow). We asked to make the scroll inertia for that case the same as the normal scrolling.

Apple's response was (surprisingly) to make the default scrolling like the overflow scrolling. So, with the next Safari release all pages will scroll like AMP pages. Hope Gruber is happy then :)

Well, I thought this was entertaining.