This time I'll bite...

J2CL has been - what? - two to three years in the making - yet, there is 
nothing released to the public yet (aside from a preview to a few blessed 
individuals).

Before someone follows up again with the usual matra that "it is not 
production ready yet and it will do more harm than good" or "somebody is 
porting the GWT widgets to J2CL as without these J2CL would be unusable" 
let's ask ourselves: *are these statements holding any ground anymore*?

Here's a situation which is very likely not typical to just us: 
We have to - like NOW - start replacing - in our app - all the dying GWT 
widget-set/RPC legacy with a maintained and more contemporary toolkit 
(React, Angular2, whatever).

(And please let's not argue over whether the GWT widget-set is still an 
option for any new development. For us it is not. Also let's not argue if 
coding against JavaScript libs with the existing GWT compiler toolchain is 
a viable option in the long term - it is obviously not.)

The question: shall we scrap GWT altogether and rewrite in JS/TS? Or shall 
we continue with Java/JSInterop?

Now, please enlighten me how we can defend the option of continuing in 
Java/JSInterop - even in front of ourselves - given that 3 years from the 
initial announcement - J2CL is still just smoke and mirrors for almost all 
Google outsiders?  We can't play with it to gain some confidence that it 
will work for us.. Also what happens if Google changes their mind and 
decides not to release it - say - due to legal issues? We would be stuck 
with an all-new Java/JSInterop code still bound to the dying compiler 
toolchain of GWT. Not a situation anybody wants to end up with, I guess...


-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/b99a4589-68f8-47f0-a414-80468bb90d5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to