Skip to main content

The present and future of editors and IDEs for Dart

When we started the Dart project in 2011, we challenged ourselves to deliver a structured and lightweight language that can be supported with productive editors and tools. To bootstrap the tooling ecosystem for Dart, we built Dart Editor to explore how to make Dart developers productive with code completion, source navigation, and static analysis.

Today, there are more editing and IDE options for a Dart developer than ever before. Developers are using a range of command-line tools, text editors, and full IDEs that support Dart. In what comes as no surprise, we've found that developers have very strong affinities to their particular editors, and that one size does not fit all. We've also learned that many developers are outgrowing Dart Editor, as they require source control support, plugins, extended customizability, and more.

To that end, we've shifted our strategy from focusing on a single Java-based editor, to focusing on low-level tools, the Dart Analysis Server, and plugins for editors. We are retiring Dart Editor at the Dart 1.11 release. WebStorm is the preferred IDE experience for Dart, and the Eclipse plugin for Dart will continue to be supported.

WebStorm and IntelliJ are full-featured IDEs, and both ship with the Dart plugin. The Dart plugin uses the Dart Analysis Server for its errors, warnings, quick fixes, and more. JetBrains editors have a robust plugin ecosystem, strong support for numerous languages and libraries, and are very customizable. Learn more about the various WebStorm editions and licenses, or download a WebStorm trial.

The Dart plugin for Sublime has strong community support, and is great for developers looking for a lightweight text editing experience for Dart. It now displays real-time errors and warnings from the Dart Analysis Server. It also supports numerous build commands (for dart2js, pub, etc.), syntax highlighting, and more.

We built DartPad for developers that want a friction-free introduction to the Dart language and libraries. DartPad, also based on the Dart Analysis Server, is perfect for dabbling in Dart, sharing snippets, answering Dart questions on StackOverflow, and exploring Dart APIs.

Another option is the Eclipse plugin for Dart, which we continue to support. The Eclipse plugin, which currently shares most of its code with Dart Editor, is powered by the Dart Analysis Server.

Server-side Dart developers can use Observatory for profiling, debugging, insights, and more. Observatory isn't an editor or IDE, but its real-time VM stats and debugger are a great complement to your editor.

The tooling ecosystem for Dart has come a long way. Stay productive!

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

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…