News for hackers. Stuff that matters.
Re:Scalability by tptacek on Wednesday August 03, 2011 @08:53AM (#2840926)
Every browser does that. Virtually all the problems that matter are internal to the browser.
Re:Scalability by zobzu on Wednesday August 03, 2011 @09:40AM (#2841078)
thats not true. FF 3.6 and before that did not compartment it per tab.

Likewise for IE, but they're per process like Chrome now.

Not sure about other webkit browsers and Opera, it's likely other wekbit browsers (except safari) do not do that.

Re:Scalability by tptacek on Wednesday August 03, 2011 @09:44AM (#2841095)
I can't follow what you're trying to say here. I'm probably just misunderstanding you. Someone suggested that Firefox had memory segmentation, and just did it with threads. That's obviously not accurate. Then you said, "they have it, just with javascript objects". What mainstream browser allows javascript in a tab to access objects in any other page, let alone another tab?
Re:Scalability by icebraining on Wednesday August 03, 2011 @10:10AM (#2841205)
Depends on what JS it is. Obviously websites can't, but a huge part of Firefox is coded in JS, which runs with high privileges. It's perfectly possible that tab specific trusted JS code (including possibly extensions code) wasn't compartmentalized and now is.
Re:Scalability by tptacek on Wednesday August 03, 2011 @04:15PM (#2842850)
Sure! Just keep in mind that a lot of that "trusted JS" is actually just a thin wrapper around C/C++ code, and the C/C++ code tends to be where the problems arise.