Skip to main content

Dart Team Updates for March 2013


The Dart project continues to move forward rapidly, and Anders Sandholm fills us in on what members of the Dart team have been doing recently:


Dart Team Updates, Mar 6 - 19

Dart language specification:
  • Make mixins more useful (apply to arbitrary superclasses).
  • More consistent treatment of malformed types.
  • Examining mechanisms to suppress warnings and checked mode when needed.
  • Liberalizing function subtyping.
  • Develop synchronous mirror API for introspection.

Dart libraries:
  • Core:
    • Added List.asMap
    • remove deprecated Arrays, Date and StringBuffer.add/addAll/addCharCodes.
    • num.round, ceil, floor and truncate now return ints.
    • rename xMatching to xWhere.
    • Added Stream.periodic and rename Timer.repeating to Timer.periodic.
    • Made argument to StringSink.writeln optional.
  • dart:io:
    • Started adding support for detecting and working with symbolic links.
    • Added support for gzip encoding in the http server.
    • Lots of bugfixing after the introduction of dart:io v2. It is looking stable again.
  • dart:html:
    • Much more cleanup - e.g., converting maps to name parameters.
    • Canvas DrawImage improvements

dart2js Compiler:

  • Landed initial support for deferred loading of libraries.
  • Lots of improvements to the way we deal with generics.
  • First round of code size and performance improvements based on global type inferencing. We’re seeing some pretty good results and our scores on DeltaBlue and Richards have improved by ~27% and 8% respectively.
  • Started working on dart:typeddata support in dart2js.

Dartium:
  • Work in progress on using dart:typeddata for typed arrays in dart:html. This will dramatically speed up WebGL performance in Dartium.
  • Various improvements in debugger support
  • Bug fixes

Dart Editor:

  • New analyzer available via experimental preference. (work in progress, all features not enabled yet).
  • Package root preferences removed in favor of --package-root cmd line option
  • Reduced heap usage by ~25%.
  • Fixed a memory leak which could eventually consume 10% of the heap.
  • Fixed a notable Editor performance issue related to Pub and symlinks

Pub (rnystrom):
  • More work on the new tech scheduling framework: scheduled processes and servers
  • Development dependencies
  • Fixed more bugs

Dart Dev Rel (sethladd)


As always, view the changelog for the full list of changes, and to get started with the Editor, see our tutorial.

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 …