Using Immutable Caching to Speed Up the Web

Re:Using Immutable Caching to Speed Up the Web by px1999 on Thursday January 26, 2017 @05:53PM (#13496111)

I understand the idea of supporting ranges of libraries from a development perspective, but when you're running something in production, is "use any of these configurations" ever desirable?

Presumably there's a reason that you'd _want_ them to use 1.12.4 over 1.0.0 (or you'd want to at least check that they didn't break anything that you rely on in 1.13 when that comes out)?

[ Parent | on HN ]

Re:Using Immutable Caching to Speed Up the Web by acdha on Thursday January 26, 2017 @09:50PM (#13497329)

It's desirable if you're really focused on performance – if you're not a site like Google/Facebook which people access all the time, it's safe to assume that none of your resources are cached and so you might find n milliseconds of load time a healthy gain (less so now that HTTP/2 is widespread). In many cases it's more likely that you'd know of a bug fixed in a new release – where you'd say libfoo >= 1.12.4 – than that 1.3 has a huge problem.

[ Parent | on HN ]