5 ms·
Put some numbers up. This whole debate is driven by so much vague thinking and so many unfounded assumptions. What realistic, year 2016 HTML client is so slow
by jhpriestley 11y ago
Put some numbers up. This whole debate is driven by so much vague thinking and so many unfounded assumptions.
What realistic, year 2016 HTML client is so slow that it can't run 100K or so of string interpolation in a millisecond or two? Quite aside from the supposed benefits of performing computation on a server, the idea that web applications are bottlenecked by HTML generation is already absurd.
- falcolas 11y agoMobile Chrome. https://news.ycombinator.com/item?id=11366272 https://news.ycombinator.com/item?id=11366272
- jhpriestley 11y agoHere's a benchmark: http://jsperf.com/dom-vs-innerhtml-based-templating/1079 http://jsperf.com/dom-vs-innerhtml-based-templating/1079 It looks like mobile chrome can perform 500k string interpolations in a second, each one being about 500 bytes. So the time for 100 kilobytes would be approximately half a millisecond.