I've been playing with remix for a couple of days now, I think this cache strategy could work for me. So far the worst thing about remix is not having a clear story about hosting, which adds a lot of friction compared to the triangle company.
Love the simple, easy to follow example. Too bad e-tags in distributed environments (using load balancers) is harder (probably still possible). If all your requests are going to a single server then it seems awesome. For static assets/content (marketing pages etc) this seems great
Well, if the response would be the same the etag will be the same. So even if every request goes to a different server, the etags will still work exactly the same
13:47 Not sure if the 90 bytes was the data sent from the server to the browser or the the other way round. The size of the response headers should be 90B, no? Or is it both request and response put together? Because it says "90B transferred over the network".
Awesome vid. Learned a lot! Btw, when do we have to put the 'must-revalidate' header? Also, will we be able to configure a global headers that will apply for every page with Remix? Thanks!
Hey ryan. Can I please request you to enable keycastr on screen. I am used to vim. But would like to see what commands you are using. I am sure I might learn something there too.
The headers function gives you the hand to include whatever http header(s) you want. I don't think Remix is designed to decide on anyone's caching strategy, and that's probably why they're coming up with this api
you are an S-tier teacher
It is that type of video which you download and save to playlist and watch every month. It's gold
This was just great to watch. Amazing video Ryan!
Thank you!
I've been playing with remix for a couple of days now, I think this cache strategy could work for me. So far the worst thing about remix is not having a clear story about hosting, which adds a lot of friction compared to the triangle company.
Amazing explanation and demo
OK. I finally learned how these work today. :)
This is amazing!
I'm learning a ton here about Web essentials
is there any way to manually revalidate the response like click on a refresh button.
Love this. Thanks for the explanation as well as the demo
13:03 Was that a reference to "I'm Thinking of Ending Things" ? Great movie.
Hey, we all need the deep dive after the introduction to http caching! I have an idea: Expose the caching Michael wrote for unpkg!
I'm so stoked for the release!
This guy is good at teaching, he should start a training company.
This was really good thanks !
Love the simple, easy to follow example.
Too bad e-tags in distributed environments (using load balancers) is harder (probably still possible).
If all your requests are going to a single server then it seems awesome. For static assets/content (marketing pages etc) this seems great
Well, if the response would be the same the etag will be the same. So even if every request goes to a different server, the etags will still work exactly the same
13:47 Not sure if the 90 bytes was the data sent from the server to the browser or the the other way round. The size of the response headers should be 90B, no? Or is it both request and response put together? Because it says "90B transferred over the network".
TODO: test this and report back.
Important info well presented, nice!
great explanation ! loved it !
Awesome vid. Learned a lot! Btw, when do we have to put the 'must-revalidate' header? Also, will we be able to configure a global headers that will apply for every page with Remix? Thanks!
♥
Hey ryan. Can I please request you to enable keycastr on screen. I am used to vim. But would like to see what commands you are using. I am sure I might learn something there too.
All day Winston 🤣
13:03 I’m thinking of ending things! Lol
Fellow Charlie Kaufman fan?
suicide joke :O
Noticed the same thing, are you OK Ryan?
awesome :D
What is the font.
Does the Etag / if-none-match also come included with Remix headers() function?
The headers function gives you the hand to include whatever http header(s) you want. I don't think Remix is designed to decide on anyone's caching strategy, and that's probably why they're coming up with this api
stupid question but how does the ${Array.from} work inside the html?
He wrote the HTML string inside a template literal. Notice the backticks before and after the HTML code.
developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals
allDayWinston 😆
Fourth!
First
WITCHCRAFT :o
second