News for hackers. Stuff that matters.

A comment on Never connect to ProtonMail using Chrome. Parent comment

Re:Never connect to ProtonMail using Chrome by anfilt on Monday November 19, 2018 @10:16PM (#18491585)
It's just an example of how much weight Google is able to throw around. That's a just one part of what would be needed for a browser. The more parts you add the harder it becomes to build a browser.

Also I have read about QUIC there are some things that are interesting about it. However, there are things that I don't like.

Moreover, this was something I read from IETF mail archive: "That QUIC isn't yet proven. That's true, but the name won't be formalised or used on the wire until the RFC is published, so we have a good amount of time to back away. Even then, if it fails in the market, we can always skip to HTTP/4 one day, if we need to."[1]

I find that pretty concerning. If it does not pan out we can just skip over. That's still something someone has to implement even it's not used much. I would only be considering things that people in general are eager to use not just a few big companies.

[1] https://mailarchive.ietf.org/arch/msg/quic/RLRs4nB1lwFCZ_7k0...

[ Parent | on HN ]
Re:Never connect to ProtonMail using Chrome by rgbrenner on Tuesday November 20, 2018 @02:57AM (#18492429)
That's still something someone has to implement even it's not used much.

Not true. This is why alpn and the upgrade header exist. You do not need to implement any of the new protocols, and you can certainly skip a version if you don't think it's worth the effort.

[ Parent | on HN ]