Google Dart & XAML
A few things that I find intriguing:
- C style syntax : Google consciously don't try to invent new syntax and stick to the syntax that most dev already familiar with.
- Optional static typing : specifying a type against parameter or variables are optional and mainly for development time checking (intellisense & warnings). On ‘production mode’, Dart doesn't enforce it.
- Dart is designed for dev to work with an ‘offline first’ approach. The server component will be simple REST component like WCF Data Services, Web API, or NodeJS type of service (which to note; all the above will run on Azure)
- View engines work very similarly to XAML. Google is still brewing the view engine and seems to borrow a lot of the concept from XAML & its view model binding capabilities.
- Just like CoffeeScript : using Dart would mean that we as the developer will need to debug on code that the framework generates. There's no correlation engine as yet between the source code and generated code.