I ran the angular gwt example using mvn gwt:run-codeserver, first thing I noticed: @Components needs to be annotated with @JsType as well, properties needs to be annotated with @JsProperty, constructurs needs to be annotated with @JsConstructor, methods with @JsMethod, ... besides getters and seters, that's a lot of extra boilerplate don't you think? Apparantly my browser is too old for Angular GWT to run (I'm busy on a CentOS box), so I'll have to try it some other time on my MacBook, the annotation boilerplate already put me off though.

Dart Strong Mode when GWT has stronger type checking out of the box,

Dart already has Strong Mode, it's just being improved. The benefit of Dart here over GWT is that types are optional, I don't have to be bogged down by writing types everywhere. The benefit being that I can move a lot faster, get things done and then have types added later on if I really need to. This is one benefit of Kotlin as well, inferred types, in Java you still need to write out the types everywhere.

Tell me which one is less code to write:

Java8:

String value = Optional.ofNullable(somemethodThatCanReturnNull()).orElse("value");

Kotlin:

var value = somemethodThatCanReturnNull() ?: "value"

or if you really want to, but the above one infers the type, so this is not needed:

var value:String = somemethodThatCanReturnNull() ?: "value"

Dart:

var value = somemethodThatCanReturnNull() ?? "value";

or

String value = somemethodThatCanReturnNull() ?? "value";

And I can cite many more examples where Kotlin and Dart are simply less code to write to get the same thing working. For UI development, this is crucial. Most of the UI doesn't even require strong typing, server-side I fully agree with strong typing, but does it really make sense in the UI when most of your inputs will probably be Strings ?

fast edit refresh when GWT has great SuperDevMode,

Dart has a special Dartium browser which gives me exactly this (instant refreshes, although only on chrome) as well as Observatory which gives me deep insights into memory consumption, I can track object creation to make sure I don't have leaks, set breakpoints in the browser, etc. Development is done in Dartium, only then I test in IE, Firefox, Safari, etc, but even when I do test it in browsers outside Dartium, it's generally fast enough after the pub server warmed up. So "super-dev mode", although a useful feature, it's not something that's missed by myself; I've generally tested other browsers on the QA server already compiled to JS and had no issues with the generated JS before.

and also would like to have better js interop what GWT has.

In the places where I've experimented with JS-interop, it was working just fine in Dart, JS-interop is generally not something I use.

From your blog:

Ongoing work on Flutter for Dart; if about GWT we can use already Cordova, Phonegap, Appcelerator Titanium (via Titanium4J), ...

Dart is also available with Cordova and Phonegap, you also get DartGap which wraps Cordova and then there's Flutter to look forward to which will blow Cordova and Phonegap out of the water when you all of a sudden have native-like Andriod / iOS support via Dart.

Get me KotlinGWT with everything JavaGWT currently has and you have my attention (the direction Kotlin is going with WASM support, I'd probably stick to Dart or use Kotlin when WASM becomes reliable), Optional Types and Inferred Types are what I'm after in UI development (and on the server as well since I switched to Kotlin), Strongly Typed and boilerplate slows me down.

If you're preferring Angular2 TypeScript over Angular2 Dart, chances are you haven't used Dart yourself.

The latest of my evaluation applications uses Dart for the BE as well, not just for the FE. It was surprisingly simple to get working together with Angular2 FE. Code sharing between the 2 is also a nice addition.

I will definitely consider a Dart BE for the next production application I work on.

Thanks Daniel, I will let you know, since I will try both FE and BE and Angular2 ...

I'm not using Dart in the backend - main reason is that it doesn't cover all my needs at the moment. Although you can have a look at Dart's Redstone micro framework which should be sufficient for most people. I'm currently using Kotlin + Spring since the existing infrastructure is all Java8 + Spring based. Frontend I've been churning out 1000s of lines of Dart code in the last two weeks all Angular2, nearly halfway finished with a project that I just started.

Hi, I saw you on Slack last night :-) As Günter mentioned, i18n support should be ready soon, also looking forward to it!

Hello Vlad, another approach would be not to localize your website on code level but rather translate it with a translation proxy solution. Easyling is a very well known one - guess what language was chosen for it's front-end ;)

Very little to no extra coding is required to get a translated website up and running with it. Sign up for a demo, they'd be happy to show you around!

Looking forward :-D

I avoid using mirrors at all cost, as soon as I use mirrors, the generated JS explodes in size. The @MirrorsUsed seems to help with this though. Dart feels like a mixture between Java and JavaScript, so quick to pick up by most developers. Pub is also great, no need for Jrebel or SpringLoaded when using Dart; just refresh the browser and it's there immediately - just like JavaScript, no latency or waiting period before you can refresh the page.

The reflectable package provides much better support to define what needs to kept available for reflective access than @MirrorsUsed() from dart:mirrors to not hurt tree-shaking more than necessary. It generates code from reflective access and reflective access isn't used anymore after dart2js.

That's not really correct. GWT 2.8 supports Java8 syntax that means you can leverage lambdas which make async code even more concise than the ES6 version.

I write code in Java8 daily, it's certainly an improvement over Java6 and Java7, but it's still very clunky loaded with boilerplate once you've started working in other languages, hence the reason I recently made the switch to Kotlin, all the Java8 benefits minus the boilerplate.

Furthermore SuperDevMode is really very fast.

This was not my experience unfortunately, maybe I had to give it some more RAM via Xmx params or add some special startup params, the old GWT was heavy on RAM if my memory serves me correctly and running my CPU into the ceiling. I was looking for out-of-the-box experience though, not having to tune / tweak anything.

 that currently even easier to use than the Dart's JsInterop

Yes, the GWT-JS interop is much more mature than Dart's JS-interop, but in this project this was not something that interested me much as I was looking for a pure implementation in one language.

 Also GWT is used for Google Inbox, Google Spreadsheet and used to write business code once in java and use it in iOS, Android and the Web. 

I'm aware of this, AWS is using it as well, but I could argue that it's being used because that's what it was written in originally. Google didn't rewrite AdWords in GWT, in fact, they moved away from GWT to Dart to be able to move quicker, Google Cloud's new dashboard is also in Angular if I'm not mistaken (not sure if it's using Dart though). I had several projects in GWT myself, awesome tech for its time when browsers were super incompatible and JS was super broken. JS got a lot better now, browsers became a lot better, transpilers no longer need to compile a separate JS file per browser, some minor polyfills are enough to get it cross-browser compatible these days.

  and used to write business code once in java and use it in iOS, Android and the Web

This is currently an advantage if this is your business requirements, Flutter in Dart would obviously give me these same benefits in the future, currently my business requirements are met using Cordova / PhoneGap which works good enough with Dart for my requirements until Flutter eventually makes it debut.

   Google is also working on GWT 3.0 which will be a pure Java to ES6 transpiler and reduce the compiler complexity a lot

Is Google writing any new projects in GWT ? The reason it needs maintenance by Google is since Google has huge products still using it. I stand corrected about the maintenance, there was a time when things slowed down considerably after the handover to the steering committee a few years ago, it has indeed picked up again.

Also looking at jobs in GWT, Indeed gave me about 600 results, Angular gave me about 12000 results and retraining somebody who already knows Angular TypeScript / JavaScript into using Angular Dart would be considerably easier than getting somebody started in GWT. Based on the decline on in available jobs in GWT, it's probably fair to make the argument that GWT's usebase shrunk a lot.

If I had to choose a piece of tech for a Java heavy shop, it would be tight between TeaVM and GWT, KotlinJS would be another option (if it's a long-term project that doesn't need to have perfect JS immediately) or even Kotlin with TeaVM. If I could compile Kotlin to GWT, maybe the appeal would be more, I haven't tested if Kotlin could be compiled with GWT superDev compiler.

Thanks for the comment :-)

I've worked with both Ember.js and ExtJS / Sencha on front-end projects with close to 100k lines of JavaScript code several years ago. JavaScript was the problem in both (developer written JS), stuff would sometimes work in one browser and not 100% in another browser (minor things, but in the corporate world, minor errors could cost you your contract),

Less files we had to manually build a build script for, we had issues where we had to tweak our code to make minification work (In Dart that's taken care of for you). We had over 5000 selenium tests running over and over the whole day and javascript errors which could have been avoided with a stricter type system went unnoticed often.

The components are nice, if you can replace the JavaScript with Dart, it'll be an excellent choice.

querySelector is a good example, it's only partially supported in some browsers (partial support in IE8 and buggy on IOS) - if I use it in JavaScript, chances are that it might work in some browsers and might break in another browser - I now need to go check which JS APIs I can use and can't use based on the browsers I want to support (painful)

Use querySelector in Dart and it'll work across all browsers that Dart says is supported, if not you file a bug and Google fixes it.