Now officially known as “ECMA-408,” the first edition of the Dart standard — Dart 1.3 — is available as a PDF download from Ecma’s website. But Ecma’s stamp of approval won’t amount to much without larger and more compelling reasons for the language to be broadly adopted.
When InfoQ asked Google Dart project lead Anders Sandholm what the standardization, he replied, ” … there is an open process for the onward evolution of Dart and that anyone can become an Ecma member, join TC52, and have a direct impact on Dart’s future development.”
This evolution of the language through its standard, rather than merely the source code for one of its implementations, speaks to Google’s need for other people to build on it as a fixed base. This stands in contrast to what could be called the “GitHub way,” where users can fork and change the project rather than standing in line. The source code for Dart is freely available, so it stands to reason some of those truly interested in evolving Dart might well fork it.
The single biggest obstacle for Dart remains the general indifference of developers to the language, despite Google’s continued investment. If anything, Google’s Go language i’s finding more traction because it addresses problems developers are trying to solve (such as parallelism and concurrency across multiple machines). If ratifying Dart as a standard is meant to spread the language via adoption by browser makers apart from Google, it’s an idea that seems a long way from paying off.