Hacker News Reader

Comment by simion314 | Hacker News Reader

>Browsers will deprecate plain HTTP sooner or later.

This is a stupid idea, it means the browsers will not be compatible with old websites, if they drop http I hope they would first drop all the other old stuff that are bad and no longer cool.

A big warning should be enough, old websites should still work in a competent browser.

View on HN

> if they drop http I hope they would first drop all the other old stuff that are bad and no longer cool.

They have been doing this. Gopher, FTP, XUL extensions, NPAPI browser plugins, old TLS versions, for examples in the last few years, and alert()/confirm()/prompt() for Chrome's current push.

Worth noting that at the same time, "they" weren't good enough at pushing new things that the same time. For example, all new compression methods work only over HTTPS (actually, this alone can be a reason to switch to HTTPS) - because they were incompatible with some HTTP proxies: https://bugs.chromium.org/p/chromium/issues/detail?id=14801

<rant> I'm actually looking forward for them to drop HTTP digest auth, because it's the only auth scheme which doesn't rely on sending shared secret over the wire with each request </rant>

That is not part of https or html , they also removed RSS , i know some big ego dude wants to add to his CV that he killed http buit I think he should maybe create something more useful(like make sure we can css styule the elements scrollbars so designers won't force me to install a JS library because the scrollbars look like shit and can't customize them to look fine on all browsers or to be more objective see what is the most popular workaround that is used and implement that native (maybe is the calendar, or a better color picker, or native support for modals - run the numbers and not implement stuff thazt only look good on your CV)

Getting rid of notifications would be much nicer than getting rid of http.

Reply on news.ycombinator.com