News for hackers. Stuff that matters.
Re:What’s Next for Multi-Process Firefox by anon1385 on Tuesday August 02, 2016 @03:06PM (#12212404)
Are you not aware of how Safari works?

https://trac.webkit.org/wiki/WebKit2

Re:What’s Next for Multi-Process Firefox by cptskippy on Tuesday August 02, 2016 @03:16PM (#12212493)
I am, would you like to clarify whatever point it is that you're trying to make?
Re:What’s Next for Multi-Process Firefox by anon1385 on Tuesday August 02, 2016 @03:25PM (#12212577)
Why are you claiming that Safari uses a single process for everything except plugins?
Re:What’s Next for Multi-Process Firefox by cptskippy on Tuesday August 02, 2016 @04:10PM (#12212960)
I was talking about sandboxing. Multi-process rendering is not the same thing and does not intrinsically sandbox an app or make it more secure.
Re:What’s Next for Multi-Process Firefox by anon1385 on Tuesday August 02, 2016 @05:13PM (#12213464)
But Safari uses multiple processes and sandboxes those processes. You keep claiming that there is some difference between it and Chrome but you can't say what it is.
Re:What’s Next for Multi-Process Firefox by cptskippy on Tuesday August 02, 2016 @05:52PM (#12213691)
Safari is a sandboxed app but that covers everything, I have never read about individual process level sandboxing in Safari beyond the plugin sandbox. Are they using XPC or did they roll something custom?
Re:What’s Next for Multi-Process Firefox by comex on Tuesday August 02, 2016 @06:23PM (#12213901)
WebProcess does have its own, more restrictive sandbox, although it's not as tight as Chrome's:

https://github.com/WebKit/webkit/blob/master/Source/WebKit2/...

For IPC they use something custom (part of the WebKit repo) called "CoreIPC".

Re:What’s Next for Multi-Process Firefox by cptskippy on Tuesday August 02, 2016 @07:10PM (#12214150)
That makes sense given that it's open source.