Why I’m joining the Dart team, of all places

The author explains why he transferred to the Dart team and why he expects Dart to succeed. He argues from Google’s internal adoption, the amount of maintenance work, the language’s planned reach across platforms, and the experience of using it.

Reading notes

#

• He says many people were surprised by his move, but he trusts Dart enough to bet his career on it.
• Dart is used heavily inside Google, including mission-critical code tied to major revenue.
• The language is on a special code review path at Google.
• The Dart GitHub organization has many maintained repositories.
• He points to recent commit activity in the core SDK as evidence of sustained work.
• He says commit volume does not prove quality by itself, but it does show investment and improvement.
• He names experienced Google engineers and other well-known contributors as part of the team.
• He says Dart was designed as a general-purpose language and is meant to run on the web, servers, micro-processors, micro-controllers, Android, and iOS.
• He says Dart is stable and consistent, with projects able to keep using the same standard library, language features, and package manager over time.
• He says the community values readability and follows official style, usage, and design guides.
• He says programming in Dart feels right to him and that many smart developers like it.
• He describes Dart as familiar, unsurprising, and flexible enough to support robust code while staying out of the way.