Skip to main content

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 very deep view hierarchies (65ms versus 128ms in October).
  • For AngularDart Components, we see major improvements in performance. For example, the <material-button> component gets initialized 1.5x faster (0.5ms versus 0.7ms in October).


Generated code size:
  • For a small app (GWT Mail sample app), we see
    • 3% reduction since October (2.0)
    • 24% reduction since August (when AngularDart went all Dart)
  • For large apps, we see
    • 13% reduction since October
    • 29% reduction since August


Developer experience:
  • Simplified API
    • Simpler onPush change detection using ComponentState and setState.
    • Only one load method (instead of loadAsRoot, loadAsRootIntoNode).
    • Got rid of TitleService, use idomatic document.title instead.
    • Removed viewBindings (use viewProviders).
    • ngSwitchCase replaces the soft deprecated ngSwitchWhen.
    • XHR is deprecated.
    • EventEmitter is deprecated: use the idiomatic Stream and StreamController instead.
    • Removed IterableDifferFactory.
    • A name parameter is now required for all @Pipe(...) definitions: @Pipe(name: 'uppercase') is replaced by @Pipe('uppercase').
    • null is no longer propagated as an initial change value. Fields must start with a non-null value.
    • Removed NgPlural; use the much more dart-y package:intl instead.
  • Catching bugs earlier
    • selector is now a @required property.
    • ngIf throws if the bound value changes during change detection.
    • In generated .template.dart change detected primitives are typed.
  • Testing
    • package:angular_test with improved NgTestBed.
  • Dev mode tweaks
    • New isDebugMode function.
    • Warning when Dartium is run without checked mode.
    • By default, the ExceptionHandler is a BrowserExceptionHandler which prints to console. You can override it if you don't want this behavior (for example, when releasing to production).
You can find more information in the changelog.

AngularDart 3.0 is production ready, and already used at Google by very large apps like AdWords and AdSense. Upgrade today to make your apps smaller, faster, and more reliable!

Popular posts from this blog

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…

The new AdWords UI uses Dart — we asked why

Google just announced a re-designed AdWords experience. In case you’re not familiar with AdWords: businesses use it to advertise on google.com and partner websites. Advertising makes up majority of Google’s revenue, so when Google decides to completely redo the customer-facing front end to it, it’s a big deal. The Dart team is proud to say that this new front end is built with Dart and Angular 2. Whenever you asked us whether Google is ‘even using Dart for anything,’ this is what we had in mind but couldn’t say aloud. Until now. We asked Joshy Joseph, the primary technical lead on the project, some questions. Joshy is focusing on things like infrastructure, application latency and development velocity, so he’s the right person to ask about Dart.Q: What exactly did we launch on Monday?It’s a complete redesign of the AdWords customer experience that is rolling out slowly as a test to a small initial set of advertisers. The most noticeable thing is probably the Material Design look and f…

Const, Static, Final, Oh my!

Posted by Seth Ladd

(This is an "oldie but a goodie" misc@dartlang.org post originally written by Bob Nystrom. It is being posted here as the explanations still ring true.)

Bob writes:


"static", "final", and "const" mean entirely distinct things in Dart:

"static" means a member is available on the class itself instead of on instances of the class. That's all it means, and it isn't used for anything else. static modifies *members*.

"final" means single-assignment: a final variable or field *must* have an initializer. Once assigned a value, a final variable's value cannot be changed. final modifies *variables*.

"const" has a meaning that's a bit more complex and subtle in Dart. const modifies *values*. You can use it when creating collections, like const [1, 2, 3], and when constructing objects (instead of new) like const Point(2, 3). Here, const means that the object's entire deep state can be determ…