3 ms·
As far as I can tell, the advantages of using a RIA (rich internet application) toolkit are: * easier to develop desktop-like web applications * more straight
by astrofinch 16y ago
As far as I can tell, the advantages of using a RIA (rich internet application) toolkit are:
* easier to develop desktop-like web applications
* more straightforward to avoid duplicating client-side and server-side logic
and the disadvantages are
* your page tends to load significantly slower
* your page isn't accessible to people browsing without javascript or disabled folks
* you'll still have to generate html for googlebot, etc.
Things I'm not sure about:
* difference in development time
* whether it's equally easy to integrate real-time functionality when you're using a RIA toolkit
What did I miss?
(other examples of RIA toolkits are http://www.sproutcore.com/ http://www.sproutcore.com/ and http://cappuccino.org/ http://cappuccino.org/. SproutCore is notable for supporting mobile devices unusually well, so I guess that might be a point in its favor?)
- lkcl 16y ago* page loads are slower: in a web 2.0 app they're also a one-off, and if you want to you can do dynamic loading of modules. it's not that bad, due to HTTP GZ compression. * pyjamas-web is an experiment to do pure-html, executing the exact same python pyjamas app SERVER-SIDE. disabled folk: wrong. look at GWT accessibility. * googlebot: not entiiirely correct. look up the (rather stupid "!" referral system that google "invented") - and again, look up "pyjamas-web" experiment. l.
- astrofinch 16y agoSo have you also written apps with Django? How does development time compare?