The dead live longer: 5 arguments for the success of Dart
Google associate Filip Hracek has recently moved to the Dart Development Team. A move which provoked not only rather amicably intended comments (for example that by doing so he will hopefully not be riding a dead horse), but also clearly negative reactions. Yet he provides good reasons which in his opinion speak for the success of Google’s web language.
- Google places much emphasis on Dart
A company’s lack of trust in a project or product is never a good sign. In this regard at least, you do not need to worry about Dart, according to Hracek. He states that every day enormous volumes of Dart code are being written which are all key to the company’s success. The product team which is responsible for most of Google’s sales uses Dart. In other words: Even if only Google were to use Dart, the survival of the language is guaranteed in the long run.
- Dart is actively maintained
Although with Version 1.13, Dart has reached a fairly stable stage, Hracek claims that development is proceeding at a notorious pace; currently, there 139 active repositories on GitHub, in December 2015 alone there were hundreds of commits:
Excluding merges, 32 authors have pushed 408 commits to master and 412 commits to all branches. On master, 828 files have changed and there have been 93,059 additions and 88,236 deletions.
Compared to similar projects, Dart is in good shape. Even if quantity does not necessarily mean quality, the large investments which flow into the development of the language show it.
- Dart will soon run everywhere
See also: Dart 1.9: Asynchronous programming ahoy
- Dart is stable and steady
For those who are weary of constant changes in tools and libraries, Dart could be an uncommon haven of peace: indeed, the language is being constantly developed, however projects up to two years old still use the same standard library, the same language features, as well as the same package and dependency manager. In addition, a large part of the community follows the official style, use and design guides – legibility of the code is evidently top priority.
- Dart “feels right”
Hracek does admit that Dart is not everybody’s cup of tea. However, there are a number of circumstances which ensure that work with Dart subjectively “feels right.” So especially if you are familiar with C#, C, ActionScript, Java and others, syntactically you will feel quite at home with Dart. Moreover, you wouldn’t expect any nasty surprises from a semantic point of view, the standard library is well thought out, standard features like Async/Await, String interpolation, etc. are a cinch to use and thanks to optional types, as well as optional generics, libraries, packages and transformers, the easy creation of robust code is possible.