It has been about 4 months since Ray's post on what the GWT team is working on. In that time there has been only one GWT official blog update and no releases for 6 months.
After reading the link that Alan suggested, I am encouraged but on slightly since the post is several months old. There needs to be some official signs of life. If the GWT group is fully staffed then it should not be possible to communicate that in some way. At Caltech we have been using GWT for over 4 years. We have build a very large and amazing set of web applications using GWT. We are very invested in GWT and I am eager to see some more obvious signs of life. Trey On Apr 4, 6:20 am, Joshua Kappon <shuky.kap...@gmail.com> wrote: > Joseph, Coderinabstract > > I agree with you both. > I also appreciate the GWT contributors, and I hope Google will continue to > support and improve this toolkit, > But since there was no official movement on the blog and on the project > page for about 6 months, I believe it is our responsibility to let google > know it is missing, and we hurt for that, help me spread the word please. > > Alan, > I am following Ray, and saw that post. I am also searching constantly for > new updates about the project, but don't you agree it should have been at > least posted also in the blog? again, if you want the community to grow, > you must make it easier for new comers to join and bring them up to date. > > > > > > > > On Wednesday, April 4, 2012 7:07:22 AM UTC+3, coderinabstract wrote: > > > + 1... > > > Working on web apps since web came to existence.... asp, jsp, cgi, DHTML, > > javascript, struts and it was a real mess and did not truly enjoy it. > > Also,apps created were error prone with code bloat and good design was > > messy and a challenge. > > > The power of true OO, with Java, generics and good design with GWT is a > > complete game changing innovation compared to the page based development, > > untyped and script based frameworks in creating highest quality end user > > experiences. > > > Sincerely hope thats GWTs power with HTML5/CSS and supporting a truly open > > standard already qualifies this to be the best design experience for > > someone like me who really enjoys good application design. Augmenting GWT > > with frameworks like GWTP and other opensource frameworks makes this > > a formidable high performing application design architecture out there. I > > have yet to find a solid scalable OO/Java based design framework with this > > kind of pure OO and componentization power for user experience > > management... combine that with GIN/GUICE and it keeps on getting better. > > > I sincerely hope Google continues to promote this awesome framework and > > continue to make web development so much fun. Was kind of disappointed to > > see it go away from the front page of the new google developers site, > > however agree that this is a large and formidable community which shall > > continue to move forward. > > > Best... > > > On Tuesday, April 3, 2012 12:54:53 PM UTC-4, Alan Chaney wrote: > > >> Hi Joseph > >> On 04/03/2012 08:34 AM, Joseph Lust wrote: > >> > Alan, > > >> > Thanks as always for your courteous replies. I'm grateful for the > >> > efforts the Google developers put into GWT, as any other enterprise > >> > building such a framework would most certainly charge the Earth for it > >> > while also crippling its functionality in exchange for customer > >> > lock-in. Google just makes great software. > > >> > However, I work in a large enterprise where our GWT Community of > >> > Practice group must make a case for why any new application should use > >> > GWT. It is important to management to know the future of GWT and a > >> > roadmap is how this is commonly done. While I don't personally think > >> > GWT will suffer from the recent project pogroms at Google, a roadmap > >> > and rough release schedule will lend greater confidence to others in > >> > the stability and longevity of the framework needed before a company > >> > is willing to build multi-million dollar projects with it. > > >> Have you seen this thread on Google+? > >>https://plus.google.com/117487419861992917007/posts/6YWpsHpqMqZ > > >> especially Ray Cromwell's comment about half-way down? Also Eric > >> Clayberg's - I suggest you read the whole thread, but I've copied and > >> pasted two comments which caught me eye. > >> <SNIP> > >> Ray Cromwell: "Many of Google's services are still being written in GWT > >> and won't change anytime soon, for example AdWords and AdSense, from > >> which Google derives the majority of their revenue, are written in GWT, > >> so given that fact alone, GWT will be around for a long time and > >> continue to be improved. The loss of Ray Ryan and Bob were a big set > >> back (unrelated to Dart), and we have people trying to get up to speed > >> on their contributions to maintain them, but honesty, we rely on many of > >> our top external users like Thomas Broyer and Stephan Haberman to fill > >> the gap until that time. (Thanks guys) Turnover is natural and happens > >> at all companies, and it's always rough. > > >> The next release or two of GWT may include more core improvements than > >> the last few point releases of GWT so far, consider: > >> 1) Compiler optimizations that reduce code by size by 30% uncompressed, > >> and 15% gzipped > >> 2) SourceMap support and Source-Level Java debugging in Chrome (and > >> hopefully Firefox) > >> 3) A "super draft mode" that can recompile many apps in under 10 seconds > >> and most under 5 > >> 4) New "to the metal" "modern browser" HTML bindings > >> 5) Testing framework that makes GUI testing delightful > >> 6) Incremental compile support to speed up production compiles > > >> So code will be getting smaller, faster, easier to debug (in some > >> situations) and test, and compiles will go quicker. This reflects > >> somewhat the shift in GWT team composition, but as people ramp up on > >> other parts of the SDK (e.g. MVP stuff), I'm sure there will be improved > >> responsiveness to fixing bugs in that area as well. > > >> Obviously, we want Dart to be a huge success, but even if it is, Java > >> isn't going away anytime soon. :)" > >> </SNIP> > >> <SNIP> > >> Eric Clayberg: "I can assure you that GWT is not in maintenance mode. > >> Not even close! Quite the contrary, GWT is very healthy, and the GWT > >> team continues to focus on making GWT a great choice for building > >> structured web applications now and in the future. If you have the need > >> to start a new web app project, GWT would be an excellent choice, and > >> there is no reason to avoid it. The GWT team is fully staffed, and we > >> have very ambitious plans for GWT's future. GWT is used by many large, > >> important projects within Google (and outside Google), and that is > >> unlikely to change any time soon." > >> <SNIP> > > >> I accept that its not an official roadmap - but it seems to give a clear > >> indication of a continued commitment to developing GWT, albeit on a > >> slower scale than before. I shoudl add that I have no commercial > >> affliation with Google whatsoever, I just use GWT in a couple of > >> different projects in two different companies. > > >> Alan > > >> > If GWT retains buy-in at Google, I don't understand why such planning > >> > would be detrimental to the GWT team. As I see it, such public > >> > planning will only drive more companies and startups to join the GWT > >> > bandwagon. > > >> > Sincerely, > >> > Joseph > > >> > -- > >> > 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/-/5rzWGy06oFgJ. > >> > To post to this group, send email to > >> google-web-toolkit@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > google-web-toolkit+unsubscr...@googlegroups.com. > >> > For more options, visit this group at > >> >http://groups.google.com/group/google-web-toolkit?hl=en. > > On Wednesday, April 4, 2012 7:07:22 AM UTC+3, coderinabstract wrote: > > > + 1... > > > Working on web apps since web came to existence.... asp, jsp, cgi, DHTML, > > javascript, struts and it was a real mess and did not truly enjoy it. > > Also,apps created were error prone with code bloat and good design was > > messy and a challenge. > > > The power of true OO, with Java, generics and good design with GWT is a > > complete game changing innovation compared to the page based development, > > untyped and script based frameworks in creating highest quality end user > > experiences. > > > Sincerely hope thats GWTs power with HTML5/CSS and supporting a truly open > > standard already qualifies this to be the best design experience for > > someone like me who really enjoys good application design. Augmenting GWT > > with frameworks like GWTP and other opensource frameworks makes this > > a formidable high performing application design architecture out there. I > > have yet to find a solid scalable OO/Java based design framework with this > > kind of pure OO and componentization power for user experience > > management... combine that with GIN/GUICE and it keeps on getting better. > > > I sincerely hope Google continues to promote this awesome framework and > > continue to make web development so much fun. Was kind of disappointed to > > see it go away from the front page of the new google developers site, > > however agree that this is a large and formidable community which shall > > continue to move forward. > > > Best... > > > On Tuesday, April 3, 2012 12:54:53 PM UTC-4, Alan Chaney wrote: > > >> Hi Joseph > >> On 04/03/2012 08:34 AM, Joseph Lust wrote: > >> > Alan, > > >> > Thanks as always for your courteous replies. I'm grateful for the > >> > efforts the Google developers put into GWT, as any other enterprise > >> > building such a framework would most certainly charge the Earth for it > >> > while also crippling its functionality in exchange for customer > >> > lock-in. Google just makes great software. > > >> > However, I work in a large enterprise where our GWT Community of > >> > Practice group must make a case for why any new application should use > >> > GWT. It is important to management to know the future of GWT and a > >> > roadmap is how this is commonly done. While I don't personally think > >> > GWT will suffer from the recent project pogroms at Google, a roadmap > >> > and rough release schedule will lend greater confidence to others in > >> > the stability and longevity of the framework needed before a company > >> > is willing to build multi-million dollar projects with it. > > >> Have you seen this thread on Google+? > >>https://plus.google.com/117487419861992917007/posts/6YWpsHpqMqZ > > >> especially Ray Cromwell's comment about half-way down? Also Eric > > ... > > read more » -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
