News for hackers. Stuff that matters.
Re:The pros and cons of developing a complete Javascript UI by brunoc on Wednesday August 10, 2011 @10:11AM (#2868248)
There are ways around that.

One of the easy ways is to simply in-line your JSON model when you generate the initial page.

So essentially your webpage contains the html structure you need, followed by something like

    <script>
        Myapp.start( { tasks: [ { id: 1, title: 'do something' } ]) 

    </script>
So essentially you bootstrap your application in order to avoid a large AJAX call right off the bat.
Re:The pros and cons of developing a complete Javascript UI by prateekdayal on Wednesday August 10, 2011 @10:16AM (#2868274)
In fact Backbone's documentation on fetch (the method for populating collections using an AJAX call) specifically recommends this pattern - http://documentcloud.github.com/backbone/#Collection-fetch
Re:The pros and cons of developing a complete Javascript UI by radicalbyte on Friday August 12, 2011 @06:43AM (#2876746)
I did almost exactly that on my last project. Works a treat.

With html5 features (i.e. local storage) you can just cache data client-side and sync in the background.

I.e. build a disconnected client-server application.