@mjackson @brianleroux @jaffathecake @kelseyhightower @mikesherov @steren @Netlify @remix_run Aha! I see the challenge you are referring too! I was a bit thrown by "it’s impossible to cache HTML"
Since every deploy persists forever on a unique URL I bet there is an approach to address this. I'll noodle on it.
(here's my blog as it was in 2016 https://57b8db8dd6865d5bcf4684db--hawksworx.netlify.app/)
@jaffathecake @csswizardry @bdc @sarah_edo Gotcha. Comms aside, do you have what you need via the _headers config in @Netlify which allows you to control the cache behaviour on given paths to get the behaviour you'd prefer on some projects?
If so, I can talk comms here.
If not, could you help me understand the gaps?
If so, I can talk comms here.
If not, could you help me understand the gaps?
@jaffathecake @csswizardry @bdc @sarah_edo As in, for very many small assets it gets expensive relatively speaking since the browser checks to see if it can used its cached version for lots and lots of items and that overhead mounts up?
@jaffathecake @csswizardry @bdc @sarah_edo I full second! Oh, I admit to being surprised at that level of overhead for the 304s which should be very fast. I need to explore that example more.
@jaffathecake @csswizardry @bdc @sarah_edo Aha. So this is mostly a communication thing? That's most helpful feedback. Things have certainly moved on since that 2015 blog post. Even this one back in 2017 offers a bit more info on our defaults and I doubt we'd still say "more assets is best"
https://www.netlify.com/blog/2017/02/23/better-living-through-caching/
https://www.netlify.com/blog/2017/02/23/better-living-through-caching/
@jaffathecake @csswizardry @bdc @sarah_edo Gotcha!
I'm not Captain Cache Config but I've lived through enough cache horrors to want good defaults that deliver high confidence and good performance. Equally, for those with the wisdom to take on full config of their caches, I'd like to learn what primitives that needs.
I'm not Captain Cache Config but I've lived through enough cache horrors to want good defaults that deliver high confidence and good performance. Equally, for those with the wisdom to take on full config of their caches, I'd like to learn what primitives that needs.
@jaffathecake @csswizardry @bdc @sarah_edo What would be your preferred best default behaviour for all use cases?
@mjackson @kelseyhightower @mikesherov @steren @Netlify You can get a few more details about how browsers re-use previously cached assets from the @Netlify CDN, and how this is configurable if you want, from this post on the Netlify blog:
https://www.netlify.com/blog/2017/02/23/better-living-through-caching/
https://www.netlify.com/blog/2017/02/23/better-living-through-caching/
@mjackson @kelseyhightower @mikesherov @steren @Netlify (this is technically what Netlify does behind the scenes when a deploy includes unchanged assets)
We don't purge assets from the CDN, we direct traffic to ensure latest assets are served and keeps your deploys atomic. (But you can tell browsers to cache as you like)
We don't purge assets from the CDN, we direct traffic to ensure latest assets are served and keeps your deploys atomic. (But you can tell browsers to cache as you like)
@mjackson @kelseyhightower @mikesherov @steren @Netlify You can set the headers to tell browsers to cache assets, including html (found on any paths you specify) for whatever period you like. It sounds like you want to not have atomic deploys so that you can mix updated assets with previous assets on the CDN
@kelseyhightower @mikesherov @mjackson @steren ...and as for @Netlify being "bad at caching", the Jamstack model allows us to apply default cache-busting behaviours which are perfect for the vast majority of use cases, but you have granular control over caching if you need it and know how to wield it.
https://docs.netlify.com/routing/headers/#multi-value-headers
https://docs.netlify.com/routing/headers/#multi-value-headers
@kelseyhightower @mikesherov @mjackson @steren Meanwhile an important misunderstanding to clear up is Michael's comment that Jamstack is bad for caching strategies. The opposite is in fact true. When the UI can be atomically pre-generated, it enables very sensible strategies.
@kelseyhightower @mikesherov @mjackson @steren Yeah there is some helpful feedback there. Keen to refine the messaging to make it more clear and helpful.
The efforts continue!
The efforts continue!
@opinionatedpie @vuejs @vite_js @bencodezen "Made" is over stating it. I had previously stocked up thanks to @Tzmanics encouragement.
https://www.the-teashed.co.uk/
https://www.the-teashed.co.uk/
I came to learn about @vuejs and @vite_js from @bencodezen but his examples triggered me to making bubble tea and ordering ramen.
Not the worst.
Not the worst.
I basically want Ben to teach me everything https://twitter.com/bencodezen/status/1377681669092732928
@zachleat @sarah_edo @kenny_io @PaulieScanlon @Netlify @cassidoo I approve this message.
(if not the leading)
(if not the leading)
@miliardopiscrat @bencodezen @cassidoo Psst I think muddling up @Shopify and @Spotify is the source of bigger problems 😘