Skip to main content

5 items the Dart team has on their radar

Posted by Seth Ladd

Hello Dartisans,

Some of you have asked what the bigger picture is with what we’re working on. The Dart team has the following items on their radar. There is no particular order or priority implied, nor is this exhaustive, but these are some of the features we are either working on or intend to work on.

Across all components we are working improving performance and stability.


  • Dart language and libraries
    • Language see http://goo.gl/2Z9ZY (Area-Language, Milestone-M1)
    • dart:html: parity with the deprecated dart:dom, IndexedDB
    • dart:io: HTTPS, improved HTTP support, optimize performance
    • Package manager: discover, install, upgrade, version, and publish.
    • Date refactoring
    • Continued work on Future and Isolates API
  • Dart Editor
    • background analysis (which will provide a significant speedup)
    • debugging support (browser and VM)
    • simple refactoring support (various rename options to start)
    • search improvements (like text search in libraries)
  • Dart VM
    • debugging standalone and server programs (from command line and from Editor).
    • conformance with the language spec (in particular synchronize with dart2js when implementing new features)
    • implementation of mirror based reflection
    • improved handling of GC
    • rollout of optimizations to the new compiler pipeline
  • Dartium and Dart + Dev Tools
    • dev tools debugger to understand Dart scripts
  • Dart compiler to JavaScript
    • dart2js to replace frog
    • conformance with the language spec
    • improve size and performance of generated JS code

As always, thanks for trying Dart! Please join the Dart mailing list for discussions, and check out Stack Overflow for how-to questions. Please use http://dartbug.com to file bugs and issues.

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).

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 …

AngularDart 3.0: Easy upgrade, better performance

AngularDart 3.0 is now available. It brings better performance and smaller generated code, while also making you more productive.


Version 3.0 is an evolution: although it has some breaking changes (detailed below), it is a smooth upgrade due to minimal public API adjustments. Most of the progress is under the hood—in code quality, stability, generated code size, performance, and developer experience.

Code quality:
2731 instances of making the framework code more type safe (using sound Dart).The AngularDart framework code size is down by 12%.Many additional style updates to the codebase:Changed to use idiomatic <T> for generic methods.Removed NgZoneImpl, all the code exists in NgZone now.Stability:
Many CSS encapsulation fixes due to update with csslib package.Fixed bugs with IE11.

Performance:
For the Mail sample app, we see 30% faster time-to-interactive (currently 3812 ms on a simulated 3G connection, measured via Lighthouse).Our large app benchmark shows 2x faster render times of…