On Sat, Oct 9, 2010 at 8:50 PM, Paul D. Fernhout <[email protected]> wrote: > On 10/9/10 3:45 PM, Dirk Pranke wrote: >> >> C++ is a significant security concern; and it is reasonable to want a >> browser written in a memory-safe language. >> >> Unfortunately, web browsers are large, extremely >> performance-sensitive, legacy applications. All of the major browsers >> are written in some combination of C, C++, and Objective-C (and >> undoubtedly assembly in isolated areas like the JITs), and it's >> unclear if one can reasonably hope to see a web browser written from >> scratch in a new language to ever hope to render the majority of the >> current web correctly; the effort may simply be too large. I was not >> aware of Lobo; it looks interesting but currently idle, and is a fine >> example of this problem. >> >> I continue to hope, but I may be unreasonable :) > > Yes, that seems like a good description of the problem. > > How about this as a possibility towards a solution ...
I think I'd rather try to write a browser from scratch than debug/maintain your solution ;) Also, re: running Chrome in VirtualBox, are you aware that the page renderers are already run in sandboxed execution environments? It's unclear how much more protection each page in a separate VM would really buy you. -- Dirk _______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
