I am open to listen to what GWT developers have to say and to get a good feedback loop going.
So if you have something in mind please bring it up in the gwt contributer list I will take a look for sure! -Daniel Am 09.07.2012 um 16:01 schrieb Joshua Kappon: > We're hoping that the steering committee will make steps for reaching and > expanding the GWT community more actively. > I think that a great step in this direction is establishing a road-map with > the help of the community. > > Regular GWT Hangouts could also be nice ;) > > > On Sunday, July 8, 2012 5:01:42 PM UTC+3, Daniel Kurka wrote: > I have been on IO all week and talked to many people from the GWT team and > other GWT developers. > > I am not worried at all about GWTs future. It had a bad marketing in the last > year due to many reasons which we will turn around in the upcoming months > with the GWT steering committee. > > The GWT 2.5 release is one of the biggest GWT ever and has many new things in > there. Wait for Rays talk to appear (in which I play a very small role) on > the youtube in a few days to clear things up for you. > > -Daniel > > > > > Am 06.07.2012 um 22:04 schrieb Murray: > >> Daniel, >> >> I was at Google I/O last week and decided ask for myself.. the responses I >> got, was NOT good >> I flat out asked one Googler, working a developer "bar" in the main lobby >> (not sure what team he was on) >> "..should I continue my project that's not yet released, in GWT or what..?" >> and he appeared to be reluctant >> to say...suggesting that something was up! he then went on to say he would >> change it to DART as it >> is not yet a complete standard.... So then I asked "..what about >> JSP/Appengine or Python?" and with a big Grin >> on if face he shuck his head affirmatively violently ... as if to say he >> doesn't want it to be said that "he told me so" >> >> right now we need some GWT folks to step up and say something definitive!!! >> this "rumor" has been going around for >> a while now.. and there were no Sessions on GWT at the IO2012 other than >> Porting GWT to DART !!! >> >> I went to a session on Appengine /REST and a a question was asked at the end >> of the session regarding >> REST and GWT the answer was also suspect... >> >> I think this link will take you to the session ..forward to the end... >> https://developers.google.com/events/io/sessions/gooio2012/121/ >> >> >> >> >> >> On Friday, June 22, 2012 1:54:29 PM UTC-4, Daniel Kurka wrote: >> I can assure you (since I am deeply invested in GWT) that GWT is in no way >> of being phased out. The main reason is the amount of other talks (android, >> google+) being added to the conference, reducing talk time for everyone else. >> As Thomas said before there is something big coming for GWT which will be >> announced in Rays talk at IO. >> >> There are a lot of google products relying on GWT which is not something >> that you could change in a short amount of time. Dart may be an interesting >> project, but it is not going to change the way google currently depends on >> GWT (at least not in the next years). >> >> The fact that the GWT team is looking for team members on the google >> employment list should also put you in the direction that this is no where >> near dead. >> >> So hopefully as a contributer to the project I can calm you nerves a little. >> >> -Daniel >> >> >> >> >> >> >> Am 19.06.2012 um 19:29 schrieb Thomas Lefort: >> >>> https://groups.google.com/forum/?fromgroups#!topic/Google-Web-Toolkit-Employment/NJmWmKsXQlI >>> >>> sounds pretty healthy to me :) >>> >>> I bet competition will be fierce! >>> >>> >>> On Thursday, 17 May 2012 08:00:00 UTC+2, Celinio Fernandes wrote: >>> Hello, >>> I just noticed that the schedule for Google IO 2012 is now available : >>> https://developers.google.com/events/io/sessions >>> Not sure whether it is definitive or not. >>> I see that this year there is no session dedicated to GWT. How come ? >>> But there are 2 sessions dedicated to Dart. Is this a sign ? >>> >>> >>> >>> >>> -- >>> 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/-/m0up22vaGNoJ. >>> 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. >> >> >> -- >> 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/-/Jh2IrAfsH8MJ. >> 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. > > > -- > 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/-/wiC33gog6rEJ. > 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. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
