Skip to main content

Simplifying Dart's HTML bindings

Posted by Jacob Richman


We are changing the implementation of dart:html from a wrapper based solution to a wrapper-free solution.  The dart:html API will not change as part of this transition but it will no longer be possible to use dart:html and dart:dom from within the same isolate. Also, the dart:htmlimpl library will go away.

Why are we doing this?

  • Smaller compiler output because dead code elimination is more effective with the new solution.
  • Faster compile times as dart:html is expressed directly rather than being expressed as a wrapper layer on top of dart:dom.
  • Faster runtime execution and lower runtime memory usage as the overhead of wrapping and unwrapping is avoided.

This change will happen as soon as early next week.

A few tradeoffs include:

  • It will no longer be possible to import dart:html and dart:dom within the same isolate.  At some point we expect to remove dart:dom completely so it doesn’t make sense to try to support this use case.  Supporting it would be extremely difficult and fragile given wrapper free implementations of both libraries.
  • dart:htmlimpl is going away as it doesn’t make sense to expose publicly given that the implementation of dart:html on Dartium will continue to use wrappers for some time.  dart:htmlimpl was only needed before to work around known broken or missing functionality in dart:html.  This escape hatch will not be needed with the updated library as dart:html and dart:dom are generated by the same script so the dart:html versions of rapidly evolving APIs such as Web Audio API will always function just as well as the dart:dom versions.

Once the new version lands if there is functionality in dart:dom that you needed, but not in dart:html, please file bugs.

Popular posts from this blog

Dart in 2016: The fastest growing programming language at Google, 2nd fastest growing in TIOBE Index

Dart was the fastest growing programming language at Google in 2016 with millions of lines of code written. It also made it to TIOBE Index Top 20 this month (see TIOBE's methodology).

It takes time to build something as ambitious as Dart and, in some ways, Dart is still in its infancy. But we're glad the hard work is starting to pay off.

Many thanks to our amazing community!

We're going to celebrate by ... releasing 1.22 next week (as per our usual 6 week release schedule).

The new Google AdSense user interface: built with AngularDart

AdSense is a free, simple way to earn money by placing ads on your website. The team just launched a completely new version of their app for publishers. Read all about it here. We asked Daniel White, the tech lead for the project, some questions because the new UI happens to be built with Dart and Angular2.


AdSense launched way back in 2003. How long is it since the last big redesign?
Last big redesign was called ‘AdSense 3’ and launched about 6 years ago. It was written in Google Web Toolkit (GWT) and the UI has evolved through several iterations - but this is the first ground-up redesign in 6 years. There are a number of long-standing UX issues that we’ve taken the opportunity to solve. A big shout-out to our UX team who’ve been 100% behind this project. We couldn’t have done it without them!

How many software engineers worked on the project?
Purely on the AdSense applications, we have a team of close to 100. Around 25% of them write Dart.

How many lines of code?
We have around 160K LO…

AngularDart 2.1 and new Components

AngularDart got its own dedicated team 5 months ago. Last month, we launched 2.0 final on the Dart Developer Summit. Today, we’re releasing the first minor release after that: 2.1.

Since the focus of AngularDart is Productivity, Performance, Stability, there are no major breaking changes (see the changelog) — but a lot of behind-the-scenes improvements. Your apps will get slightly smaller and faster (even relative to 2.0 which already made huge strides in size and performance since the compiled-from-TypeScript days).

Many features that AngularJS had to implement for JavaScript and TypeScript are not needed in Dart (because Dart already has those features out-of-the-box). So we’re removing them from AngularDart. Renderer is deprecated in favor of plain-old dart:html. NgPlural is going away — Dart programs can use the package:intl library.

New components

On the Dart Developer Summit, we launched AngularDart Components — the material design widgets Google is using in customer-facing apps …