I'm personally fine with this. FTP is a different protocol, just like BitTorrent. It's not part of the modern web, so it's just another loose end to tie up. Even though it will be around for a while, it's not relevant to Chrome's user audience/usecase.
I'm not fine with this. I'm of the mindset that code written 20 years ago should run today. This is a breaking change on a critical piece of internet infrastructure. Google, by nature of operating the most popular web browser, has a moral obligation to the community to provide a stable environment. There are something like 10^9 webpages out there. How many of these will become less accessible because of this change?…
So you would have cp/m, MS-DOS, PDP-11 RSX-11M, Coherent, Vax VMS, old broken compilers for dead languages, IBM 360 TOS (yes, tape operating system), IBM 360 DOS, Sigma 5 Real-Time-Batch monitor, autocoder, 1401 software, Palm OS?
But for the love of all that is Balloons and Seashells, why?
More to the point--did Chrome have FTP 20 years ago? No, it did not.
In my opinion, they should have never put it there in the first place.