Dear fellow GWT users,
I would like to announce that I have finally solved what I always thought
to be GWT's greatest weakness: its lack of debugging information for
client-side exceptions in production.
With my patch, your deployed app will be able to report stack traces like
this:
On Wed, Jul 17, 2013 at 4:56 PM, Alex Epshteyn alexander.epsht...@gmail.com
wrote:
I would like to announce that I have finally solved what I always thought
to be GWT's greatest weakness: its lack of debugging information for
client-side exceptions in production.
With my patch, your
Do you plan to maintain that code if it is integrated into GWT or will it
be a one time contribution and other people have to wrap their head around
it again if your solution needs to be adjusted?
I ask this because GWT will drop support for IE6/7 relatively soon and
probably by the end of
I certainly applaud the obvious time, effort, and care that you've put
into these improvements, but 45% size and 22-44% execution speed overhead
sounds like a rather painful penalty to pay. I'm not sure that's going to
be worth using in a performance-sensitive application.
If you use
Thanks for all your questions. Here are my answers.
So, something like this has been used at least internally for quite a long
time -- what exactly did you have to change in StackTraceDeobfuscator?
Quite a few things, actually. I go into great detail about that, including
diffs of some
