3 ms·
> Heck HTTP isn't even the hard part anyways Wait until you read about HTTP upgrade mechanisms, HTTP transfer encodings or even 206 Partial Content implementat
by cookiengineer 5y ago
> Heck HTTP isn't even the hard part anyways
Wait until you read about HTTP upgrade mechanisms, HTTP transfer encodings or even 206 Partial Content implementations that are broken everywhere.
HTTP 0.9 was easy to implement, but everything starting from 1.1 and upwards is borderline insane, especially SPDY and QUIC.
While I don't agree with gemini's design decisions (and neither with gopher's), I can fully understand their point of view in regards to unnecessary complexity and side effects of network states.
Source: Building a peer to peer Web Browser, for around 2 years already (still far away from usable).
- zamadatix 5y agoAs I said just because a web browser may support a lot of things doesn't mean your simple subset client/server has to. I have no doubt implementing HTTP/2, HTTP/3 and its QUIC revisions, SPDY and its revisions, and every extension and option known in the specs would be a lot of work. Not doing so doesn't require making an alternative protocol. You're still free to implement a subset of HTTP/1.1 just like you're free to not implement Javascript or WebGPU when making a simple HTML browser. You want to TOFU certs? Go ahead, HTTPS isn't going to stop you. You want to use client side certs even though most websites don't? Go ahead, HTTPS supports you. You want to use a custom port? Go ahead, HTTPS supports you. You want to leave some features out? Go ahead, you don't have to implement every feature Chrome supports