@ilyess I assumed it was there for many years and not frequently reimplemented, i.e. when other rendering engines or such would require it. It's also much simpler than http.
I also look at boringssl etc. as nice and slim reimplementations of openssl which is meant to cover also archs and corner cases rarely used.. but for ftp/firefox it did not feel worth the trade off. Have not looked at the implementation code wise though.
@globalc makes sense. I haven’t looked at their implementation either, I just assumed that the portion of users using ftp on firefox or chrome was so slim that it didn’t make sense for either browser to keep maintaining it.
@globalc While I definitely do not agree with all the changes that are happening to Firefox (for example Proton, seemingly an attempt at imitating the ugliest design elements from Edge and deprecating the compact theme while making the widgets bigger) I do understand the removal of FTP. FTP was used by everyone on the Internet back in the day, now it's only used directly by nerds/power users like ourselves, and we don't need the web browser for it. All mainstream file managers do FTP now.
@mikeri It's missing in my workflow at least, I often accessed ftp from the browser. I do run KDE, but not it's ftp browsing components, will settle with lftp for now.
Might be interesting to know how much ftp was used, and how big/error prone the implementation was.
@globalc It would be interesting to know about the usage of a lot of stuff that are being changed/removed in Firefox. But judging by the general way the development is going it's clear Mozilla doesn't really care about the power users but wants to appeal to the general mainstream, which is ironic, as the mainstream doesn't really care or know about Firefox anymore.
chaos.social – a Fediverse instance for & by the Chaos community