The fact that we'd have to look it up is why it was removed. I haven't used FTP in at least a decade—scp does the trick for my server management needs, HTTP is sufficient for download-only use cases, and Dropbox-style applications have supplanted FTP for shared files. FTP is more general than any of these three replacements, but it isn't ideal for any one of the use cases.
To name a few, I interact with a number of sites on shared hosting that have been using FTP for years. I also work with a data server that primarily interfaces with its data store through FTP. It also used to be easier to just host an FTP server and manage its access independent of a website, but still link to it in a browser where people who are not technically inclined could browse and interact with files without needing a separate dedicated client. Even for me, it would be simpler to just see an FTP file listing in a browser sometimes
The point is that browsers used to be able to browse the Internet, but major players such as Google have been working hard to limit all of these things to just HTTPS. Excusing things away by saying "well I don't use it, so it's useless" has only helped to narrow this path