Re: [whatwg/url] Consider removing the `gopher` special-case. (#342)

> Would you also argue that once we drop support for FTP, we start parsing those URLs differently?

Yes. I can't think of a good reason to treat protocols that user agents don't actually understand differently than other protocols that user agents don't understand. We don't have special processing for `ssh:`, for instance, and I'd suggest that that's more widely used than `gopher:`.

> I guess I don't care too strongly either way, but it seems a little strange just in order to get rid of lookup entry.

It's certainly not much code, and has little practical impact either way. But removing it will mean that I never have to reassure myself that Chromium's net stack doesn't actually support Gopher even through `kGopherScheme` is defined in Chromium's URL library, nor will `gopher:` come up when discussing UI treatment of various schemes in the context of various stages of [HTTP BAD](https://blog.chromium.org/2017/04/next-steps-toward-more-connection.html) with good folks like @estark37.

It's cruft that seems very safe to remove.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/342#issuecomment-322749421