GWT vs. Dart - what are the main differences? Is Dart a potential replacement for GWT?

Question

I'm trying to figure out which of the two to use, having four basic criteria

• Writer is better, supported client JavaScript code, with the ease of a modern IDE (better content support, better debugging).
• Cross browser
• Less lock, code can be read
• Technology that is likely to be supported in the future (hardest to say)

What are the main differences between the two technologies?

Both seem to have similar use cases and the same potential developer community

Will it look like the GWT will eventually be replaced by Darth? Any signs offering this?

Or am I missing something, and they are completely different concepts?

Answer 1

I think the main goal of Dart is not to replace the original compilers with JavaScript like GWT, but to replace JavaScript itself. This needs to be done for the huge supported base codes, as well as to improve performance and many other reasons that I think of.

It is more strongly typed and borrowed many concepts from Java and other languages.

As for predicting the future, you can see how Dart does against JavaScript in Google Trends.

Answer 2

I think I found this: (should have read the Dart FAQ first, not googling "GWT vs Dart")

From: http://www.dartlang.org/support/faq.html#future-for-GWT

Q. What is the future for GWT?

Bruce Johnson posted on the GWT blog (with additional comments for Plus): “Darth and GWT both share the goal of creating a structured network of programming. In fact, many of the same engineers who brought you the GWT work on Darth. We see Darth as an ambitious evolution of the GWT mission to make web applications better for end users and we’re optimistic about its potential. When Dart develops and becomes ready for prime time, we expect to work closely with the GWT developer community to explore Dart. "

“Meanwhile, rest assured that GWT will continue to be a productive and reliable way to build the most ambitious web applications - and even games like Angry Birds. Key projects at Google rely on GWT every day and we plan to continue to improve (and open-sourcing) GWT based on their real needs. "

Answer 3

Dart basically exists to solve two problems

• Provide a client-side language that allows developers to create large applications without the pain typically associated with large javascript applications.
• Use the client language and the server in the same language (i.e., the Dart SDK will ultimately be similar to NodeJS).

Thus, it solves the same problem: GWT (bridging the gap between the client and server), and some of the problems solved by CoffeeScript (a modern language suitable for large-scale development).

Dart, we hope, will do a better job of bridging the gap between the client and server than GWT, since it was designed from the very beginning to compile it into JavaScript, thereby solving the main problem with GWT-RPC (i.e., GWT-RPC can only serialize a tiny subset of Java, Dart does not have this problem).

Whether it will be better than CoffeScript is another discussion, but now its improved debugging capabilities (i.e., launching it directly inside Chrome) proves a big plus for developing large-scale web applications (for example, GWT does this using its dev mode) ,

Answer 4

Dart, we hope, will do a better job of bridging the gap between client and server than GWT, as it was created from the very beginning to compile its JavaScript, thus solving the main problem with GWT-RPC (i.e. GWT-RPC can only serialize a tiny subset of Java, Dart does not have this problem).

I have never seen or encountered this problem. You can easily serialize all types and most data structures in java.util. *. What else do you need or need.