Profile cover photo
Profile photo
Peter Beverloo
Software Engineer, Google Chrome
Software Engineer, Google Chrome

Peter's posts

Post has shared content
Super proud of our team in London who made this happen!

+John Mellor Michael van Ouwerkerk +Mounir Lamouri +Matt Gaunt +Paul Kinlan Miguel Garcia 
The Push API and Notification API are now available for Developers in Chrome 42!  The Push API in Chrome relies on a few different pieces of technology, including Web App Manifests and Service Workers.

Check out the HTML5Rocks post at

#ServiceWorker   #PushAPI   #NotificationAPI  
Animated Photo

Post has shared content

Post has shared content
The work of +Michael van Ouwerkerk :-)!  Some discussions surrounding the specifications are the reason this is still experimental, let's hope these can be resolved soon!

Post has shared content

Post has shared content
Device Agnostic Development

The slides from my talk with +Peter Beverloo can be found here:

It was a great opportunity to come at web performance from a slightly different angle :)

If you attended the talk your rating would be much appreciated:


Post has shared content
Thanks for everyone for turning up to my talk at #io13 here are my slides for the mobile html talk I did with +Peter Beverloo 

Post has attachment
Interesting: many of the old user agent detection scripts out there search for "MSIE" to identify Internet Explorer, which will be removed from IE 11. Instead, IE 11's user agent now includes "like Gecko", causing the browser to be detected as Mozilla Firefox and not be served any work-arounds or limited experiences it might serve to Internet Explorer. Interesting approach, but I'm inclined to agree with this :-).

For Web Developers: strongly prefer feature detection over user agent string detection. Opera's new user agent string mentions seven browsers/engines (Mozilla, WebKit, KHTML, Gecko, Chrome, Mobile Safari, Opera)!

Via +Kenneth Rohde Christiansen.

Post has shared content
Here's a story from Chrome's development that isn't as technical (or long) as my omnibox post the other day ( ).

Shortly before our public launch, in August of 2008, the team had moved to a different building, and we'd moved our buildbots with us.  Buildbots are computers that spend their time building and running various tests to ensure that we don't screw things up when we change code in Chrome (and we still use them -- in fact, even more now!  The latest results are available at ).

Anyway, in the new location, a bunch of the buildbots were sitting on racks near a printer.  Unfortunately, these bots kept going offline, which goofed up our test results.  When the infrastructure subteam would investigate, they'd find the circuit breaker for that area had been tripped.

After this happened several times seemingly at random, someone finally figured out that whenever a print job warmed up the printer while the bots were busy, it'd trip the breaker.  Since the bots were really important (especially so close to launch) and there were other printers elsewhere on the same floor, the problem was solved by unplugging the printer and putting signs on it saying OFF UNTIL LAUNCH.

This solution didn't last long.  10 minutes after the printer was unplugged, a maintenance guy showed up, called by some automated system that apparently checked constantly for downed printers.  He insisted he needed to plug the printer back in because of a company policy that people shouldn't have to walk more than a certain distance to a printer.  The infrastructure folks replied that this was unacceptable, and they'd need the printer to stay off until after the public release.  He checked with his boss, who wasn't happy about this idea either.

Finally, the infrastructure folks called in the big guns: they called over our director (now VP), +Linus Upson, to persuade the maintenance folks to leave the printer unplugged.

A day later, maintenance showed up once more.  They packed up the printer and left.  We never saw it again.

[photo has been edited to remove printer names]

Post has shared content

Post has shared content
Thrilled by the momentum of Chromebooks so far and today we're excited to introduce the Chromebook Pixel. The Pixel is built for the power user who lives in the cloud, and we hope it will inspire future innovation.
Wait while more posts are being loaded