> Chrome developers are crap developers and they hide behind processes because they don't have the chops to do threads. This might undermine the rest of your a

> Chrome developers are crap developers and they hide behind processes because they don't have the chops to do threads. This might undermine the rest of your argument. Chrome developers are pretty damn sharp, and they use processes so they can add features the fastest while maintaining the best security profile (and record). But I agree with your overall point. I'm saddened by the need for the browser to suck up more and more of my computer's resources - more gigabytes of ram, more cores - in order to enable web developers to develop ever-flashier applications faster. The balance has swung way too far, web applications (and even static content sites) need to be less flashy, and spend more time on reasonably sane implementations and libraries. I'm also sad that Firefox is pressured into just doing what Chrome does. But I can understand, they don't see an alternative, they have to "keep up" with websites and user bases that can't be trusted.