4 ms·

>>> We’ve been hard at work deploying Brisket to power three of the best and fastest sites on the web — BloombergView.com, BloombergPolitics.com, and BloombergB

>>> We’ve been hard at work deploying Brisket to power three of the best and fastest sites on the web — BloombergView.com, BloombergPolitics.com, and BloombergBusiness.com. Okay so after throwing up a bit at the hyperbole I played around with said sites. They feel fairly slow and loading different sections seems to be random how long it will take to register my click event. UX for showing page loading seems very limited and the differences in times of load for things feels very off. Content sites like the ones Bloomberg mentions should not be done as single page webapps! The problem of rendering pages that have HTML on them has been solved - probably best to leave stuff like Brisket for apps that need it, like stock exchanges or real time analytics.

aikah 12y ago
And those 3 sites render with javascript off(I guess thanks to "isomorphism")... which means they don't need to be single page apps at first place.
- xtrumanx 12y ago
  Which would you prefer, a full page refresh that will refetch a large portion of the page that you're already looking at or an ajax call that will return far less bytes than a full page refresh would have and then replacing only the parts of the page that needs changing? Also if its truly isomorphic, everything would still work as usual if javascript is off.
  - DougWebb 12y ago
    I want the page I'm looking at to be mostly the content I'm interested in, so when I follow a link to get more content most of the page should be updated. Under those conditions, a full page refresh is preferable because it works nicely with the browser history, bookmarking, "Email this Link" feature, and anything else I might want to do with the page of content.
    - xtrumanx 12y ago
      I should have prefaced my original question with "all other things being equal...". I believe you can have browser history, bookmarking, email this link any thing else you might want to do with the page in a single page application and also get the benefit of not doing a full page refresh. Single page application are reletively new and kinks are being worked out but if I could have my cake and eat it too, I wouldn't stand in the way of those trying to make that a reality.
  - duderific 12y ago
    How about loading the whole page on each click, and front caching the parts of the page (nav etc.) that are repeated on each page. This would have really good performance, and be simpler than building a single page app when one isn't really required.
at-fates-hands 12y ago
>>> probably best to leave stuff like Brisket for apps that need it, like stock exchanges or real time analytics. I had the same reaction and was confused, thinking they were going to add a bunch of real time data streams or something. After I re-read the article again, I realized they're not going to use it for something really useful to their industry. Is this a good case for creating something where a need has already been solved a thousand times by several other frameworks?

aikah 12y ago

And those 3 sites render with javascript off(I guess thanks to "isomorphism")... which means they don't need to be single page apps at first place.

xtrumanx 12y ago
Which would you prefer, a full page refresh that will refetch a large portion of the page that you're already looking at or an ajax call that will return far less bytes than a full page refresh would have and then replacing only the parts of the page that needs changing? Also if its truly isomorphic, everything would still work as usual if javascript is off.
- DougWebb 12y ago
  I want the page I'm looking at to be mostly the content I'm interested in, so when I follow a link to get more content most of the page should be updated. Under those conditions, a full page refresh is preferable because it works nicely with the browser history, bookmarking, "Email this Link" feature, and anything else I might want to do with the page of content.
  - xtrumanx 12y ago
    I should have prefaced my original question with "all other things being equal...". I believe you can have browser history, bookmarking, email this link any thing else you might want to do with the page in a single page application and also get the benefit of not doing a full page refresh. Single page application are reletively new and kinks are being worked out but if I could have my cake and eat it too, I wouldn't stand in the way of those trying to make that a reality.
- duderific 12y ago
  How about loading the whole page on each click, and front caching the parts of the page (nav etc.) that are repeated on each page. This would have really good performance, and be simpler than building a single page app when one isn't really required.

at-fates-hands 12y ago

>>> probably best to leave stuff like Brisket for apps that need it, like stock exchanges or real time analytics. I had the same reaction and was confused, thinking they were going to add a bunch of real time data streams or something. After I re-read the article again, I realized they're not going to use it for something really useful to their industry. Is this a good case for creating something where a need has already been solved a thousand times by several other frameworks?