Mauro, I have the same feeling. It seems like nothing has changed since GWT being detached from Google. After years of neglecting the loyal developers, who devoted time to report issues that were bugging us, we just got slapped in the face. We are now officially allowed to fix the bugs ourselves - and maybe after spending our free time on this, just maybe they will take our fixes.
This attitude does not give me a lot of confidence that GWT is going the right direction, so I will probably be holding off in advocating GWT as a dependable tool for enterprise developments. Bug fixes are way more important than new functionality. We have to support our software for 10 years, we need to be able to depend on a professional attitude towards bug fixing. Look at the code base now: - 4 different ways of handling events (Listeners, Handlers and 2 event bus implementations - which should I choose ?). - CssResources are not really usable with style dependent naming as used in most of the widgets so I need to mark as NonStrict or use @external all over the place. - GWT RPC is not fast enough and causes stackoverflow and slow script warnings (well after years of waiting that bug will be resolved by moving to IE9). - DeRPC was supposed to fix the deficiencies of RPC but it got scrapped - RequestFactory is the new kid in town, but let's face it, it is no that easy to start with because we are not all pushing JPA Objects straight to the browser. We have our own JDBC layer that works much faster than most JPA compliant implementations. - LayoutPanels vs regular panels, watch out when mixing. - No full featured table implementation. - No CellTree (basically a big lack of decent components that are completely inline with all optimisations that GWT allows) - ... I'm sure others can add to this list, this is just the first things that comes to mind. and those are just the first things that comes to mind. David On Tue, Jun 4, 2013 at 9:06 AM, Mauro Molinari <[email protected]> wrote: > I think Thomas's comments on > http://code.google.com/p/google-web-toolkit/issues/detail?id=6962 and the > "spring cleaning" thing say it all on the attitude of GWT devs toward bug > reports: they are just an annoyance and the fact that the issue tracker has > a lot of very old reports (not even considered for years) is just the > reporters' fault. After all, GWT is quite perfect as is and many supposed > bugs should have fixed themselves during the years, or are just invalid. > > Feel free to provide patches, although they probably won't be reviewed at > all, since your reports usually just matter to you and few others. > > I'm really sad :-( > Mauro. > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > 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 [email protected]. To post to this group, send email to [email protected]. 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.
