Explore >> Select a destination
|
You are here 
|
shortdiv.com | ||
| | | | |
byroot.github.io
|
|
| | | | | I want to write a post about Pitchfork, explaining where it comes from, why it is like it is, and how I see its future. But before I can get to that, I think I need to share my mental model on a few things, in this case, HTTP/2. | |
| | | | |
www.debugbear.com
|
|
| | | | | Server-side rendering ensures that website content appears quickly, without first having to download and run application code. | |
| | | | |
sookocheff.com
|
|
| | | | | Note: To make this easier to read (and write), h1 may be used in place of HTTP/1, and h2 may used in place of HTTP/2. HTTP/1 has a long and storied history. Originally developed as a sixty page specification documented in RFC 1945, it was designed to handle text-based pages that leverage hypermedia to connect documents to each other. Typical web pages would kilobytes of data. For example, the first web page was a simple text file with web links to other text documents. Now, the web is made up of media-rich sites containing images, scripts, stylesheets, fonts, and more. The size of a typical web page is measured in megabytes rather than kilobytes, and the number of requests required to assemble a full page can be over one hundred. The reality of how web pages... | |
| | | | |
bitsofco.de
|
|
| | | Articles on frontend development and more. | ||
