It went well - it was a smaller crowd, probably in part due to fewer "talks" and more "contrib", but that's a balance we're going to have to continue to strike.
The main focus was on getting closure to provide the sort of optimization we've come to expect from gwt2, and we had a surprisingly large amount of difficulty in getting it to do this. I'm doing a writeup now for the closure compiler list, since we've got a fairly simple set of plain example JS that demonstrates the issue. The biggest concern is that this means that you have to use raw JS to "explain" this pattern to the compiler, otherwise it will not understand and will not bother to prune/optimize code, but our guess right now is that this is a specific enough of a use case that we can provide tooling to solve this problem, and that tooling can generate JS instead of developers writing it. Also worth noting that j2cl+closure has been at least on par with gwt2 if not smaller in the examples we've tried so far, so especially if it tends to generate sub-optimal code in a few cases, we know it is doing a far better job than gwt2 in other cases. Next week we have two talks planned already, and have room for 1-2 more if anyone is interested. As usual, the call will start an hour early with no set topic, instead anyone can ask questions or make suggestions on what we can discuss. https://calendar.google.com/event?action=TEMPLATE&tmeid=MXVmcmw1czU5cHMxYm5lcHEzZWQ0MjR2ODUgY29saW5AdmVydGlzcGFuLmNvbQ&tmsrc=colin%40vertispan.com -- Colin Alworth co...@colinalworth.com On Tue, Jul 21, 2020, at 8:24 AM, Michael Conrad wrote: > How did it go? > > > On 7/15/20 5:02 PM, Colin Alworth wrote: >> We have a shorter itinerary this week - I'll record a short piece on >> j2cl-maven-plugin and how to start a project with it, try using pieces from >> the ecosystem. >> >> Dmitrii, Ahmad and I will continue our brainstorming about efficiently >> producing both optimized output and minimizing the work the compiler does >> for i18n/cldr generated code. >> >> > > > -- > 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...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit-contributors/864efc55-2de0-3db7-be88-e3fe9170da42%40newsrx.com > > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/864efc55-2de0-3db7-be88-e3fe9170da42%40newsrx.com?utm_medium=email&utm_source=footer>. -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/17bf2f7e-77ca-4fd7-959b-e2412f0047c0%40www.fastmail.com.
