> it would be nice to have J2CL released separately as soon as it is ready
I still don't get why the development of J2CL / GWT 3 cannot be done openly like any other open source project. Why this secrecy is necessary. This kind of project management type is very unusual in case of open source projects It will make many people to stay away from the project and to switch to (even worse) alternatives :( -- Norbi On Saturday, 9 June 2018 22:47:48 UTC+2, Ming-Yee Iu wrote: > > Wow! It's great to see all that progress being made on GWT 3. That's a lot > more backwards compatibility than I was expecting. > > Still, it would be nice to have J2CL released separately as soon as it is > ready to do so because > > 1. Based on past experience, it will take 1-2 years or more before GWT > 3 is released > 2. J2CL is useful independent of GWT 3. Just recently, I wanted to > package up some Java code as node.js NPM packages for others to use, but > doing that really requires something like J2CL instead of GWT > 3. It's good to have some time for people to develop best practices > for how J2CL code can be mixed with JS. Google's JS code style is very > clean, well-typed, and Java-like, so it will naturally work well with > J2CL. > Much real-world JS code is ugly and makes use of horrible JS corner cases > and hacks, so it might take a while to figure out best practices for how > to > deal with those. > > -- 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/9516f69a-62cc-4eb9-86e6-aaeec3a09366%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
