Chrome 63: Site Isolation, extension blocking and TLS 1.3

Finally. Chrome's multi-process architecture is insanely great because it separates rendering from UI from networking from graphics from... etc., but people always incorrectly talk about how it protects one website from another by separating them into different processes, when this isn't actually how it works (particularly if you are actually using the tab feature, in which case you have so many tabs that Chrome constantly shares processes).

The reality is that not only do I already have a tab associated with my one critical service--email--in every single renderer process, but attackers can pretty trivially force a tab with any website they want to end up in their process. The way this feature is understood by random people--and the way it is often marketed (which is a big reason people believe this version of how it works)--is finally going to match reality.