Skip to main content

Dart Team's Digest


Posted by Anders Sandholm

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

In the Dart to JavaScript Compiler we're getting ready to deprecate frog and remove it from the SDK. We increased test coverage for dart2js on build bots, fixed a bunch of browser compatibility issues and landed liveness analysis resulting in 3-4% code size reduction and less temporary variables. Finally, we're now generating smaller code for simple tear-off closures.

In Dartium, we're phasing out dart:dom and are now supporting wrapperless dart:html.

For the Dart Editor we now have new and improved Editor documentation! We also improved code completion in the absence of explicit type information. We have improved type inference in if, while, for and for-in statements and all launches now run in checked mode by default. All launches (JavaScript and Dartium) now serve from a server and not from a file: url. (This plays better with loading resources using XHR and the browser security model). Analysis results now cached between sessions which leads to faster start-up. Finally, we fixed a number of issues including, an issue with lots of warnings related to final fields and a performance issue with the outline view.

For Dart Server side libraries we published instructions on building native C/C++ extensions for the standalone Dart VM, landed feature enhancements and bug fixing in the HTTP, File and Directory interfaces. Finally, we've introduced hardening of the APIs to deal gracefully with unexpected arguments.

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…