Channels ▼
RSS

Mobile

Google Chrome Dev Summit Promises Real Guts


Google is promising developers a new focus on application performance enhancement and an enriched set of web APIs in line with its Google Chrome Developer Summit scheduled for this November.

In addition to the API focus, Google is turning its all-seeing eye to multi-device workflows, performance tips, and the guts of Blink.

NOTE: Blink is the rendering engine used in Chrome. Blink is implemented on top of an abstract platform and thus cannot be run by itself — the Chromium Content module provides the implementation of this abstract platform required for running Blink.

Google's developer tuition strategy hinges around learning how to build for a multi-device world and the need to "maintain the scale" of code so that programmers can (as Google puts it) "laugh in the face" of dropped network connections.

The search giant now turns it attention to how we should live in a declarative world with web components and how we can optimize performance across GPU, CPU, and the network.

Also in the spotlight are the +Dart client libraries for Google APIs. Google says that each client library is bundled as a pub package and uploaded to http://pub.dartlang.org (this is Dart's package hosting service).

August has also seen Google developers concentrate on cloud platform updates including layer 3 load-balancing capabilities for the Google Compute Engine. There are also new features and productivity improvements for Google Cloud Datastore — plus improvements to the PHP runtime as part of the Google App Engine 1.8.3 release.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video