Skip to main content

Dart 1.2 continues to improve developer experience

With the 1.2 release, the Dart team continues its commitment to regular, compatible updates to our core runtime and tools. This release includes improved debugging, faster networking, and Angular support in the Editor.

Debugging Dart applications is now easier. Breakpoints can now be set at local variable assignments. A number of bugs have also been addressed, including stepping through recursive functions and eliminating side effects of using the debugger.

The Dart core libraries continue to improve with a focus on performance. WebSocket throughput has increased by a factor of 15 since version 1.0. The speed of our core async primitives, Future and Stream, also improved by over 10%.



Angular support in the Editor has been greatly improved in this release. Search, navigation, and refactoring now understand Angular elements. A number of Angular-specific warnings have also been added.

Please see the Release Notes for a description of all changes. Dart 1.2 includes bug fixes, performance improvements, and enhancements across the Dart virtual machine, compiler, libraries and tools.

You can download v1.2 at the Download Dart page. If you are running the Dart Editor, you can update by checking "About Dart Editor" in the IDE.

Tell us what you build with Dart in our Google+ community and let us know if you have any issues or feature requests.

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 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 …