On Monday, 16 November 2015 18:52:50 UTC, Jens wrote:
>
>
> I'm not talking about a re-write here, I'm talking about new projects. For
>> new projects, I can't see a compelling reason for picking GWT, if the devs
>> are going to have to understand JS to use GWT then it is better to invest
>>
On Monday, 16 November 2015 12:34:51 UTC, Thomas Broyer wrote:
>
>
>
> On Monday, November 16, 2015 at 11:29:14 AM UTC+1, Robert Stone wrote:
>>
>>
>>
>> On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote:
>>>
>>>
>>&
On Monday, 16 November 2015 12:51:35 UTC, Thomas Broyer wrote:
>
>
>
> On Monday, November 16, 2015 at 1:28:16 PM UTC+1, stuckagain wrote:
>>
>> Thanks for all the feedback. But it does not put my mind at rest right
>> now.
>>
>> It would have been much better if GWT 2.8 would have provided
On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote:
>
>
> My worry about "just pick a mainstream JS framework and use it via
> JSInterop" is that if you're a) coupled to a JS environment for unit
> testing and b) interfacing with a framework that is inherently
> dynamic/untyped,
