It's an implementation detail. It's not the "//" that matters, it's that web browsers weren't offering reasonable abstractions; so this weird detail affected mo

It's an implementation detail. It's not the "//" that matters, it's that web browsers weren't offering reasonable abstractions; so this weird detail affected more people than it should have. These days, you can type "foobar" instead of http://www.foobar.com/ http://www.foobar.com/ in any browser, and it works. The "//" isn't a big deal. There's more that browsers could be doing. Why ever display "<anything>://" in a browser, when it could be a menu of protocols?