3 ms·
That works until you have (like the example) 20k titles. That's a performance hit to the (assuming) database to send all of that data at once, to the web server
by dpcx 9y ago
That works until you have (like the example) 20k titles. That's a performance hit to the (assuming) database to send all of that data at once, to the web server for having to parse all of those results and generate the HTML, to the client browser for having to parse all of that HTML and render it. It's possible, of course, that it's better for the user. It just doesn't happen to be that way very often, from my own anecdotal experience.
- deleted 9y ago[deleted]
- dzhiurgis 9y agoIs it tho? It's probably half the size of any JS framework or library out there. Yes, it can be slow if you wrap each line in tons nested HTML, inefficient CSS and tons of JS handlers, but it doesn't have to.