dblohm7

86 ms·

931.
by dblohm7 12y ago
I don't think people are taking issue with the fact that you switched; they're taking issue with your indirect suggestion that Mozilla is taking too long to implement multiprocess.
932.
by dblohm7 12y ago
"one child process that holds all plugins (Flash, Acrobat)." Not true. Each plugin module gets its own plugin container. Flash instances share a separate plugin-container from the one shared by Acrobat instances.
933.
by dblohm7 12y ago
"Sadly Firefox 39 (nightly) still has no real multi process support. There are only two processes, the main process holds all tabs, the single child process 'plugin-container' holds all plugins (Flash, Acrobat, etc.)." T
934.
by dblohm7 12y ago
The single content process is an interim step until electrolysis development is further along.
935.
by dblohm7 12y ago
Mozilla is not dropping NPAPI support. Having said that, we are trying to replace NPAPI plugins whereever we can (PDF.js, Shumway)
936.
by dblohm7 12y ago
That is correct.
937.
by dblohm7 12y ago
If there is a problem, then file a bug! It's an open source browser!
938.
by dblohm7 12y ago
"When you start using a seemingly mature HTML5 api, and find that it doesn't work as expected in all browsers, what recourse does one have?" File bugs. Chromium and Firefox are not black boxes.
939.
by dblohm7 12y ago
That would require them to file bugs against the browser. In the case of the sparse array issue, nobody had filed anything until a Mozillian read about the issue here on HN. It was fixed in Nightly the same day.
940.
by dblohm7 12y ago
How Google Inbox shares 70% of its code across Android, iOS, and Chrome FTFY
941.
by dblohm7 12y ago
It wasn't tiles that was the problem. It was the reinforced carbon-carbon panels on the leading edge of the wing. That's a little bit more difficult.
942.
by dblohm7 12y ago
I'd also like to point out that, if you read the bugzilla bug, it was fixed on the same day that it was reported! Nobody from Google bothered to file any bugs against Firefox; it wasn't until a Mozilla engineer saw the Google engi
943.
by dblohm7 12y ago
Yet they didn't file a single bug against Firefox!
944.
by dblohm7 12y ago
I think the most telling fact is that Google made zero effort to file bugs against Firefox to help make things work. A Mozilla JS dev fixed the sparse array bug the SAME DAY it was filed. Note that the bug wasn't filed until somebody s
945.
by dblohm7 12y ago
You can help: http://dblohm7.ca/blog/2014/08/14/diffusion-of-responsibilit...
946.
by dblohm7 12y ago
RIM
947.
by dblohm7 12y ago
Like these? https://developer.mozilla.org/en/Apps/Quickstart/Build/Intro...
948.
by dblohm7 12y ago
Perhaps she was somebody who figured out that writing books and consulting about interviews and recruiting was more lucrative? I'm not about to doubt somebody's credentials because she saw and opportunity and took it.
949.
by dblohm7 12y ago
Unless it favors them.
950.
by dblohm7 12y ago
In this case they can be deleted, and furthermore are eventually replaced by tiles containing thumbnails from your own browsing history, just as they are now.
951.
by dblohm7 12y ago
Have you filed any bugs for it?
952.
by dblohm7 12y ago
Once again, nobody is denying anything about memory problems. But there are two things at play here: 1. One person's experience is not universal. With a web browser as customizable as Firefox, there will be certain configurations causi
953.
Quality Software Costs Money – Heartbleed Was Free(queue.acm.org)
94 points by dblohm7 12y ago|70 comments
954.
"Mozilla cannot fix 100% of the bugs that we do not know about."(dblohm7.ca)
4 points by dblohm7 12y ago|0 comments
955.
by dblohm7 12y ago
That's like selling your car because you came back from an auto show and didn't like the manufacturer's concept car.
956.
by dblohm7 12y ago
> two tabs open no plugins and it crashes on a machine with 16Gb of ram if left open over night, and the bug is trivial to reproduce Keep in mind that whatever the bug is, it's probably only trivial to reproduce for you . If it tru
957.
by dblohm7 12y ago
Like using their search engine to promote Chrome?
958.
by dblohm7 12y ago
If you're having problems, consider trying the Gecko Profiler ( https://developer.mozilla.org/en-US/docs/Mozilla/Performance... ) and attaching a profile to a bug. We can't fix what we don't know
959.
by dblohm7 12y ago
Coming soon! https://wiki.mozilla.org/Security/Sandbox
960.
by dblohm7 12y ago
And yet, now we hear people complaining that everybody should just run WebKit, while at the same time whining about needing to hack around IE6.

More ›