We brought back the Internets first search engine Archie [video]
youtube.com
youtube.com
FTP is the best. Invaluable when building a system from the ground up, starting from only a minimal rootfs and a compiler, building GNU make and then all the software one needs. FTP allows one to retrieve source code tarballs without the need for DNS and the hassle of compiling an SSL library and making sure certificates are up-to-date (because so-called "tech" companies forced seemingly every website to disable http access and redirect http to https). I compile systems from source. I do not rely on binary packages and package managers.
https://web.archive.org/web/20090223180617if_/http://mywiki....
But in 2024, it is exceedingly difficult to use HTTP without TLS to download all the source code that is _still_ found on FTP servers.
It's not FTP, the protocol, that is the best. It is the _option_ of having something else to use besides HTTPS, third party-controlled "web PKI" and for-profit "developer platforms" in order to download source code.
Having that simpler, non-commercial option is the best. IMHO.
Actually, you don't need to manage certificates when we access sites over https as that is done on the server side. You just need to ensure that you are using the latest version of the SSL libraries when compiling systems.
Even then, most certificate providers give you ways to update certificates quickly and easily. If you do it correctly then you would only need to update them once a year. (you can set this to a longer duration)
- Suramya
The new eats the old and thats change you need to embrace.