GµårÐïåñ wrote:Yeah in my view Fx is dead browser walking and I foresee that it will go the way of other browsers that got hyped and then died off. Addons like NS and RP are the only reason I stick with it and even then its only about 30% of the time, I use my own builds of Chromium original source so I don't have to deal with Google's Chrome version which pushes their own services and yet have a browser that has enough source modulation to allow me to tighten it up a bit. I have tried to do the same with Mozilla but its codebase is such a mess and a patch work of crap upon crap that I gave up trying to build anything unique out of that mess. For example, Collusion, does absolutely NOTHING for me, because NS castrates everything so well, it has nothing to show.
A few comments:
1. I agree what is said in this thread about Collusion. It's a joke. I want to block cookies (particularly from trackers), I don't want to watch them
2. IMO, the rant about FF and the rapid release process is exaggerated. Yes, it's really a pity that Electrolysis is put on hold, and yes, FF 4 was horrible, but since then FF has improved a lot (e.g. the
MemShrink project).
3. Regarding FF vs. Chrome: I still prefer FF because it's considerably more configurable (there's hardly anything in about:config which you can NOT change/tweak); many addons are still better and more reliable than their Chrome counterparts (ScriptNo is definitely inferior to Noscript, the Chrome ABP version is not yet on par with the FF one, and the same is true for Autopager - just to name some examples.) Several aspects in Chrome are not as controllable as in FF (see also what I wrote
here), e.g., you can not disable DOM Storage (I know, I know there is a switch for that - but if you use it most Chrome addons don't work anymore so it's unusable). And yes, the Chrome sandbox (or rather sandbox
es if you're using Ubuntu) is definitely a good thing and I hope that FF will have it, too, before long. However, with FF tightly confined in its Apparmor profile in Ubuntu I feel safe without a sandbox. On the other hand, I regard the risks from XSS and Clickjacking rather high (actually higher than malware trying to break out of a sandbox or Apparmor). While Chrome has a built-in XSS filter, there is nothing against Clickjacking. Noscript is still the only protection against this. Besides, Google is one the few monopolies which try to dominate the Internet, and Chrome is one tool for them to achieve this. If everyone is using their browser, they are free to define web standards as they suit
them - and not necessarily
us. Therefore, it's also a political decision which browser to use.
4. Regarding the Mozilla Review Process: What you wrote contradicts to what Giorgio
said about it:
In fact, the review process has been improved and tightened a lot during the past years, for instance:
an automatic scanner checks for many known buggy, unsafe, and/or malicious coding patterns
editors are all picked among expert extension developers and must audit the code of the extension, rather than just checking that it works as advertised and doesn't exhibit malicious behavior
in case of doubt, the mandatory review performed by "ordinary" editors escalates to a super-review to be made by an AMO administratos
This doesn't mean a 100% guarantee that a malicious or buggy extension can't be published on AMO, but is significantly better than any other web-based software repository that I know (including Google's Chrome Extensions vault and Apple's Apps marketplace).