>
>
> No, Google is not converting all Java to JS to abandon Java, it's the
> exact opposite. Google needs to support 4 platforms with it's code
>
>
OK, that is almost calming.
> But the Gmail team is 12 years old, we have a vast codebase that includes
> a lot of JS...
>
That is fine. I
The source code of Elemental2 is now available on github:
https://github.com/google/elemental2
Please refer to the project README for more information about how to use it.
If you have any questions/issues, feel free to open a bug in the github
project.
Important note: Elemental2 is in beta state
On Fri, May 19, 2017 at 5:45 AM, Learner Evermore <
learner.everm...@gmail.com> wrote:
> So... If I read this correctly... Google has discovered that GWT is not
> good enough (is bad) to continue using it. It is creating a J2CL that
> produces readable code so that it can completely abandon its or
Is there a way I can access J2CL code? Not open source?
--
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 google-web-toolkit-contributors+unsubscr...@googlegr
>
>
> Google didn't have any incentive to release GWT 10 years ago, or to
> continue maintaining it in the open source. They've always been the main
> drivers and main contributors so they could have stopped sync'ing their
> internal repository to the outside work long ago; but they did just th
On Friday, May 19, 2017 at 2:45:37 PM UTC+2, Learner Evermore wrote:
>
> So... If I read this correctly... Google has discovered that GWT is not
> good enough (is bad) to continue using it. It is creating a J2CL that
> produces readable code so that it can completely abandon its original Java
My responses to specific points:
Removing JSNI, , generators... we ourselves were careful
enough to either never use some of these and/or to abstract and encapsulate
their use. However everyone here seems to take the perspective of "it is
just one product of one company that is affected". It is
So... If I read this correctly... Google has discovered that GWT is not
good enough (is bad) to continue using it. It is creating a J2CL that
produces readable code so that it can completely abandon its original Java
source and continue without it. The already slow involvement will turn into
no
On Thursday, May 18, 2017 at 9:37:58 PM UTC+2, Relja Pcela wrote:
>
> It would be really nice to see some new answers on this kind of questions
> from GWT contributors other than: "We don't know how GWT3 will look like in
> this moment but we know that J2CL will not include this and that" becau
Hi,
On Thursday, May 18, 2017 at 6:29:29 PM UTC+2, Learner Evermore wrote:
>
> Hi there!
>
> I am faced with having to re-think what we are doing in the company I work
> for with respect to GWT, existing and new projects and I am struggling, to
> say the least. We've been very much a GWT shop fo
On Friday, May 19, 2017 at 10:35:29 AM UTC+2, Relja Pcela wrote:
>
> Can somebody please tell us who are the members of gwt committee
>
That page is *almost* up-to-date: http://www.gwtproject.org/steering.html
(Ray has been replaced by Bhaskar Janakiraman as he moved to the Inbox team
–afaik–,
Can somebody please tell us who are the members of gwt committee and is
there any meeting notes in the last year (or two) ?
--
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, se
12 matches
Mail list logo
