-
 KDE-Apps.org Applications for the KDE-Desktop 
 GTK-Apps.org Applications using the GTK Toolkit 
 GnomeFiles.org Applications for GNOME 
 MeeGo-Central.org Applications for MeeGo 
 CLI-Apps.org Command Line Applications 
 Qt-Apps.org Free Qt Applications 
 Qt-Prop.org Proprietary Qt Applications 
 Maemo-Apps.org Applications for the Maemo Plattform 
 Java-Apps.org Free Java Applications 
 eyeOS-Apps.org Free eyeOS Applications 
 Wine-Apps.org Wine Applications 
 Server-Apps.org Server Applications 
 apps.ownCloud.com ownCloud Applications 
--
-
 KDE-Look.org Artwork for the KDE-Desktop 
 GNOME-Look.org Artwork for the GNOME-Desktop 
 Xfce-Look.org Artwork for the Xfce-Desktop 
 Box-Look.org Artwork for your Windowmanager 
 E17-Stuff.org Artwork for Enlightenment 
 Beryl-Themes.org Artwork for the Beryl Windowmanager 
 Compiz-Themes.org Artwork for the Compiz Windowmanager 
 EDE-Look.org Themes for your EDE Desktop 
--
-
 Debian-Art.org Stuff for Debian 
 Gentoo-Art.org Artwork for Gentoo Linux 
 SUSE-Art.org Artwork for openSUSE 
 Ubuntu-Art.org Artwork for Ubuntu 
 Kubuntu-Art.org Artwork for Kubuntu 
 LinuxMint-Art.org Artwork for Linux Mint 
 Arch-Stuff.org Art And Stuff for Arch Linux 
 Frugalware-Art.org Themes for Frugalware 
 Fedora-Art.org Artwork for Fedora Linux 
 Mandriva-Art.org Artwork for Mandriva Linux 
--
-
 KDE-Files.org Files for KDE Applications 
 OpenTemplate.org Documents for OpenOffice.org
 GIMPStuff.org Files for GIMP
 InkscapeStuff.org Files for Inkscape
 ScribusStuff.org Files for Scribus
 BlenderStuff.org Textures and Objects for Blender
 VLC-Addons.org Themes and Extensions for VLC
--
-
 KDE-Help.org Support for your KDE Desktop 
 GNOME-Help.org Support for your GNOME Desktop 
 Xfce-Help.org Support for your Xfce Desktop 
--
openDesktop.orgopenDesktop.org:   Applications   Artwork   Linux Distributions   Documents    LinuxDaily.com    Linux42.org    OpenSkillz.com   
 
Apps
News
Groups
Knowledge
Events
Forum
People
Jobs
Register
Login

-
- News . 
0
votes
click to vote up

process separation


Published Feb 27 2013 via RSS

When Google Chrome first came out sporting its process separation feature where each tab is in its own process, it was broadly hailed as the best thing ever. The idea was to increase stability and security. 

This was during a time when Plasma Desktop was still facing a number of implementation hurdles that impacted stability. So a number of well-meaning people decided that I should be informed about this revolutionary new idea in Chrome and every component in Plasma Desktop should be put into its own process.

This was applying a solution from one problem space to another that just didn't map at all. For technical reasons it was not feasible and I offered alternatives. Still, there was a good year or so when pretty much every single day I would get at least one message from someone suggesting we redesign Plasma to be separated across different processes. Some were kinder than others, but after a while even the nicest of people sounded like fingernails on a chalkboard.

Since then we've moved on to the alternative approaches we identified well before Chrome was even available: interpreted rather than compiled code. Today we're walking with both feet into the brave new world of QML. As of Qt5 we have QML2 which brings with it scene graph based rendering that can be done in hardware where available and a runtime that makes writing beautiful interfaces that are also stable very easy. It has been a long road to this point and has involved countless dozens of bright people working hard.

In the meantime, how is that process separation in Chrome working out? Here's the conclusion of one analysis based on actually measuring things: "The [process separation] mechanism is based on a relatively dated concept, superseded by compile-time code validation techniques such as Google's own Native Client [..] 
An unintended consequence of this design is that all attempts to synchronize the state between two processes are inevitably very expensive. [..] It seems that the apparent improvements in the stability of Chrome come at a very significant cost; and that unless the architecture is revised substantially, it may hinder the development of tightly-integrated and highly responsive web apps."

I don't hold quite so dim a view of process separation used in the right places as one might come away with after reading that article, but it is a cautionary tale about believing in silver bullets. Different problems are different and very few design concepts carry only benefit with no cost.



BackRead original postSend to a friend

Add comment

Add comment
Show all posts




-
 
 
 Who we are
Contact
More about us
Frequently Asked Questions
Register
Twitter
Blog
Explore
Apps
Jobs
Knowledge
Events
People
Updates on identi.ca
Updates on Twitter
Facebook App
Content RSS   
Events RSS   

Participate
Groups
Forum
Add App
Public API
About GTK-Apps.org
Legal Notice
Spreadshirt Shop
CafePress Shop
Advertising
Sponsor us
Report Abuse
 

Copyright 2007-2014 GTK-Apps.org Team  
All rights reserved. GTK-Apps.org is not liable for any content or goods on this site.
All contributors are responsible for the lawfulness of their uploads.