Ehh, TCP has issues with mobile connectivity and is designed around the idea that 1 logical application stream should map to 1 TCP connection, which causes issues.
But that’s why we’ve got QUIC now.
Other than that though, TCP is fine. If all you need is simple in-order delivery of a stream of bytes it’s hard to beat.
And tell me again exactly what the difference is between a protocol and an api, when both are using software that has not been changed for decades? Just curious.
Besides that, TCP/IP is the worst thing ever for a large network and it only gets worse by the day.
That’s a protocol, not a software library
TCP does what it does pretty well, no need for replacing that which works fine
Ehh, TCP has issues with mobile connectivity and is designed around the idea that 1 logical application stream should map to 1 TCP connection, which causes issues.
But that’s why we’ve got QUIC now.
Other than that though, TCP is fine. If all you need is simple in-order delivery of a stream of bytes it’s hard to beat.
And tell me again exactly what the difference is between a protocol and an api, when both are using software that has not been changed for decades? Just curious.
Besides that, TCP/IP is the worst thing ever for a large network and it only gets worse by the day.
thatsbait.meme
yet you use it every fucking moment, including to post this message.
wow. damn bro. go back to NetBEUI if you’re so fucking l33t.
If I’m going back I’m choosing OSI kthx
my brother in layer 3
jfc look in a mirror dumbass. Who gets this angry over internet protocols and then calls the other party fucking l33t?
lol you’re the genius who decided to talk shit about things they obviously do not understand.
Yes I refered to myself as the other party and have a different username. Doublely dumbass.
oh whoops, I got my assholes confused!
Can’t be easy with your head up your own.
yet there are so many around who keep farting their mouths off.
gotta to block them one at a time I guess.