3 ms·
Well, sometimes is not much that it's poor code but a lot of data to render. For example, imagine rendering a form with 100 elements. If it takes 0.1 second to
by diggan 10y ago
Well, sometimes is not much that it's poor code but a lot of data to render. For example, imagine rendering a form with 100 elements. If it takes 0.1 second to render that on a average computer, you can make that 0.01 by rendering it on the server instead.
- intrasight 10y agoBut your server has to render it for the thousands of visitors to you site. I still don't get the rationale.
- Sanddancer 10y agoSmart rendering would involve using a mostly static template that's updated with the relatively few dynamic elements as the page is being readied to be sent over the wire. If 90% of your dynamic content is the same, why put that through your app processes at all?
- intrasight 10y agoStatic stuff is static at either end, and doesn't add to rendering time.
- jeremiep 10y agoAnd then you can cache it. Whats the point of downloading megabytes of javascript, calling 80 different endpoints and then generating what could've been statically saved from the beginning and sent in a single request?