Skip to content

Instantly share code, notes, and snippets.

@vsavkin

vsavkin/on_dart

Last active August 29, 2015 13:57
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save vsavkin/9884641 to your computer and use it in GitHub Desktop.
Save vsavkin/9884641 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
on_dart
The author has a few good points, but I think he doen't see the whole picture.
1. Even if the DartVM is not deployed to any other browser, there is still a lot of value in having it:
* The VM can be used on the server side.
* The VM can be used to speed up development process (no compilation).
* Just the fact that it can be shipped with the mobile Chrome, I think, is a big deal.
2. I would not compare the Dart/JS interop with the COM interop. It is closer to the Java/Scala interop or to the JRuby/Java interop. It is not completely seamless, but not too bad.
3. Optional/gradual types are often criticed because they do not provide certain guarantees. But it is actually a great thing! Gilad Bracha gave a great presentation a few years ago, where he talks about the benefits of optional types (the section on optional types is somewhere in the middle of the talk):
http://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2012/Dart-A-Well-Structured-Web-Programming-Language
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment