Skip to main content

Dart Team's "Weekly" Digest

Posted by Anders Sandholm

It’s been a while since the last update, but here’s a summary of the recent events in Dart-land. 

First version of the Dart Language Tour is published.

In the Dart language specification, we’ve revised the switch statement specification. There is also an ongoing triage of all open language bugs: classify as either something to be acted on, something that may be considered in the future, or most likely won’t happen.

In the Dart-to-JavaScript Compiler we have:
  • Added rough first version of dart2js to the SDK.
  • Started shrinking the generated code through type-based tree shaking and simplifications of code patterns (much more to come).
  • Changed all bitwise operations to yield 32-bit unsigned results thus making it easier to write algorithms that manipulate bits (crypto, hashing).
  • Added preliminary support for reified generics (work in progress).
The Dart Editor now has the following included 
  • Run button launches last run except if application or html file is selected
  • Debugging VM applications (work in progress)
  • AnalysisServer fixes and improvements
  • Auto updater (work in progress)
  • Trim memory used by DartC
  • Rename refactoring, code completion, and analysis fixes and improvements
  • Improvements and fixes to UI test suite
Dart Server libraries:
  • Added initial version of crypto library: lib/crypto/crypto.dart. Initially supports sha1, sha256 and HMAC.
  • Added support for WebSocket servers and clients.
  • Added support for links in File and Directory dart:io APIs on Linux and Mac.
  • Added files needed for native extension development to the SDK.
  • Changed the error-handling behavior in dart:io. If an error occurs and there is no error handler an exception will now be thrown. This gets rid of silent failures that makes applications hard to debug.

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…

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and – even more so – from large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …