Here again is the right kind of assessment to make on whether to use SmartGWT for a given application:
If your users will use the application infrequently and briefly AND many of them will not have broadband AND you cannot use a CDN or similar approach AND you have no way to mask the download time (see background downloading) AND your app doesn't require anything unique to SmartGWT AND you decide that it makes sense to spend extra time in development and delay release in order to save your users a few seconds wait on the first ever access THEN yes by all means use another technology, SmartGWT doesn't solve every problem and it would be worse if it tried to.
- GWT's widget system will never match JQuery's ultralight footprint for basic interactivity
- GWT is an awkward technology to use for sites that are mostly about content rather than interactivity (eg, mainstream CMS integration lacking)
- perhaps worst, GWT applications grow in proportion to their most complex screens, forcing you to keep dividing the application to keep a light footprint on key landing pages, which basically throws away many of GWT's key benefits.
Codedude, as we mentioned before, posting your .. unique .. opinion in various places only forces the SmartGWT team to waste time making sure the full story is told. This hurts SmartGWT and the SmartGWT community. This discussion has already been pursued exhaustively, let's leave it alone now.
Leave a comment: