https://en.wikipedia.org/wiki/Heartbleed
(I mean, I'm not overjoyed at the deprecation of FTP support because I used it just yesterday, but let's at least be honest here. The protocol might be decades old but the implementations aren't necessarily, and if they're being actively maintained there's always the possibility of introducing new bugs.)
That's not the "stable protocol that's been around for decades" situation that FTP is in.
That is literally the point I was making when I said, "if they're being actively maintained there's always the possibility of introducing new bugs."
Moreover, just because a library had its last fix a decade (or whatever) ago is no guarantee that unfixed bugs do not lie undiscovered in it.
Many protocols evolve not by being replaced by incrementally better point releases, but rather by being supplanted entirely by a better designed alternative.
FTP effectively evolved into HTTP for this use case, and scp/sftp for the authenticated file transfer use case.
and there are other bugs in the implementation which further demotivates the FTP support.
To me that reads as there are bugs in Chrome's implementation of FTP.
Did you take that to mean the author intended to convey the message that the FTP protocol has bugs?