4 ms·
This reminds me of the tragic situation where if you process XHTML locally using XML tools that incidentally fetch the DTD, then things block and become absolut
by frou_dh 6y ago
This reminds me of the tragic situation where if you process XHTML locally using XML tools that incidentally fetch the DTD, then things block and become absolutely dirt slow, because the W3C sysadmins are permanently pissed off by that: https://stackoverflow.com/a/13865692/82 https://stackoverflow.com/a/13865692/82
- treve 6y agoJust the other day I was looking for a full XHTML DTD to find the list of built-in entities and was so surprised about the speed. This explains a lot!
- habitue 6y agoThis is great. It's a perfect solution too, because it's not super long, but it's long enough that nobody is going to go into production without figuring out how to cache it
- zo1 6y agoTo be fair - it seems that caching in general when it comes to web-resources has been neglected collectively on the web. Two big factors include Web 2.0 and the rise of Youtube which actively fought to have their content un-cacheable via normal software & existing mechanisms.