On Friday, July 6, 2012 11:46:00 PM UTC+2, Murray wrote: > > Jim, > Thanks for the reply and links, I never noticed Rays session on the list, > then I again.. the sessions were being constantly updated anyways... Wish > I had gone to that one >
Also, we've been in close touch with Ray recently (the Steering Committee; by mail, chat, and conferences on the phone –which are fun to plan when spanning Europe and the US 'til California ;-) ) and the news are good. The reason Google opens GWT is that they don't have the resources to handle the community's need/pressure (the priority, understandably, always was on their own internal needs first); the goal is to share the resources and responsibilities with others (among which "big players" like RedHat/JBoss, Sencha and Vaadin, and smaller ones like ArcBees; see Ray's slides for the full list). If you're not yet aware, before you learn it from uninformed sources: yes, Google Atlanta engineering offices are closing, so the original GWT Team is shut down. Dev already started shifting to Mountain View, CA (where Ray Ryan worked until last fall, and Ray Cromwell is, among others), but there will probably be some blurry moment this summer as things settle down (sources will also be moving from "internally developed within Google and mirrored to the public SVN" to "openly developed on Git and mirrored within Google". So yes, expect some "blurry moment" this summer, but news are good. (BTW, the Atlanta-based GWT Team worked that last year on building a collaborative IDE they just open-sourced before closing the doors: http://www.google.com/p/collide ) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/HEO-6L17uxcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
