Skip to main content

Rename refactoring improvements with new Dart Editor build

Posted by Dan Rubel

New Dart Editor build available. Highlights from build 6943 include
  • better management of console view
  • allow multiple consoles to be visible for multiple running applications
  • rename refactoring improvements and bug fixes
  • cleanup launch configurations of removed/deleted applications
  • analysis support for same prefix for multiple imports
  • JavaScript compiler and Dartium improvements
  • UI and analysis improvements and bug fixes

Read the full change log or start with the Dart Editor tutorial.

Thanks in advance for your feedback!


  1. Based on reading Dart updates at this website, I think too much effort is going into the Dart IDE and not enough into the language itself. If Google builds a solid language, Eclipse, IntelliJ, etc will make good IDEs to develop with.

    After the language itself is solid and appealing, the next areas Google should focus on are marketing and browser compatibility. Google is famous for terrible marketing of good ideas (Google Checkout comes to mind). Dart also needs to be heavily marketed to web and Java/C#/PHP developers who dislike JavaScript.

    Dart needs to run natively in Chrome and Firefox. Being easy to run Dart natively in these two browsers, which represent ~50% of all users, will encourage developers to try the language.

    Once developers see that great apps are easier to create and maintain in Dart than in JavaScript, Dart will start to achieve critical mass of community support needed to pressure other browser makes to support native Dart too.

    Success in marketing and cross browser native Dart will make Dart a legitimate alternative to JavaScript. These areas need Google's efforts more than making a customized version of Eclipse for Dart.


Post a Comment

Popular posts from this blog

Const, Static, Final, Oh my!

Posted by Seth Ladd

(This is an "oldie but a goodie" 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…

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

Dart 1.12 Released, with Null-Aware Operators and more

Dart 1.12.0 is now released! It contains the new null-aware operators language feature, and enhancements to pub, Observatory, dartdoc, and much more.

Null-aware operators

The new null-aware operators help you reduce the amount of code required to work with references that are potentially null. This feature is a collection of syntactic sugar for traversing (potentially null) object calls, conditionally setting a variable, and evaluating two (potentially null) expressions.

Click or tap the red Run button below to see them in action.


  if null operator. `expr1 ?? expr2` evaluates to `expr1` if not `null`, otherwise `expr2`.


  null-aware assignment. `v ??= expr` causes `v` to be assigned `expr` only if `v` is `null`.


  null-aware access. `x?.p` evaluates to `x.p` if `x` is not `null`, otherwise evaluates to `null`.


  null-aware method invocation. `x?.m()` invokes `m` only if `x` is not `null`.

Learn more about Dart's null-aware operators in our Language Tour.

.packages fi…