WebKit2 API Layer Brings Split-Process Model 95
99BottlesOfBeerInMyF writes "Anders Carlsson and Sam Weinig over at Apple just announced WebKit2, a rework of the WebKit engine that powers Chrome and Safari. This new version of WebKit incorporates the same style of split-process model that provides stability in Chrome, but built directly into the framework so all browsers based upon WebKit will be able to gain the same level of sandboxing and stability. AppleInsider has a writeup, and the team has provided 'high level documentation' as well. Both Palm and the Epiphany team are going to be happy about this."
Re:I'm going to predict the future. (Score:3, Insightful)
The next "big thing" will be some dipshit who writes an HTML rendering engine using nothing but JavaScript and HTML5 canvas.
Nope, canvas clearly isn't the right choice. If some dipshit were to seriously consider this, they'd use OpenGL.
Just because this is how the Web community does things, that JavaScript/HTML5/canvas browser will in turn get a new scripting language that's even shittier than JavaScript is.
First: Where's your evidence that this is how the Web community does things? I honestly can't remember the last time I wrote a scripting language within a scripting language in anything at all related to web development.
Second: What, exactly, is shitty about JavaScript? Most people who think JavaScript is shitty don't understand it. It's actually a very nice language, albeit with a few ugly quirks.
Soon it'll be hyped even more than Ruby on Rails, AJAX and Cloud Computing were.
Nope, because as much as you'd like to believe otherwise, each of those things actually has something of value to contribute to the world. You may not like Rails, but it did remind everyone that MVC is a Good Idea, and new Web frameworks generally include at least that concept. AJAX allows applications to run in the browser -- again, like it or not, that's something which has value. Cloud computing, in either sense -- whether you're talking about web apps keeping your data, or utility computing -- again have something to contribute.
What does your hypothetical browser contribute? It does the exact same thing as everything we have, only slower and shittier. (And before you claim that this is how web apps work, how, exactly, could I safely run an application without installing it before now? Again, it actually has some positive points, whether or not they're things you want -- your idea has none.)
Managers around the world will force their developers to rewrite all of their web sites and web apps to target this new shitty scripting language and browser.
I don't know any managers who have suggested something so stupid with the current generation.
Re:Why is this tagged 'Apple'? (Score:5, Insightful)
Like GP said, WebKit is basically just the work of the KHTML devs. Apple leeched off of their work.
If by 'leeched' you mean they took an existing open project, modified and extended it, then released that work for free. I guess if you redefine leech then yes they leeched it.
Re:Yay! Sandboxes! (Score:3, Insightful)
IMHO of course :)
Re:Is there a sandbox for sandbox? (Score:3, Insightful)
"Unless your program is screwing up my system..."
In what way is a process hang *not* screwing up my system?
List of ways it's potentially screwing up my system:
- It's consuming CPU and not doing anything useful.
- It's consuming RAM and not doing anything useful.
- It's stopping me from doing actual work in it.
His point is that the only time the end user should see a process manager is if you fucked up... Admittedly programmers tend to fuck up an awful lot – this programming thing is *really* hard to get right, but the general point is right. A user shouldn't see the process manager unless a program has fucked up.
Re:Yay! Sandboxes! (Score:2, Insightful)
Are you absolutely sure it's not Flash/PDF/[Silver/Moon]light plugins that are freezing Chrome?
Wait, hang on, what's the difference in a plugin freezing Chrome and the problem described by GP? He says a tab can hang and then sometimes all the other tabs die too, to the end user who cares if it's technically caused by a plugin or not?