Skip to main content

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 strong mode – 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 of strong mode, and the large number of users already using it, we have decided to make strong mode the standard type system for Dart. This means that we will initiate a move to 2.0 in three phases: 1) strong mode is opt in, 2) strong mode is the default, and 3) strong mode is the only mode. We are making sure that Dart users have a smooth transition to the new type system, as explained in more detail below.

Moving to strong mode also enables the use of the new Dart development compiler (dartdevc, also known as DDC) instead of Dartium for web app development. With dartdevc you get faster developer cycles and can use any recent version of Chrome – unlocking among other things the use of bleeding edge browser features. Once the developer experience with dartdevc matches that of Dartium, we’ll stop maintaining Dartium.

You should continue to use dart2js to compile your final app. Where dartdevc is optimized for fast refreshes and easy debugging, dart2js is optimized for small generated code size and fast runtime of web apps.

As mentioned above, to help prepare for the transition to strong mode, we’re moving to 2.0 in three phases: In the current phase (phase 1) you can opt in to strong mode and dartdevc. Phase 2 will make strong mode the default, but you'll be able to opt out. Finally, phase 3 will make strong mode the only type system for Dart, and eventually we’ll remove Dartium.


We believe these changes will help you and your team be more productive when writing Dart apps. If you’d like to try out strong mode and dartdevc with your web apps, check out the Dart 1.24 announcement and follow the instructions in the Tool Changes section of the changelog. To use strong mode when building for mobile, check out flutter.io.

As always, we’d love to hear about your experiences with Dart and strong mode – especially if you encounter issues when transitioning to dartdevc and our new type system.

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

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 …