"The Google Web Toolkit software and sample code developed by Google is
licensed under the Apache License, v. 2.0. " - so, if you are really
worried about it "disappearing" keep an up to date copy of the trunk.
Alan
>
> What do you guys think? (if you agree, +1 this)
>
> Best,
> Josh
> --
> 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/-/Vygrm-U-8-oJ.
> To post to this group, send email to google-we...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-tool...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
--
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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
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
>
>
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> >> > To unsubscribe from this group, send email to
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/w4BDuP8UfowJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
There is a significant difference between having to watch the GWT
Contributor Google group and an official post to the GWT blog. Not
posting to the official blog is surely a sign of internal GWT
problems. A healthy project is going to have official updates.
--
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/-/TSws9XOf334J.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
--
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/-/TSws9XOf334J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsub...@googlegroups.com.
My 2 cents:
1st cent: GWT works for us like a charm for many years in really large
dev teams and in projects used by millions daily. So I am totally sure
that GWT is great and super-stable. It's not a toy but a really
productive and working thing.
2nd cent: I also find it a bit strange that Google does not say more
about GWT. But on the other hand it's open source and if you follow
the contributors list you get a good feeling that a lot is going on.
Cheers,
Raphael
(btw. @ GWT devs: Great job. I enjoy using GWT each day...).
Google, please realize that GWT is awesome and put all your great efforts into GWT instead of starting all over with a language like Dart that doesn't bring any real pros to the table and will never be a standard like Java/Javascript.
A roadmap including some long term commitment would really make my day.
--
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/-/9jcRLdMkjmkJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
OK yeah sure maybe it is "political" but ...
What if Oracle wins big against Google in terms of java use for android.
From Google's standpoint, couldn't you see why they might be
interested in an alternative? Do you know what courts will decide?
Does Google? I don't.
Shawn
Two weeks later and not a single reply by a GWT developer? On any open source project that would be enough to scare users away.
--
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/-/M8iedHJtDncJ.
> > To post to this group, send email to google-web-toolkit@googlegroups.com.
> > To unsubscribe from this group, send email to
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/2hh07FVI2kcJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
+1
> > To post to this group, send email to google-we...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-web-tool...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-web-toolkit?hl=en.
--
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/-/2hh07FVI2kcJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
--
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/-/Il4Yx4xku4EJ.
For over a year I was trying to convince my customers (that I develop programs for) to use GWT with their SAP system. The technologies available over there are WebDynpro for ABAP or Business Server Pages, which do not even know what AJAX is.In January I managed to do that. We just finished porting one of the tool to mobile phones with the use of GWT on SAP. We just started writing another tool that was simply impossible to write in Web Dynpro ABAP.It would really break my belief in Google, if now (after over a year of convincing my customers) I would need to go back and say - GWT is no longer available.One thing that comes to my mind. I remember 2 years ago seeing all those great presentations of Google Wave on Google I/O. I managed to convince my customers to use it. We really loved it. It was great for communication. Look where we are now with that tool. Not only it just died, but there's also no decent export of the data from that system available (selecting at most 10 or 100 waves and putting them to PDFs is not enough for me - it will take me ages to select and download).Also what was contributed by Google to the open source seems to have very little stability. I've tried to use the projects on Apache, but the server simply stops working after a couple of wave edits.
So what I am really affraid of, is that this lack of commits to GWT public repository is really a way of doing the same thing as was done with Wave. We will be left without decent source code.
I've been for years with technologies like SAP or AS/400. Those are really annoying when you try to do something modern. But the thing that is good about them is that they never go away. I understand that Google needs to try new things (dart). But turning away from such a big project like GWT is stabbing yourself in the back.
--
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/-/7AzFOXodwtkJ.
I strongly disagree with this. First of all browser technology and HTML are in constant flux. If GWT is not updated, it will very soon become out-of-date (bugs in new browsers) and unusable (reliably usable over a broad base of browsers and platforms). Secondly, building apps with GWT is a full time job. Having to understand and maintain GWT makes two full time jobs. Building GWT apps could easily be a multi-million dollar effort - and so could maintaining GWT. This is a huge, huge risk!Another issue I've seen this many times before. When Windows became popular, many developer tools appeared. Many were quite good. IMO, the worst development environment by far was Microsoft's MFC. Virtually all of the other tools either sold out or got dropped. Management often chose MFC over other tool because they were non-technical and the old IBM adage applied to Microsoft "no one ever lost their job by selecting Microsoft" ruled. In the end, the industry largely settled on the absolute lowest common denominator. Innovation in that area, for all practical purposes, is dead.
Now we have ASP, JSP, and other popular mashups out there. I am utterly shocked how poor they are (although to their credit, they are trying to solve practical problems given an environment that was clearly not meant to support what they are attempting!). These environments are among the worst I've ever seen. It's one kludgy work around after another with three totally different environments attempting to interact. GWT goes a very long way to solve this very significant problem. However, GWT is a total waste of time if you risk your entire company on it and it gets dropped. In terms of financial risk, very unfortunately, tool popularity and support beats functionality, elegance, and productivity every time.
A statement of commitment from Google would make a huge difference to me.Blake McBride
On Thu, Apr 12, 2012 at 7:52 AM, Frank <frank....@gmail.com> wrote:
GWT will also not go away...
If you have downloaded GWT on your computer you just can keep using it even years after Google has dropped GWT...
Just like you still can program in QuickBasic or something.
GWT doesn't need anything from Google on the web to operate.
I will just keep using GWT if Google drops it, and see keep an eye on Dart.
Op donderdag 12 april 2012 10:00:15 UTC+2 schreef dominikz het volgende:
I've been for years with technologies like SAP or AS/400. Those are really annoying when you try to do something modern. But the thing that is good about them is that they never go away. I understand that Google needs to try new things (dart). But turning away from such a big project like GWT is stabbing yourself in the back.
--
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/-/TSws9XOf334J.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
--
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/-/mXcfTwGGCc4J.
--
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/-/oMjVjCSRcF0J.
I understand that the GWT team is regrouping, and hope you'll keep us posted.
I also feel, that the community wants to be more informed and invloved and I think that a scheduled GWT hangout could be awesome for that porpose.
although the community isn't that big, I personally feel it's growing stronger each year, and that the GWT team can use it for achieving more (not just codewise).
Best,
Joshua
Great! Thanks for Ray, looking forward hearing from you.
--
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/-/F_zzFyjpQYMJ.
Trey
A.U.S Cristian Rinaldi Teléfono Móvil: (0342) 155 238 083 www.logikas.com Lisandro de la Torre 2643 Of 5 - 3000 - Santa Fe Teléfono Fijo: (0342) 483 5138 |
A paragraph or two every couple of months about what you are working on would make a huge difference.
Trey
--
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/-/Sh0MPpPmifUJ.
If Google can provide GWT support service, that will be super, which
is a win-win for companies who has GWT in production and Google GWT
development team.
With the rise of the new developers.google.com, and with Google trying to rally up developers using Google technologies and products, and the rise of Dart and unclear future of GWT, I think it's about time that Google will rethink the all "We don't and won't have a road map, and there are no release dates for new GWT versions" and embrace the GWT developers community.What do you guys think? (if you agree, +1 this)Best,Josh
--
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/-/SpJYwne0PdAJ.
Here is more info from Google about GWT. :)