3 ms·
>I'm of the mindset that code written 20 years ago should run today. Given that chrome didn't exist 20 years ago, this seems like a fairly absurd position to a
by notatoad 7y ago
>I'm of the mindset that code written 20 years ago should run today.
Given that chrome didn't exist 20 years ago, this seems like a fairly absurd position to apply to this situation. No code from 20 years ago relies on chrome having ftp support.
- read_if_gay_ 7y agoThe number 20 is probably an upper bound.
- gnfurlong 7y agoChrome didn't exist 20 years ago, but you can trace its lineage back that far. Khtml dates back to 1998 apparently.
- tim58 7y agoWeb browsers existed 20 years ago. We should be able to visit and use a website written in 1999 on any modern browser.
- notatoad 7y agoand you can. but an FTP dump is not a website, and a browser not having native support for non-http protocols does not break websites. FTP links will still work, they just won't be displayed in a browser anymore. People are blowing this way out of proportion, as if FTP is some critical underpinning of the web or web browsers are a critical part of FTP. Web browsers have always been terrible FTP clients, anybody who uses FTP on a regular basis uses a better client. The most tangible impact of this change is to give grumpy internet commenters something to complain about.