You saw the same arguments when the Python Cryptography library started adopting Rust to replace memory-unsafe C code in their C library. People running, like, DEC Alphas in their basements for sport were furious. It was on the front page of HN for several days. It blew over, because nobody really cares about those people in a durable, meaningful way.
Same situation with FTP. It's dead. Stick a fork in it.
Absolutely not the same situation. There are numerous mentions in this very thread about industries / sectors that still heavily rely on FTP. There's hundreds of millions of dollars worth of contracts that rely on data being transferred using that protocol. This isn't people enjoying retro computing. This is day-to-day operations.
And they'll make do without Firefox and Chrome, just like the DEC Alpha in the basement didn't explode when the Cryptography team moved away from C.
For whatever it's worth: those industries should not be relying on FTP. FTP is bad. But I'm not advocating to ban it from the Internet; rather, I'm just saying, nobody should make software security compromises of any sort to continue supporting it.
It's commercial infrastructure, not a fetish.
You saw the same arguments when the Python Cryptography library started adopting Rust to replace memory-unsafe C code in their C library. People running, like, DEC Alphas in their basements for sport were furious. It was on the front page of HN for several days. It blew over, because nobody really cares about those people in a durable, meaningful way.
Same situation with FTP. It's dead. Stick a fork in it.