pdev

V<T> : T would be so helpful!  So would ext methods which allow a ref this <Type> <name>

Its always good to see an interview with a Turing Award recipient.  Good interview guys.

@vesuvius

Breaking the web seems like a worse issue than it is.  Infact, IE8 already contains the solution for this.  If the browser detects insecure scripting it could block the actions and indicate to the user that they may want to reload the site in compatibility mode.

@LordKain

Web browsers run on all kinds of devices today, from pcs to mobiles and fridges.  Because of this there is a strong need to abstract the code from the underlying system.  This means that even if you were to compile C++ for a special web environment, there would still need to be a layer of abstraction such as virtual machices or JIT.  With Silverlight and Flash both having GPU support now, and the progressive increases in speed, the only advantage C++ on the web would have is language preference.  Also its worth pointing out the impossibility of creating an accepted standard for how such a language would work across browsers.

"Gazelle leaps ahead of all current browsers with the principal approach because there is no dependable way to execute code in the Gazelle kernel (so there can be no process hijacking or remote code execution on the host machine - code only runs in the context of a principal and this can include more than one process in context -)"

Chromium (chromes base) is separated into two protection domains.  These are a browser kernel and rendering engine.  The rendering engine domain runs in a restricted sand box environment.  Web pages and plugins are both executed in the rendering engine domain which means they have restricted access to your system.  As with Gazelle, all communication to the kernel is done via a tight API proxied through IPC.  From what I can tell, Gazelle offers no specific improvements over chrome in this area.

However Gazelle does shine!  Gazelle puts serious priority on DOM and script interaction which is in desperate need of improvement in all current browsers.  I definitely look forward to further information on this project in the future.

As for my chrome links, this area really interests me but companies are still fairly hush about what they're doing.  Chrome is the exception to this, which is why I posted the links.  There is a lot of valuable information there for anyone interested in this sort of thing.

Interesting topic and good video.  If you liked it, you might want to also check docs on google chrome:

http://dev.chromium.org/developers/design-documents/process-models
http://dev.chromium.org/developers/design-documents/multi-process-architecture
http://dev.chromium.org/developers/design-documents