Skip to main content

Dart Team's Weekly Digest


Posted by Anders Sandholm

Quick update on what happened in Dart-land this week.

  • Dart language specification revisions for version 0.08 are ongoing: cascades, lazy init, liberalized string constants, relaxed compile-time errors.
  • In the Dart VM, the new compiler infrastructure now compiles about half of the methods in frog and we have better support for source breakpoints. We implemented Dart C API for weak reference sets (aka object grouping) and automatic concatenation of string literals. Finally, we have better resolution of URIs in the dart standalone binary.
  • In the Dart to JavaScript Compiler, we started to support constructs that introduce complicated control flow (break, continue) in the new optimizing backend. Moreover, the first samples that use the new wrapperless dart:html library work when compiled with the optimizing backend.
  • The Dart Editor has a new Files view which replaces the old Libraries view. We also made a switch to perform analysis against Dart SDK runtime libraries and cleaned up wizards, welcome page, and UI to reflect switch to new Files view. The editor has improved launch configurations and analysis engine (DartC) and we modified "native" keyword analysis to support usage in Frog.
  • On the Dart UI front, we enabled wrapperless HTML which reduces size of swarm from 750K->450K. Also, utf libraries merged.
  • In dart:io, we landed extensions and bug fixes to the HTTP libraries and the initial native extension library support is well under way.
  • On dartlang.org, we have a new left navigation organization and published Bootstrap into Dart language (part one) and added an Exceptions section to the language tour.

Popular posts from this blog

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…

AngularDart 4

AngularDart v4 is now available. We've been busy since the release angular2 v3.1.0 in May. Not only did we "drop the 2", but we also improved the compiler and tightened up the framework to give you smaller code, we updated the package structure to improve usability, and we added several new features. Check out the updated documentation to get started.
Just angular Upgrading to v4 will require more than updating your version constraint. The package has changed names (back) to angular – dropping the 2. You'll need to update your pubspec.yaml and the corresponding imports in your code. In most instances, find-and-replace should do the trick. Going forward, the package will be called package:angular. We'll just update the version number.
Smaller code The updated compiler in 4.0 allows type-based optimizations that not only improve runtime performance but generate better code because we are able to strongly type templates. A big result of the update is that many ap…