How Basecamp Next got to be so damn fast without using much client-side UI

Re:How Basecamp Next got to be so damn fast without using mu... by rkalla on Friday February 17, 2012 @10:58AM (#3603742)

Are you guys taking care to send as-plain-as-possible markup from the server to the client and then style it up to keep most the UI development in CSS or are you just sending through raw, styled HTML that gets inserted as-sent directly into the page?

This reminds me of the early days of Java Servlets when people would stream back HTML from inside their Java Servlet code to JSP pages to build it out... made it impossibly hard to edit the templates.

Then the Java world moved to templating engines, but it was still the same idea.

Just curious how you are managing this pain point (I am not a Ruby dev so maybe there is a well-known 'best practice' templating approach?).

[ Parent | on HN ]

Re:How Basecamp Next got to be so damn fast without using mu... by dhh on Friday February 17, 2012 @11:07AM (#3603774)

I'm not sure I understand the pain point you're describing. What's "styled HTML"? We're sending HTML across the wire that looks exactly like the HTML we used to render the initial page. It has classes, ids, and custom data descriptors.

We have not experienced any pain doing this.

[ Parent | on HN ]

Re:How Basecamp Next got to be so damn fast without using mu... by rkalla on Friday February 17, 2012 @11:23AM (#3603848)

You answered my poorly-worded question. Thanks.

[ Parent | on HN ]