Skip to main content

Core libraries stabilize with Dart's new M4 release

Today, we are releasing Dart SDK Milestone 4 (v0.4.7 r21548), available for immediate download. The highlights are:
  • Corecollection, and async libraries are now stable. There will be no more breaking changes to these libraries.1
  • Performance improved in both the dart2js compiler and the Dart VM. 
  • Dart Editor comes with an all-new analysis engine for faster real-time feedback. 
  • Classes can be used as mixins. 
dart2js now generates more efficient code. Compared to the previous M3 release, DeltaBlue runs twice as fast and Richards runs 40% faster. The native Dart VM now runs Richards twice as fast as V8. On DeltaBlue, the VM improved by 22%. Details are available at dartlang.org/performance.




Dart Editor comes with an all-new analysis engine for faster real-time feedback, code completion, refactoring, and more. For example, analyzing the content of a folder is now more than 50% faster. We also improved the Dart plugin for Sublime with syntax highlighting, common Dart snippets, and dart2js and Pub integration.

On the language front, Dart now has a first implementation of mixins for sharing code between unrelated classes. For example, the core libraries use mixins for List and Iterable.

We’re thrilled to see new and exciting uses of Dart, such as Glyph3D and the API for interacting with Glass. We thank you for your patience as we worked through the breaking library changes, and we can't wait to see what you build with our improved, more stable platform. We invite you to download Dart, and we look forward to your feedback.

1 Except for the class Invoke, which will change slightly to accommodate efficient minification.

Posted by Lars Bak, Chief Dart Officer

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…