Skip to main content

Dart Team's Weekly Digest

Posted by Anders Sandholm

Quick update on what happened in Dart-land this week.
  • Dartium binary available. See hang-out video, blog posts and the new Dartium page for more info. On dartlang.org, we also added a Resources page and Seth had the first blog post on classes in Dart.
  • Coming soon: Adjacent string literals will be concatenated: ‘dog’ ‘house’ == ‘doghouse’. String + operator is on its way out.
  • Promise is removed, use Future.
  • toString on collections will soon return their contents and deal with recursive refs intelligently.
  • The VM now recognizes dart:json, dart:uri and dart:utf8.
  • In the Dart to JavaScript Compiler, the SSA-based backend is now capable of dealing with many parts of corelib and we took the first steps towards wrapperless HTML and DOM libraries in the optimizing backend. Moreover, we fixed compiled JavaScript to run on browsers without Function.prototype.bind (Safari).
  • The Dart Editor continuous build bundles SDK and Dartium (except on Windows - no Dartium yet). The editor now launches Dartium by default, only compiles to JS if necessary on launch. It also had a few performance improvements and fixes and the new Welcome Page provides quick & easy access to samples.

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).

AngularDart is going all Dart

Until now, the multiple language flavors of Angular 2 were written as TypeScript source, and then automatically compiled to both JavaScript and Dart. We're happy to announce that we’re splitting the Angular 2 codebase into two flavors – a Dart version and a TypeScript/JavaScript version – and creating a dedicated AngularDart team. This is amazing news for Dart developers because: The framework will feel more like idiomatic Dart. It will make use of Dart features that couldn't work with the TypeScript flavor. It will be faster. This is equally great news for our TypeScript and JavaScript developers, by the way. Cleaner API, performance gains, easier contributions. Read more on the Angular blog. Angular 2 for Dart is used by many teams at Google. Most famously by the AdWords team, but many other Google teams build large, mobile-friendly web apps. Some of the top requests from these teams were: make the API feel like Dart, provide a faster edit-refresh cycle, and

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