>>107598087
Sure you could, but why would you?

>>107598087

Eh, why though?

>>107598609
>>107598638
op please respond

>>107598087
JSON is also shit.
Still using HTTP 1.1.
Not using webp.

>>107598087
it can't

I don't want to do your homework for you, but think about a body that is larger than your RAM

[
    {
        "tagName": "!doctype",
        "html": true
    }, {
        "tagName": "html",
        "lang": "en",
        "children": [
            {
                "tagName": "head",
                "children": [{
                    "tagName": "title",
                    "children": [
                        "JSON replacing HTTP demo"
                    ]
                }]
            }, {
                "tagName": "body",
                "children": [{
                    "tagName": "h1",
                    "children": [
                        "JSON instead of HTTP is so very much better and more readable, too."
                    ]
                }]
            },
        ]
    }
]

>>107599792
Not OP but are you alluding to HTTP/2 streaming / HTTP/1.1 chunked transfer encoding? Not sure I'm following, it's still TCP so the body is sent in segments that the client could receive and process one at a time and then discard while the total size exceeds the size of main memory, no

>>107598087
>properly structured json