On Tuesday, October 25, 2011 12:19:54 AM UTC+2, Tomasz Gawel wrote:
I still don't understand the need for dart.
Have a look at www.infoq.com/articles/google-dart
if it would be cross-compiled so where is the advantage over gwt? in
gwt we have the language that we allready know and tools that were
worked out over years.
if it will be incorporated into browser as virtual machine than just
why not to incorporate the jvm? licensing issues?
Dart is designed so as to be cross-compiled to JS, so there's no impedance mismatch. GWT has to do some really tricky things to compile Java to JS (for instance, in Java every object has a hashCode() method and this causes issues when people try to put DOM elements into maps: http://code.google.com/p/google-web-toolkit/issues/detail?id=4086; in Dart, there's a Hashable interface –implemented by very few objects–, and a Hashmap can only use Hashable-s as keys).
and another thing - javascript is extremely powerful scripting
language. (as far as it is used for scripting -> max 300 lines of code
it's flexibility is a real power. when comes to maintaining bigger
apps this flexibility occurs to be serious flaw, but it the place
where gwt enters the play.
as i look closer at DART i start to suspect that probably it is not to
replace javascript but to replace java (and so avoid dependence to
oracle)
but do they think they can provide something better than java which
gained its maturity over years?
Oh yeah, dependence to Oracle; not as if they're going to provide MySQL in AppEngine ;-)
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/QzT8_eAtEQQJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment