Re: Overuse of "AssumedStale" Issue Tag

Of course I recognize the pain and a few weeks ago I have to admit I was less positive then now..

But in the mean time many things have happened, issues are being fixxed as we speak...

Yes, I also have a lotttt of issues that are put on AssumedStale... But that means they get a lower priority, not that they are forgotten!..

Please put yourself in their position (GWT dev member)... 

Imagine you just entered the GWT dev team and have to clean up 5000 open issues ?... What would you do ?... 

Of course it's a bad thing that it got this far, but taken as it is, Google had their own private gwt issue tracker and hardly used the public issue tracker (follow the sources please)...

All these things have changed, contributors are joining the gwt development and things are being picked up quicker then before... 

Patient please, see it as GWT just started as it's completely different "thing" now..

I understand your "complaints", but please turn them around in "help"... 

The way things are setup now, it's very easy to contribute code to to the Trunc, others will review it, and accepted (if your lucky ;)...

This setup certainly invites me (and others) to do this...

Like mentioned, every body stresses/usages the browser differently, that results in different kind of issues. As such, it might be hard that your issues get  attention. The more reason to pick them up yourself and contribute (in the past contributing was hard, as google had strict rules, that all changed now)...

BTW: this is nothing... Hibernate is/was much worse ;)... The Hibernate dev team would hammer you down ;)....

On Tue, Jun 4, 2013 at 10:15 AM, David <david.nouls@gmail.com> wrote:

Ed,

You are right that my glass is half empty, but that is just my character ;-)

I've been using GWT since it was first introduced, I loved it straight away - coming from a Motif/JBuilder/Swing background.

I am still hoping that they manage to get this back on-track, but I just hope that they put a little more focus on bug-fixing.

It is really frustrating that about all the issues I ever reported where put on assumed stale. I spend a lot of time to detect and report these. In the mean time I have worked around many of them (JSNI to the rescue!) and I guess a lot of other people have done the same. But for new people starting out with GWT, this is not easy.

You might now have experienced the same issues, but all applications stress the browsers differently. We need to send a lot of data over RPC and that was just plain bad on older IE. Our software runs over fast networks, so the bandwidth is not the issue. But the browser limitations in IE7/8 were. I moved on to JSON for my RPC needs and it moved from minutes to less than a second in some cases.

David

On Tue, Jun 4, 2013 at 9:50 AM, Ed <post2edbras@gmail.com> wrote:

@David, @Mauro,

I am surprised and disappointed by your reactions.

My reaction on this all:

Please be positive and not so negative. Clearly your glass is half empty and mine is half full (and I am using GWT for about 7 years now)...

Please follow the GWT news, G+ GWT posts, Ray Google 2013 GWT session, the issues being solved blazing fasts currently..., the contributor forum, etc...

I am sure that if you follow these sources, your glass will be half full as well. If not, please see a doctor ;)...

@David: your list of negative points is incorrect as I am building huge gwt projects and don't have this experience of 80% of your issues. So you might want to consider refactoring/reviewing your code/GWT usage.

GWT had a tough year putting all pieces in place, but I think things look very promising which they  are showing if you follow the above sources...

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.

To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/5aNsIcPKDm4/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.