Can someone explain the difference between the process / thread architecture of chrome and firefox desktop apps and the implications of this difference? On MacOS Chrome appears as many processes named Chrome helper or something, whereas Firefox appears as a single process with many threads. Given that the two are trying to solve the same problem and are so superficially similar, is the difference in architecture surprising?