On Dart core libraries we've introduced a library fork in experimental/lib_v2. Discussions and prototypes on Streams (called “Observable” in C#). Started work on refactoring the collections library. (Almost) removed library core_impl. noSuchMethod now takes an InvocationMirror.
In the dart:io library, we've implemented HTTP session and HTTP basic authentication support. We fixed bugs in the HTTP library and fixed a bug that caused Pub to fail (because of accessing files open in other processes on Windows). We're also working on improving IO performance and started landing HTTPS support.
For dart:html, we now have implementations and interfaces merged, dart:svg is split from dart:html and there's new support for keycodes.
In the Dart VM, the GC is now collecting unreferenced compiled code to avoid running out of code heap. The compiler now has bounds check elimination for some array accesses and we're doing investigations into better mega-morphic call site dispatch and landed first handling of related excessive de-optimizations. In the runtime, we've changed internal string representation to be UTF-16 in accordance to the updated language specification. Finally, we've worked on stability and bug fixes.
In the Dart Editor there's a new auto-recovery feature: The content of open editors is remembered and restored if a crash occurs. The Editor now uses the dart2js snapshot in the SDK. Compile times for the clock sample went from 9.8 seconds to 4.6 seconds. Saves in the editor are significantly faster. Times for our test file for saves went from 900ms to 30ms. The editor reports errors for using deprecated #library #import #source directives. It also resolves and refactor-renames [id] and [new id] references in documentation comments. Quick Fix to create missing “part” file.
On Pub, we've fixed bugs and improved error messages, created an HTTP package, added curl (for HTTPS) and multipart MIME support to HTTP package and uploaded lots of packages!
On Dart Web Components, we added ability to compose web components out of other components, the spec is in progress and we continued to fix many bugs from use community.
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).
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