Re:Diaspora re-writes its front to Backbone: why and what it...
by scottschulthess on Tuesday January 10, 2012 @05:47PM
(#3449499)
The article was confusing a bit confusing about the Garbage Collection so I'll try to explain.
1. Dispora is slow, why?
2. Requests take a long time on the server, why?
3. Most of the time is spent in ruby doing processing.
4. Why is ruby slow?
5. Ruby is slow because of the garbage collector.
6. How can we get around this ruby being slow problem?
7. Reduce calls to server side by writing replacing server side calls with javascript rendering of templates and whatnot.
Re:Diaspora re-writes its front to Backbone: why and what it...
by leoedin on Tuesday January 10, 2012 @04:56PM
(#3449264)
It fixed their garbage collection problem by reducing the amount of server-side processing they had to do (and hence, reducing the amount of garbage that required collection). Rather than send completely rendered HTML to the browser, they're using javascript in the browser to turn the data coming from the server into the rendered page.
Re:Diaspora re-writes its front to Backbone: why and what it...
by Helianthus on Tuesday January 10, 2012 @04:53PM
(#3449249)
Ha. Well, that's why I'm the asshole. ;)
Which gave me the first hit of www.backbonemedia.com/
In fact, backbone.js is no where on the first page for that search.
That's amazing it comes up first for "backbone". I did actually find that link eventually, and try out the "example" todo list, but that gave me no information about how this would fix a garbage collection problem. Does anyone know how it fixed their GC problem?