How about coming back in a year and telling us how it turned out instead? Actual case-studies and analysis are interesting, fashion statements are not.
1. It lets developers familiar/interested in the tech to know that you use it and that they should apply there.
2. You've done the work to research it and make the decision to switch - it doesn't hurt share that. Who knows someone may point out some flaws you didn't expect.
3. It increases the inertia of the technology. There are strong network effects in technology and if everyone sees that something is growing they'll make the jump too. One new library created per X developers is a big win and makes it better.
We'll definitely keep you posted on our journey with Dart. I don't have specific announcements yet but we're looking forward to share code examples and open source a few web components going forward.
So far Dart really has been a pleasure to work with and we'll definitely blog more about it in the future and hopefully also go a bit more into detail.
The main motivation behind this blog post came from people asking us about how it was to work with Dart and why we chose to adopt it.
I can see how this might come across as a fashion statement but I just wanted to share my thoughts and have a url to point people to :)