Live data from Hacker News

Update on Multi-Process Firefox

blog.mozilla.org

61–70 of 175 posts

Re: Update on Multi-Process Firefox

#61
Has anyone noticed bookmarklets not working when multi-process is turned on?

I installed a V 51 developer edition to test out multi-process, and when multi-process was on, my bookmarks that modify the dom did not work. Any one else noticed anything similar?

Re: Update on Multi-Process Firefox

#62
post #7
post #3

Does firefox run each tab in its own process yet? Or live inside a sandbox? I switched from firefox + noscript to chrome after accepting that firefox's security (even with noscript enabled) was just so far behind that of chrome.

Isn't this exactly what the article explains and clarifies?

Yes but why bother actually reading the article when you can shoot off in the comments with minimal effort? If you're wrong, someone will correct you. Amirite?

Re: Update on Multi-Process Firefox

#63
post #38

Earlier quoted context omitted.

First of all, by common measurements Firefox's market share is more like 13.5% [1], not the 4% you mentioned. According to that link Firefox is the #2 browser, ahead of Microsoft and Apple's browsers. Second, Mozilla is a non-profit, so the incentives are different that the usual ones. Basically Mozilla wants to help the open web. A 13.5% browser can do that in many ways: drive new standards, provide an alternative t…

Thanks. That makes sense. I guess I just wasn't clear that Mozilla had unusual "non-capitalistic" goals.

One could say that having an open source alternative based on standards could actually allow for a more fair plainfield for online businesses. To be frank although I use several Google services and products , I try to use opem source alternatives as much as I can.

Re: Update on Multi-Process Firefox

#64

Make Vimperator great again - still no support. :'( Two year old github issue but yet any development to be seen or reported :/

You know what they say, pull requests are the new feature requests...

But yeah, I'd love to see vimperator or pentadactyl supporting this, and no, I neither have the time nor the skillset to fix it myself.

Re: Update on Multi-Process Firefox

#65
post #2

I force-enabled multi-process FF a while ago and haven't had any issues. In the 49.x series there were one or two tab crashes, but I can't think of any recently. All of my extensions have worked just fine too.

I'm missing just two. "cli-get" and "Live HTTP Headers". It's the former I really miss. The latter was occasionally useful for debugging stuff.

Re: Update on Multi-Process Firefox

#69

Is this done in Chrome as early as 8 years ago? https://blog.chromium.org/2008/09/multi-process-architecture...

Chrome was built from scratch around this concept. Firefox wasn't, and there's a whole wealth of infrastructure around the non-multiprocess approach, from the way plugins work, all the way on up. Migrating towards multi-process has been a decidedly non-trivial task for Mozilla, involving a lot of effort from a lot of people.

Re: Update on Multi-Process Firefox

#70

Earlier quoted context omitted.

Firefox has more than a 4% market share[0][1]. One of the main reasons I've heard, is that it's free, and that the Mozilla Foundation is a non-profit. I also just found this bit, that explains how some browsers might be over or under estimated, because of how their internals work[2]. So we really don't know what the market shares really are. [0] http://gs.statcounter.com/#browser-ww-yearly-2008-2016 [1] https://www.w…

Oh. I guess the source I used was garbage. I just typed in Firefox browser share on google and looked at the first result and it looked legit. It seems their share is shrinking quite fast though.

Using a Google to check the marketshare of a product rival to Google's Chrome. It's interesting how important Google Search is and how powerful it could be. (BTW I certainly don't imply Google's algorithms are skewed)
Post reply on HN