3 ms·
The name is the reason. You see, it is the File Transfer Protocol. Do you need to transfer a file? Use the protocol designed to transfer files! Why would you
by jiggawatts 4y ago
The name is the reason.
You see, it is the File Transfer Protocol.
Do you need to transfer a file? Use the protocol designed to transfer files! Why would you use something silly like a Hypertext protocol for binary!?
I see similar conflation of the name-vs-reality all the time.
My favourite is the “secure” network that is differentiated not by firewall access policy, but by name only. Literally just a label.
- wruza 4y agoDo you need to transfer a file? Use the protocol designed to transfer files! Why would you use something silly like a Hypertext protocol for binary!? Because it’s faster with http, doesn’t require firewall/nat trickery at either side, is secure out of box via https, can be easily gui-ed via index plugin, cached via a proxy/cdn, supports “moved elsewhere” and other issue reporting. And if you ignore that “Hypertext” word that is there historically and look at http as just a metadata+data transfer protocol, it is clearly superior to ftp for any sort of data transfer.
- jiggawatts 4y agoIt's a pity there's no font-style for sarcasm, like italic or bold...