Quote:
Originally Posted by Alex
Oh, didn't know they were touting that.
I'm going to hope they fail regardless. I don't need the added headache of another major browser to consider for testing and design.
|
I read one opinion that thinks it'll drive web developers to better practices. Not only is it going to spawn individual processes per page, but it will supposedly have its own process manager (I don't think that's implemented yet, but I could just be missing it). So you'll be able to immediately, from within the browser, spot and kill memory-hog/leaking pages. The writer of that opinion is hopeful that it will lead to people being more careful about their java and other in-page apps since the browser will now be calling them out to the user.
I don't think the average user is going to be savvy enough for that to be much of a factor.