8 ms·

Hi all. Just wanted to tell you that a lot of people working on Firefox are here and we really appreciate your word of mouth support and feedback. This year i

Hi all. Just wanted to tell you that a lot of people working on Firefox are here and we really appreciate your word of mouth support and feedback. This year is going to be huge for us as we're wrapping up the part about reducing technical debt and start gearing toward using our new superpowers to innovate. We need your help to stay relevant (market share), improve quality (report bugs, write test cases), and improve (lots of code in Firefox is easy to hack on as we move a lot of UI to HTML/JS - like devtools).

Chirael 10y ago
This is great to read/hear. I'll put my vote in for two things. 1) Performance, performance, performance; this is what originally caused me to use Chrome a lot more, the perception of quick-to-open tabs and snappy responsiveness. 2) Privacy; this is something Google almost by definition can't compete on, because their business model depends on providing something free in exchange for user data (the opposite of privacy). A third important consideration of course is "not crashing" or at least if there is a crash, containing it to the offending tab - this is why I'm very happy to read about the progress of multi-process Firefox! Keep up the great work guys.
- smw 10y ago
  My only serious problem with firefox is that a single tab can lock up the entire application. Otherwise, the performance _and_ memory usage is fantastic. But that one issue is enough to keep me away from it most of the time.
  - cpeterso 10y ago
    Multiple tab processes (aka "e10s-multi") should be shipping in Firefox 54 (now in the Firefox Nightly channel). The initial rollout of multi-process Firefox ("e10s") had one process for the browser UI and one process for all tabs (and a separate process for sandboxing Flash), so one bad tab could lock up all your tabs but your browser UI would still be responsive so you could close the bad tab. e10s-multi will increase the number of shared tab processes to two or more, balancing tab isolation vs memory overhead. In the meantime, you can test more tab processes by increasing the "dom.ipc.processCount" pref in about:config. I set my process count limit to 999. :)
    - kristofferR 10y ago
      I've heard a lot of people say that, but I'm still having problems with a single tab locking up the whole browser for 5-40 seconds on FF 53.0a2 Dev Edition with e10 and process count at 999.
    - smeehee 10y ago
      Hmm… I'd look but there don't seem to be any builds since late November on mozilla.debian.net.
    - Jonnax 10y ago
      I had a look a week or so ago at e10s, but it seemed that because my laptop was a touch screen laptop (Dell XPS 13) the feature was disabled. The UI said it was due to accessibility features. Is there a timeline for getting it working with touch screens or has that already happened?
  - fencepost 10y ago
    While that's theoretically true, I've never switched from Firefox as my daily driver and crashes are very rare in my experience (more common on mobile, but I leave a bunch of stuff open there as well). Furthermore, when it does crash the session restore does a pretty solid job of restoring and letting me easily exclude tabs from being restored.
- zbraniecki 10y ago
  Hey, thank you for your input. We are aware of the importance of those three things. They're all not-trivial problems to solve, but we're working on all three: 1) Performance is an insanely complex problem. We can't easily measure the "real" performance, in a scientific way. We can measure performance of so called "microbenchmarks" which can tell you that, for example, our JavaScript engine can perform X million regular expression computations per second. The X may be higher or lower than what Chakra or V8 can, but how it translates to real world experience is insanely complicated. What we know by now is that JS engine performance is not the problem. At this point all modern engines are fast. What we need to advance are things like performance of DOM, CSS, layout, painting and prioritization (ability to ensure that UI performance cannot be blocked by website's JS computations). We're working hard on several projects this year, under the umbrella of codename "quantum" that is aiming at making Firefox blazingly fast. We're taking lessons and code from Servo and applying it in Firefox. The end result, if we succeed, is that we'll have ability to perform DOM, layout, CSS and painting orders of magnitude faster (even if it's 2x it's still huge!). The other piece of performance, is what's called perceived performance. That one is even more tricky because it's all about what your brain tells you. In cognitive psychology and HCI there are tons of studies that prove that depending on how we use tricks like animation, colors, shapes and gimmicks like focus, we can trick your eye to think that things are faster or slower. Chrome is really good at that and kudos to them! I love watching their UI painting order in 120fps slow-mo just to see all the things they employed. Together with Quantum we're going to look into ways to improve the perceived performance of Firefox. I hope we'll get it right :) 2) On the privacy front we're working with Tor browser and we're also working on several projects aiming at disrupting the current way of browsing the Internet. Read about Firefox+Tor browser and Activity Streams if you're interested. 3) On the QA front, we've made major progress over the last year. That's a huge part of the technical debt that we had to remodel in 2016. We now have much better fuzzers, tests and APIs that makes it easier to write code that will not break. On top of that, multi-process helps us make sure that painting crash doesn't crash your browser, that plugins can't crash your browser and finally that content can't crash your browser. We also designed a whole new language that is significantly better suited to write security critical code than C++ is. It's called Rust and we just started moving pieces of our engine to it. If we can succeed with this, we should end up with a codebase of the unprecedented stability for a project this size and facing third-party code. If you're interested, read about Mozilla Oxidation project. It is a major bet. We're betting on JS, we're betting on Rust. We're betting on Gecko and our ability to "change the engine mid-flight". I'm excited about the opportunity, but it's going to be a huge effort to pull it off. If any of this is interesting for you, help us! We're a small team (compared to all other browser engines), but we have a culture that fosters community participation and I believe that we can compete and shape the Web together: https://whatcanidoformozilla.org/ https://whatcanidoformozilla.org/
- RileyKyeden 10y ago
  I finally switched to Firefox when it dawned on me why Chrome for Android has no plugins, and why they went silent about the reading mode. With Firefox, I can install uBlock Origin, and it's had a reading mode for a while. Google wants to force me to look at ads that make the page slow to load, bouncy, and hard to scroll through. Google is where Microsoft was not long ago: engaging in self-destructive user-hostile behavior to protect their profit center. It can't work forever.
  - caleblloyd 10y ago
    I also switched to Firefox Mobile on Android over a year ago. Couldn't be happier with the extension support. I've got uBlock Origin and my password manager installed. Chrome is definitely smoother on mobile but using extensions is worth it for me. Does Firefox Mobile's codebase closely match that of the desktop browser? Are their release schedules similar? Wondering if we should see it speed up with Firefox's latest improvements.
    - kbrosnan 10y ago
      Firefox for Android is the exact same codebase as desktop Firefox. Many Gecko features are turned on for Firefox for Android at the same time as desktop. In other cases either Firefox for Android or desktop will have features before the other. For example Firefox for Android had HTML date/time picker support years before desktop because the OS provided widgets. In the other direction EME has been on desktop for a while and is in the works for Firefox for Android.
    - cpeterso 10y ago
      Yes. Firefox for Android uses the same Gecko engine and release schedule as Firefox for Windows, Mac, and Linux desktop. They all share most of the same code in the same source code repository [1]. Most of Mozilla's "Quantum" project to start importing Servo code into Gecko will also run on Android. Firefox for iOS has its own release schedule and shares only a little code (e.g. Firefox Accounts sync for browser history/bookmarks) with the other Firefoxes. [1] https://hg.mozilla.org/mozilla-central/file/tip/widget https://hg.mozilla.org/mozilla-central/file/tip/widget
- dandare 10y ago
  If I could cast my vote it would be 1) perception of quick-to-open tabs and snappy responsiveness, 2) everything else. I just could not stand how unresponsive Firefox used to be.
bitL 10y ago
Can you make a paid version of Firefox (identical to the free one)? I'd buy if it were for $25, or even give you $50/year subscription to keep you afloat.
- auscompgeek 10y ago
  You can always donate at https://donate.mozilla.org/ https://donate.mozilla.org/.
  - bambax 10y ago
    Donations don't replace paying options, that's a grave error. Companies can't "donate" (or it's super difficult) because their accountant will yell at them. Offer something that can be bought and written down on a proforma.
  - bambax 10y ago
    Donations don't replace paying options, that's a grave error. Companies can't "donate" (or it's super difficult) because their accountant will yell at them. Offer something that can be bought and written down on a proforma.
- c0nducktr 10y ago
  Someone on the Firefox subreddit mentioned that one of the ideas which is being considered is offering a privacy-centric VPN service for people who donate. I think that would be a great benefit for subscribers, and a neat way for Mozilla to set Firefox apart from other browsers.
  - neon_electro 10y ago
    In the meantime, Cloak is doing a good job providing a paid product that meets this need: https://www.getcloak.com/ https://www.getcloak.com/ (I'm a satisfied customer)
    - vopi181 10y ago
goalieca 10y ago
i switched to firefox about two years ago after having been on chrome since 2008 (The very first release). At first i was really impressed with chrome and its speed and stability and UI. But firefox has much improved and is now the privacy candidate. I've also switched to duckduckgo. I'm jumping right off the google hype train because i feel that their business is to mine mine.
cybernytrix 10y ago
Thanks for working in Firefox. It is so much better than where it was whe Chrome first shipped and I switched to Firefox (and also to DDG thanks to AMP). There are two issue that bug me a lot and I use FF on Mac. The back swipe behavior is not so great and enabling browser.snapshots.limit is buggy. I feel it is also slower rendering and scrolling.
tornadoboy55 10y ago
You should make Firefox feel native to each platform and follow its conventions, instead of trying to have a sort of unifying 'Firefox look' that feels out of place everywhere. Using platform-specific enhancements (like VideoToolBox on macOS for example) also would go a long way. Edit: most important of all is battery life though. Your browser can be super smooth, have all the nice extensions in the world and be FOSS, but if it cuts battery life in half everyone will hate it.
- Vinnl 10y ago
  Heh, while I see your point to some extent, you can't really argue there's any (popular) browser that does this better than Firefox :)
  - TheCoreh 10y ago
    Chrome _used_ to, a long time ago.
oxide 10y ago
I'll never be switching back to Chrome. I've gone back and forth over the years and have made Firefox my home base. You folks have made a lifelong supporter out of me the hard way, by earning my respect over the years. besides that, I support the project in general, the developers and the competition. when I installed Firefox on a friends phone with uBlock Origin added on, he loved it. p.s. that reminds me, when I was a teenager I installed Firefox for the first time. My mother insisted it was a virus and would yell at me to "remove that mozzerella fox virus IMMEDIATELY and quit installing your mIRC virus!"
arviewer 10y ago
I still prefer Firefox over Chrome or Safari, and push it to everyone I can. Thanks for all the good work! Sometimes it looks like Chrome takes over the web like IE did ten years ago. I hope you can withstand this trend.
baybal2 10y ago
Firefox is useless now. The only way to save it is to disolve mofo
garaetjjte 10y ago
Please don't kill extenstions. (I'm talking about real extensions, not limited WebExtensions)
nl 10y ago
I switched to Firefox a year or two ago. It hasn't been smooth. Chrome is faster and has better dev tools. Ads have caused significant lock ups, to the point where I was forced to install uBlock against my wishes. Nevertheless I've persisted. But the thing that continually pushes me towards switching back to Chrome is this bug[1]. It affects every single Mac user I've met, is trivially easy to confirm and yet sits there. On the positive side, the Firefox syncing works well across machines, so that is nice. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1234356 https://bugzilla.mozilla.org/show_bug.cgi?id=1234356
tajen 10y ago
Every time I try to use Firefox, I feel driven away by the web developer tools. I can't exactly pinpoint what makes me unease, I don't think that's only about habits, it feels like the FF dark background makes them harder to read or the font is too big. I'm talking about quite simple usecases: Browsing the DOM and CSS, reading warnings in the JS console, reading Ajax requests. Have you ever tried to compare the ergonomics of the dev tools between Chrome and FF? Do most people like FF's current dev tools?
- sp332 10y ago
  There are three themes built-in: dark, light, and "Firebug".
- pmontra 10y ago
  I like Firebug much more than the native dev tools, I think it has a better UI/UX. They are merging now. Firebug was one of the reasons I was using Firefox so I hope they keep the best parts of the two tools. I don't use Chrome much so I can't really tell how good it is for developers. If its dev tools are similar to the ones in Opera (same engine) they look closer to Firebug than to FF dev tools.
iandanforth 10y ago
I really wanted to try out a WebVR project last night and the only reason I got to 'Hello world' was because of nightly, so thanks for that!
cptskippy 10y ago
I've used Firefox as my primary browser since it was called Phoenix. I appreciate all you guys have done in the past couple releases, particularly Electrolysis, and I can't wait until it's always on.
smeehee 10y ago
I recently switched from Firefox to Vivaldi due to the upcoming dependency on PulseAudio. Depending on what happens, I may end up switching back; but if I do, I expect support for ALSA either by default, a run-time option or a compile-time switch.
MohammadLee 10y ago
Thank you for your great work. For me, security is by far the most important selling point. Firefox is a bit late to the party but not that far behind Chrome, as we can see on the competitions and bug bounties (a Chrome 0day is worth more than a Firefox 0day). Please continue to improve the sandboxing, the website permission model for APIs, the security of extensions (auto reviews, permission model), the binary hardening via compilation options, etc. etc. Privacy is good but if any website/ISP/government can compromise your browser, what good is it to not send the URLs you visit to Google? Performance for sure is important but that's not a criteria for me. Again, different user profile I guess!

Chirael 10y ago

This is great to read/hear. I'll put my vote in for two things. 1) Performance, performance, performance; this is what originally caused me to use Chrome a lot more, the perception of quick-to-open tabs and snappy responsiveness. 2) Privacy; this is something Google almost by definition can't compete on, because their business model depends on providing something free in exchange for user data (the opposite of privacy). A third important consideration of course is "not crashing" or at least if there is a crash, containing it to the offending tab - this is why I'm very happy to read about the progress of multi-process Firefox! Keep up the great work guys.

smw 10y ago
My only serious problem with firefox is that a single tab can lock up the entire application. Otherwise, the performance _and_ memory usage is fantastic. But that one issue is enough to keep me away from it most of the time.
- cpeterso 10y ago
  Multiple tab processes (aka "e10s-multi") should be shipping in Firefox 54 (now in the Firefox Nightly channel). The initial rollout of multi-process Firefox ("e10s") had one process for the browser UI and one process for all tabs (and a separate process for sandboxing Flash), so one bad tab could lock up all your tabs but your browser UI would still be responsive so you could close the bad tab. e10s-multi will increase the number of shared tab processes to two or more, balancing tab isolation vs memory overhead. In the meantime, you can test more tab processes by increasing the "dom.ipc.processCount" pref in about:config. I set my process count limit to 999. :)
  - kristofferR 10y ago
    I've heard a lot of people say that, but I'm still having problems with a single tab locking up the whole browser for 5-40 seconds on FF 53.0a2 Dev Edition with e10 and process count at 999.
  - smeehee 10y ago
    Hmm… I'd look but there don't seem to be any builds since late November on mozilla.debian.net.
  - Jonnax 10y ago
    I had a look a week or so ago at e10s, but it seemed that because my laptop was a touch screen laptop (Dell XPS 13) the feature was disabled. The UI said it was due to accessibility features. Is there a timeline for getting it working with touch screens or has that already happened?
- fencepost 10y ago
  While that's theoretically true, I've never switched from Firefox as my daily driver and crashes are very rare in my experience (more common on mobile, but I leave a bunch of stuff open there as well). Furthermore, when it does crash the session restore does a pretty solid job of restoring and letting me easily exclude tabs from being restored.
zbraniecki 10y ago
Hey, thank you for your input. We are aware of the importance of those three things. They're all not-trivial problems to solve, but we're working on all three: 1) Performance is an insanely complex problem. We can't easily measure the "real" performance, in a scientific way. We can measure performance of so called "microbenchmarks" which can tell you that, for example, our JavaScript engine can perform X million regular expression computations per second. The X may be higher or lower than what Chakra or V8 can, but how it translates to real world experience is insanely complicated. What we know by now is that JS engine performance is not the problem. At this point all modern engines are fast. What we need to advance are things like performance of DOM, CSS, layout, painting and prioritization (ability to ensure that UI performance cannot be blocked by website's JS computations). We're working hard on several projects this year, under the umbrella of codename "quantum" that is aiming at making Firefox blazingly fast. We're taking lessons and code from Servo and applying it in Firefox. The end result, if we succeed, is that we'll have ability to perform DOM, layout, CSS and painting orders of magnitude faster (even if it's 2x it's still huge!). The other piece of performance, is what's called perceived performance. That one is even more tricky because it's all about what your brain tells you. In cognitive psychology and HCI there are tons of studies that prove that depending on how we use tricks like animation, colors, shapes and gimmicks like focus, we can trick your eye to think that things are faster or slower. Chrome is really good at that and kudos to them! I love watching their UI painting order in 120fps slow-mo just to see all the things they employed. Together with Quantum we're going to look into ways to improve the perceived performance of Firefox. I hope we'll get it right :) 2) On the privacy front we're working with Tor browser and we're also working on several projects aiming at disrupting the current way of browsing the Internet. Read about Firefox+Tor browser and Activity Streams if you're interested. 3) On the QA front, we've made major progress over the last year. That's a huge part of the technical debt that we had to remodel in 2016. We now have much better fuzzers, tests and APIs that makes it easier to write code that will not break. On top of that, multi-process helps us make sure that painting crash doesn't crash your browser, that plugins can't crash your browser and finally that content can't crash your browser. We also designed a whole new language that is significantly better suited to write security critical code than C++ is. It's called Rust and we just started moving pieces of our engine to it. If we can succeed with this, we should end up with a codebase of the unprecedented stability for a project this size and facing third-party code. If you're interested, read about Mozilla Oxidation project. It is a major bet. We're betting on JS, we're betting on Rust. We're betting on Gecko and our ability to "change the engine mid-flight". I'm excited about the opportunity, but it's going to be a huge effort to pull it off. If any of this is interesting for you, help us! We're a small team (compared to all other browser engines), but we have a culture that fosters community participation and I believe that we can compete and shape the Web together: https://whatcanidoformozilla.org/ https://whatcanidoformozilla.org/
RileyKyeden 10y ago
I finally switched to Firefox when it dawned on me why Chrome for Android has no plugins, and why they went silent about the reading mode. With Firefox, I can install uBlock Origin, and it's had a reading mode for a while. Google wants to force me to look at ads that make the page slow to load, bouncy, and hard to scroll through. Google is where Microsoft was not long ago: engaging in self-destructive user-hostile behavior to protect their profit center. It can't work forever.
- caleblloyd 10y ago
  I also switched to Firefox Mobile on Android over a year ago. Couldn't be happier with the extension support. I've got uBlock Origin and my password manager installed. Chrome is definitely smoother on mobile but using extensions is worth it for me. Does Firefox Mobile's codebase closely match that of the desktop browser? Are their release schedules similar? Wondering if we should see it speed up with Firefox's latest improvements.
  - kbrosnan 10y ago
    Firefox for Android is the exact same codebase as desktop Firefox. Many Gecko features are turned on for Firefox for Android at the same time as desktop. In other cases either Firefox for Android or desktop will have features before the other. For example Firefox for Android had HTML date/time picker support years before desktop because the OS provided widgets. In the other direction EME has been on desktop for a while and is in the works for Firefox for Android.
  - cpeterso 10y ago
    Yes. Firefox for Android uses the same Gecko engine and release schedule as Firefox for Windows, Mac, and Linux desktop. They all share most of the same code in the same source code repository [1]. Most of Mozilla's "Quantum" project to start importing Servo code into Gecko will also run on Android. Firefox for iOS has its own release schedule and shares only a little code (e.g. Firefox Accounts sync for browser history/bookmarks) with the other Firefoxes. [1] https://hg.mozilla.org/mozilla-central/file/tip/widget https://hg.mozilla.org/mozilla-central/file/tip/widget
dandare 10y ago
If I could cast my vote it would be 1) perception of quick-to-open tabs and snappy responsiveness, 2) everything else. I just could not stand how unresponsive Firefox used to be.

bitL 10y ago

Can you make a paid version of Firefox (identical to the free one)? I'd buy if it were for $25, or even give you $50/year subscription to keep you afloat.

auscompgeek 10y ago
You can always donate at https://donate.mozilla.org/ https://donate.mozilla.org/.
- bambax 10y ago
  Donations don't replace paying options, that's a grave error. Companies can't "donate" (or it's super difficult) because their accountant will yell at them. Offer something that can be bought and written down on a proforma.
- bambax 10y ago
  Donations don't replace paying options, that's a grave error. Companies can't "donate" (or it's super difficult) because their accountant will yell at them. Offer something that can be bought and written down on a proforma.
c0nducktr 10y ago
Someone on the Firefox subreddit mentioned that one of the ideas which is being considered is offering a privacy-centric VPN service for people who donate. I think that would be a great benefit for subscribers, and a neat way for Mozilla to set Firefox apart from other browsers.
- neon_electro 10y ago
  In the meantime, Cloak is doing a good job providing a paid product that meets this need: https://www.getcloak.com/ https://www.getcloak.com/ (I'm a satisfied customer)
  - vopi181 10y ago

goalieca 10y ago

i switched to firefox about two years ago after having been on chrome since 2008 (The very first release). At first i was really impressed with chrome and its speed and stability and UI. But firefox has much improved and is now the privacy candidate. I've also switched to duckduckgo. I'm jumping right off the google hype train because i feel that their business is to mine mine.

cybernytrix 10y ago

Thanks for working in Firefox. It is so much better than where it was whe Chrome first shipped and I switched to Firefox (and also to DDG thanks to AMP). There are two issue that bug me a lot and I use FF on Mac. The back swipe behavior is not so great and enabling browser.snapshots.limit is buggy. I feel it is also slower rendering and scrolling.

tornadoboy55 10y ago

You should make Firefox feel native to each platform and follow its conventions, instead of trying to have a sort of unifying 'Firefox look' that feels out of place everywhere. Using platform-specific enhancements (like VideoToolBox on macOS for example) also would go a long way. Edit: most important of all is battery life though. Your browser can be super smooth, have all the nice extensions in the world and be FOSS, but if it cuts battery life in half everyone will hate it.

Vinnl 10y ago
Heh, while I see your point to some extent, you can't really argue there's any (popular) browser that does this better than Firefox :)
- TheCoreh 10y ago
  Chrome _used_ to, a long time ago.

oxide 10y ago

I'll never be switching back to Chrome. I've gone back and forth over the years and have made Firefox my home base. You folks have made a lifelong supporter out of me the hard way, by earning my respect over the years. besides that, I support the project in general, the developers and the competition. when I installed Firefox on a friends phone with uBlock Origin added on, he loved it. p.s. that reminds me, when I was a teenager I installed Firefox for the first time. My mother insisted it was a virus and would yell at me to "remove that mozzerella fox virus IMMEDIATELY and quit installing your mIRC virus!"

arviewer 10y ago

I still prefer Firefox over Chrome or Safari, and push it to everyone I can. Thanks for all the good work! Sometimes it looks like Chrome takes over the web like IE did ten years ago. I hope you can withstand this trend.

baybal2 10y ago

Firefox is useless now. The only way to save it is to disolve mofo

garaetjjte 10y ago

Please don't kill extenstions. (I'm talking about real extensions, not limited WebExtensions)

nl 10y ago

I switched to Firefox a year or two ago. It hasn't been smooth. Chrome is faster and has better dev tools. Ads have caused significant lock ups, to the point where I was forced to install uBlock against my wishes. Nevertheless I've persisted. But the thing that continually pushes me towards switching back to Chrome is this bug[1]. It affects every single Mac user I've met, is trivially easy to confirm and yet sits there. On the positive side, the Firefox syncing works well across machines, so that is nice. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1234356 https://bugzilla.mozilla.org/show_bug.cgi?id=1234356

tajen 10y ago

Every time I try to use Firefox, I feel driven away by the web developer tools. I can't exactly pinpoint what makes me unease, I don't think that's only about habits, it feels like the FF dark background makes them harder to read or the font is too big. I'm talking about quite simple usecases: Browsing the DOM and CSS, reading warnings in the JS console, reading Ajax requests. Have you ever tried to compare the ergonomics of the dev tools between Chrome and FF? Do most people like FF's current dev tools?

sp332 10y ago
There are three themes built-in: dark, light, and "Firebug".
pmontra 10y ago
I like Firebug much more than the native dev tools, I think it has a better UI/UX. They are merging now. Firebug was one of the reasons I was using Firefox so I hope they keep the best parts of the two tools. I don't use Chrome much so I can't really tell how good it is for developers. If its dev tools are similar to the ones in Opera (same engine) they look closer to Firebug than to FF dev tools.

iandanforth 10y ago

I really wanted to try out a WebVR project last night and the only reason I got to 'Hello world' was because of nightly, so thanks for that!

cptskippy 10y ago

I've used Firefox as my primary browser since it was called Phoenix. I appreciate all you guys have done in the past couple releases, particularly Electrolysis, and I can't wait until it's always on.

smeehee 10y ago

I recently switched from Firefox to Vivaldi due to the upcoming dependency on PulseAudio. Depending on what happens, I may end up switching back; but if I do, I expect support for ALSA either by default, a run-time option or a compile-time switch.

MohammadLee 10y ago

Thank you for your great work. For me, security is by far the most important selling point. Firefox is a bit late to the party but not that far behind Chrome, as we can see on the competitions and bug bounties (a Chrome 0day is worth more than a Firefox 0day). Please continue to improve the sandboxing, the website permission model for APIs, the security of extensions (auto reviews, permission model), the binary hardening via compilation options, etc. etc. Privacy is good but if any website/ISP/government can compromise your browser, what good is it to not send the URLs you visit to Google? Performance for sure is important but that's not a criteria for me. Again, different user profile I guess!