I have to agree. A long time ago we moved away from GWT RPC to an approach that used straight JSON. This forced on us by the poor performance on mobile devices. Right away we saw 3 to 5x speed improvement and significant code size reduction. Sure the developer experience wasn't quite as nice. However we, could hardly measure an actual hit in overall productivity. To be honest, our user experience will always take priority over developer UX.
On Saturday, May 20, 2017 at 11:07:33 AM UTC-4, Paul Robinson wrote: > > As a heavy user of GWT-RPC in a large app, I've become disillusioned with > it. That's for three reasons: > > - I often need to see what data is being sent, and it's just not very good > for that. It makes debugging harder than it could be. > > - it's not good for communicating from a mobile app. > > - it's much too easy to accidentally send much more data than necessary. > Being forced to think about your content on-the-wire would probably make a > better product in the long run. > > So we're going to pay the price to migrate away from GWT-RPC and I don't > feel too bad about it going away. > > I just hope we don't have to give up widgets too. I don't see that being > practical for us. > > Paul > > On 20 May 2017 2:56 pm, "Learner Evermore" <learner....@gmail.com > <javascript:>> wrote: > >> ... and before someone mentions version/compatibility issues with >> serialization (using any framework) not that NO framework solves this, they >> just have different ways of not solving it. And all frameworks expose >> *exactly* equal ways of dealing with it should one be interested. Including >> java.io.Serializable. And if you happen to not care and change things, it >> always results in errors (default cases excepted) only with >> java.io.Serializable you get that error immediately and with some other >> popular frameworks you get the error at the time of first use - hence less >> detectable. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "GWT Contributors" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com >> <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-web-toolkit-contributors/1eaced67-96f6-4ea0-9ef7-5bbabb2cf569%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/1eaced67-96f6-4ea0-9ef7-5bbabb2cf569%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/c4b7f9fe-7fa2-4493-a788-0b49e6c31868%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
