3 ms·
No one is going to read your blog with netcat or just curl into a pager. Idk, maybe we should revive the world of information served raw over TCP or telnet. H
by nitrogen 6y ago
No one is going to read your blog with netcat or just curl into a pager.
Idk, maybe we should revive the world of information served raw over TCP or telnet. HTTP is out of control.
- giantrobot 6y agoIn what way do you think HTTP is out of control? Before you reply please keep in mind JavaScript web apps don't have anything to do with HTTP.
- nitrogen 6y agoOk, "out of control" is a slight exaggeration, but HTTP has become a complete reimplementation of what amounts to TCP or SCTP.
- giantrobot 6y agoAgain, in what way? TCP is making sure data gets where it's going and there were no errors introduced by the transmission. A raw TCP socket doesn't have any metadata about what the data is that's coming over the socket. There's a reason the Application layer exists in the first place. You can make an argument that HTTP should be replaced with another application later protocol but just raw sockets everywhere is ridiculous. HTTP has eaten the world of application layer protocols because it is flexible and expressive. It's also relatively easy to implement and there's lots of good FOSS server packages available. Most servers make it really easy to plug in back end applications. Combine that with ubiquitous HTTP clients and it's a super low barrier to entry. You're not going to replace that ecosystem easily and you definitely won't replace it with raw sockets.