Skip to main content

Dart Team Updates and Notes

Posted by Seth Ladd


Summary

  • Summer vacations are wrapping up, back to work! The Dart project ramps up for the M1 release, which delivers a more stable language and implementations.

Details

Dart language specification:

  • Version 0.11 is almost ready - this is pretty much the M1 version.
  • Mixin proposal to be published.

Dart libraries [core, unittest, i18n, etc]:
  • Ability to make temporal assertions with the mocking library
  • Work in progress on sharing the source for the dart: library implementations across VM and dart2js.

Dart VM:
  • New language features implemented: “non-constant initializers for fields” (bug 3848), “static methods are compile-time constants” (bug 3406), “operator syntax” (bug 3767), “getter syntax” (bug 3608), “on-catch support” (bug 3757).
  • Switched to using SSA-based optimizing compiler both on ia32 and x64.
  • Using type propagation to eliminate assignability checks to improve checked mode speed.
  • Added support for external and patch to enable shared core library sources.
  • 20% decrease in initial heap size for new isolates.

Dart to JavaScript Compiler:
  • Improved noSuchMethod handling to limit the explosion in code size that used to arise from using the feature anywhere in the code base.
  • Started propagating type information through parameters to generate smaller and faster output.
  • Introduced basic framework for providing type information to the compiler backend, which will be used to experiment with global concrete type inferencing.

  • Added primitive support for external and patch to enable shared core library sources.

dart2dart:
  • Close to be able to bundle the whole dart2js into a monolithic Dart file

Dart Editor:
  • An initial implementation of a 'Create Method' quick fix. This will create a method definition to satisfy a reference to a non-existent method. You can access this functionality through the ctrl/command-1 keystroke; currently only top-level functions are supported.
  • Several analysis fixes and various updates to our analysis code for M1 language support.
  • We now include optional parameters in completion proposals.
  • There is a new Breakpoints view to view your debugger breakpoints.
  • Enhanced ‘Open Folder...’ to better support opening very large applications.
  • Fixes to the Apps view and enhancements to our Welcome page.

Dart UI [dart:html, web components]:

Dart SDK and build:
  • /lib being split into /lib and /pkg well underway.

Pub:
  • Read-only site for pub.dartlang.org (not live yet).
  • Support for installing packages from a package hosting site (like pub.dartlang.org when it’s up).
  • Windows support for Pub is coming along.
  • New documentation with more coming.

Dart Server [dart:io, etc.]:
  • Work in progress on HTTPS support.

Dart Dev Rel:
  • Auto-publish API docs on successful build.
  • Added a page on Dart books
  • More episodes of Dartisans

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…