News for hackers. Stuff that matters.
Re:How Basecamp Next got to be so damn fast without using mu... by VMG on Friday February 17, 2012 @11:43AM (#3603925)
A small change in state can cause a large change in the view.

When the server renders the html, it has to send all the portions of the view that have changed. When rendering client-side, the server only needs to send the portion of the state that changed.

Re:How Basecamp Next got to be so damn fast without using mu... by latch on Friday February 17, 2012 @11:56AM (#3603981)
Good point, thanks. So it potentially provides you with opportunities for further optimization. I guess the message from DHH is that they hit their performance targets, so this would be an unnecessary optimization (and I'm tempte to say "non-trivial to implement"..but now I know I'm being biased..)
Re:How Basecamp Next got to be so damn fast without using mu... by hollerith on Friday February 17, 2012 @01:12PM (#3604318)
>A small change in state can cause a large change in the view.

It can, but maybe there is a way to write Basecamp so that large changes in view are rare.

Re:How Basecamp Next got to be so damn fast without using mu... by VMG on Friday February 17, 2012 @03:34PM (#3604866)
That is limiting the application though. With client-side rendering you can have large view changes with little state change.