Slashdot Mirror


Firefox Will Run Chrome Extensions

An anonymous reader writes: Today Mozilla announced some big changes to its extension support. Their new addon API, WebExtensions, is mostly compatible with the extension model used by Chrome and Opera. In short, this means we'll soon see cross-platform browser extensions. They say, "For some time we've heard from add-on developers that our APIs could be better documented and easier to use. In addition, we've noticed that many Firefox add-on developers also maintain a Chrome, Safari, or Opera extension with similar functionality. We would like add-on development to be more like Web development: the same code should run in multiple browsers according to behavior set by standards, with comprehensive documentation available from multiple vendors."

152 comments

  1. Never mind run Chrome extensions... by jez9999 · · Score: 4, Informative

    ... Firefox will be Chrome. Anyone who cared about extensive browser customization will simply abandon their addons. Why keep recoding them on Mozilla's whim?

    For anyone who still cares about this stuff, the time to jump is most certainly NOW. I don't even think SeaMonkey is good enough - Pale Moon is a totally clean break.

    1. Re:Never mind run Chrome extensions... by JackieBrown · · Score: 1

      It looks like they will be supporting the old addons (using XPCOM and XUL) with firefox for at least another year

    2. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      I'm waiting for Pale Moon to release .deb or .rpm packages.

    3. Re:Never mind run Chrome extensions... by jez9999 · · Score: 4, Insightful

      Wow, a whole year. Sorry, where's the good news?

    4. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      Will the new API disallow NoScript-like extension? There is one on Chrome but from my understanding it's kind of hack and can't be 100% effective.

    5. Re: Never mind run Chrome extensions... by Anonymous Coward · · Score: 2, Insightful

      I run Firefox because I can't run add-ons on chrome on my phone and tablet, which is where I do most of my browsing.

    6. Re:Never mind run Chrome extensions... by DarkOx · · Score: 3, Interesting

      FF is a perfect example of a project going completely off the rails. I don't hear anyone saying good things about it anymore.

      It started as an effort to be lighter and faster than the old Mozilla suite. I actually like the mail client, occasionally use composer to put something together quickly and Chatzilla is fine IRC client as often as I still want to use IRC. I stayed on the SeaMonkey side of the house on my personal systems this entire time.

      It was funny as hell to watch FF get bigger and more bloated than SeaMonkey, and its performance plummet. SeaMonkey's UI in the mean time only got faster with fixes and improvements and the browser just got better with all the gekko and js improvements that came downstream from the Firefox project. SeaMonkey was always the better browser for my particular needs, but after perhaps FF3 and later it was the better browser over Firefox for pretty much all the reason FF was selected over it in the first place. Completely lost sight of what they'd been trying to do.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    7. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 5, Informative

      If you check out NoScript itself, you'll see that it's written using an XPCOM object. This update kills XPCOM, so, no, the new API will not allow NoScript. It can't block at the same level as NoScript, because Chrome offers no method to modify the DOM before the document finishes loading, which means scripts embedded in the document can't be blocked.

      So, yes, this absolutely kills NoScript in future versions of Firefox.

    8. Re:Never mind run Chrome extensions... by phantomfive · · Score: 5, Insightful

      FF is a perfect example of a project going completely off the rails. I don't hear anyone saying good things about it anymore.

      It doesn't spy on you.

      Seriously, there was a time a few years back when many people (including me) switched away from Firefox because it had memory leaks, and didn't work very well. Now, it's a fine browser, and I don't understand why anyone would use Chrome over Firefox. Forget that spyware.

      --
      "First they came for the slanderers and i said nothing."
    9. Re:Never mind run Chrome extensions... by squiggleslash · · Score: 1

      It's OK though, it will still be possible to distinguish Firefox from Chrome: Firefox will not run Chrome's plug-ins...

      --
      You are not alone. This is not normal. None of this is normal.
    10. Re:Never mind run Chrome extensions... by phantomfive · · Score: 1

      There's a project to rewrite the major parts of Firefox in Rust.

      --
      "First they came for the slanderers and i said nothing."
    11. Re:Never mind run Chrome extensions... by JackieBrown · · Score: 1

      On the first link

      We plan to add our own APIs based on the needs of existing Firefox add-ons.

      NoScript-type functionality. This would come in the form of extensions to webRequest and possibly contentSettings.

      Sidebars. Opera already supports sidebar functionality; Chrome may soon. We would like to be able to implement Tree Style Tabs or Vertical Tabs by hiding the tab strip and showing a tab sidebar.

      So I guess we will see if it's available be for they end support for XPCOM

    12. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 1

      If Mozilla should learn anything, it is not to piss off your secondary developers, aka add-on devs and anyone that uses the API in general.

      They should write an interface between the old and new extensions instead of dropping support for hundreds, if not thousands of add-ons.
      Only a small subset of extensions will not work 100% with such an interface since some do come with plugins as well, but I am pretty sure even Chrome allows plugins packaged with Add-ons if I remember correct.

      Of course, as if that is going to happen, Mozilla don't understand the point of an API.
      This is the reason their browser is dying. Nobody wants things to break, not developers, but especially not users.
      Any time you make a major change to an API, you should write an interface between the old calls and new calls. (with any default values for new parameters)
      Not doing so is only going to piss people off. You could literally rewrite the damn extension calls to the API in memory so the overhead for it is only ever experienced once.
      There are several ways you can do it. Mozilla do none!

      Mozilla, for the love of god, stop breaking APIs, you morons.

    13. Re:Never mind run Chrome extensions... by mlts · · Score: 5, Interesting

      Another nice thing about FF is that it has its own FIPS compliant data stores for passwords as well as its own separate keystore. Chrome and IE use the system's keys on Windows.

      This is important, because if someone gets a bogus root CA into the Registry, Chrome and IE will happily honor it, while Firefox will stop and point it out.

      FF also provides password protection for the keystore data. This way, if FF is left unattended (and a timeout is set), an intruder can't just walk away with a user's password stash.

    14. Re:Never mind run Chrome extensions... by Merk42 · · Score: 1

      If they keep compatibility, people would bitch about 'bloat'.
      If they never changed the API in the first place, people would bitch extensions were hard to write for.

      When you have anything, especially software, with as many users as Firefox it is impossible to do (or not do) something that won't anger a non-zero number of users.

    15. Re:Never mind run Chrome extensions... by Guspaz · · Score: 3, Informative

      Chrome does provide support for modifying the DOM before it finishes loading.

    16. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 1

      Things started to go South since version 4.

      FF 3.6 was the last version I used as my main browser.
      When you think about it, it coincides with their switch to "rapid release process". Ridiculous decision imho.

    17. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      Well i guess missing noscript won't be a minus anymore when looking for replacement for firefox then. Still, we need noscript for more browsers than the forthcoming old firefox.

    18. Re:Never mind run Chrome extensions... by LichtSpektren · · Score: 2

      Chrome does spy on you, but the options which instruct it to do so (telemetry, phishing protection, sentence completion, etc.) can be easily disabled from the Settings menu.

      As to your claim that Firefox is NOT spyware: it collects telemetry in the exact same form as Chrome does (default on, can be disabled). Plus it serves you ads based on your browsing history now. Plus there's those closed-source third-party binaries that only God knows what they're doing. One has to be either insane or partisan to say that Chrome is spyware but FF is not.

    19. Re:Never mind run Chrome extensions... by phantomfive · · Score: 4, Insightful

      Mozilla, for the love of god, stop breaking APIs, you morons.

      That is the goal. The reason the 'API' kept breaking is because there wasn't an API at all: extensions were able to access the internal firefox code. Every time an internal function changed, it caused problems for extensions. Obviously that is bad, there needs to be a clear interface (like a wall) between the outside and the inside.

      Firefox here is finally making a good interface. Their plan is to extend the Chrome API so it contains all the functionality needed for current Firefox add-ons.

      --
      "First they came for the slanderers and i said nothing."
    20. Re: Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      Isn't there a big different between AdBlock on Firefox and AdBlocm on Chrome? The FF one seems far superior. Maybe someone can explain.

    21. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      You went full Chrome, man. Never go full Chrome.

    22. Re:Never mind run Chrome extensions... by myrdos2 · · Score: 1

      It doesn't matter what browser you use if your ISP is spying on you. I just assume that nothing I do online is private, as I have assumed for the past 15 years.

      (I didn't believe TOR was private either, until FBI agents told some prof to stop telling his students about it. So I guess it must work, at least some of the time.)

    23. Re:Never mind run Chrome extensions... by chefmonkey · · Score: 3, Insightful

      Mozilla, for the love of god, stop breaking APIs, you morons.

      That's actually the entire point of this move. The problem is that the current addon "API", such as it is, is literally every class in the entire freaking browser, which is an untenably huge and perpetually changing surface to maintain. The only way to keep the current API and stop breaking stuff constantly is to freeze all development on Firefox now and forever.

      That's not really a viable approach.

      The alternative is to come up with a more stable API surface, from the ground up, and provide a transition period for add-on developers to move from the large, unsupportable infrastructure to the stable one that won't be -- as you correctly observe -- constantly breaking.

      Rather than developing a new API, the add-ons team decided to leverage the work that Chrome has already done in this space, which has the nice side effect of making life much easier for developers who want to write cross-browser add-ons.

      One of the things that's getting lost in the noise here is that the portion of the API based on Chrome's current design is just the start. There will be additional API surface to enable some of the things that had been possible with the legacy wild-west-style Add-On approach. Since reading articles is not particularly trendy, I'll quote the relevant passage here:

      A major challenge we face is that many Firefox add-ons cannot possibly be built using either WebExtensions or the SDK as they currently exist. Over the coming year, we will seek feedback from the development community, and will continue to develop and extend the WebExtension API to support as much of the functionality needed by the most popular Firefox extensions as possible.

    24. Re:Never mind run Chrome extensions... by Darinbob · · Score: 3

      But Chrome is just as bizarre though. Both have utterly insane rapid fire update schedules designed to put features that benefit developers or developers' whims and not that of the customers. If I ditch Firefox it most definitely will never be for Chrome.

    25. Re:Never mind run Chrome extensions... by Darinbob · · Score: 2

      Storing your passwords in the browser is always a bad idea.

    26. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      So far, whenever Mozilla has asked "feedback from community", they have shat on that very community and did whatever the heck they wanted anyway.

      I trust them as much as much I'd trust a politician at this point.

    27. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      will continue to develop and extend the WebExtension API to support as much of the functionality needed by the most popular Firefox extensions as possible.

      That is the problem right there. It is consistent with all the other googlefication of Firefox the last couple of years. This will be another nail in its coffin.
      Firefox is dead. It just doesn't know it yet.

    28. Re:Never mind run Chrome extensions... by roca · · Score: 3, Informative

      The old addons model isn't going away until the new model is as capable as the old model supports NoScript, the better-than-Chrome AdBlock, Tree Style Tabs, etc at least as well as the old model currently does. Although the new model is largely based on Chrome's extension API, we're not limited to that API; we're adding the features those extensions need even though Google didn't want to add them to Chrome.

    29. Re:Never mind run Chrome extensions... by mlts · · Score: 1

      In some cases, stuffing them in a browser is worth it. There are a lot of websites which demand an account to do much (pinterest). With these, there is little lost if they get compromised (other than someone trying to troll from the account), so might as well toss worthless account IDs like that in someplace that is relatively convenient, and has some security.

    30. Re:Never mind run Chrome extensions... by Barefoot+Monkey · · Score: 1

      For now.

      Consider that in the past Chrome, Opera, Firefox, Internet Explorer and many other browsers all used to support the same plugins (which were made according to the Netscape Plugin API). Quite a long time ago IE changed to its own plugin API (ActiveX *shudder*), and Chrome now uses the Pepper Plugin API. There's no reason all the other browsers couldn't eventually move over to PPAPI (or some other one, but PPAPI looks like the best at the moment) and it would be like the old days when plugins didn't need to be made over and over for each individual browser.

    31. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      intruder can't just walk away with a user's password stash
      Except that we totally can, just like for every other browser, thanks to Nirsoft WebBrowserPassView.

      Sorry. Firefox was special at some point but they've fucked everything up instead of fixing their troubles. I gave up a few years ago and switched to Chrome. A clean install of Firefox goes to 2GB+ of RAM usage and eventually locks up a CPU core and becomes unresponsive if there's a flash game open in a tab or some such. Closing all but one tab doesn't free a single byte of RAM and the CPU stays pegged. Meanwhile, Mozilla kept saying they don't have memory or resource issues (blame shifting instead of fixing the problem, no matter what the actual cause is). I never had that problem with any other browser and getting rid of Firefox fixed that problem for good too.

    32. Re:Never mind run Chrome extensions... by mlts · · Score: 1

      That utility doesn't work if the passwords are encrypted with a master password as per their website. One will get an encrypted blob, but that's it. Maybe useful for backup, but not prying out what someone used for their latest vend a goat order.

      I do agree with you with another point -- in Chrome, I can do a shift-esc, and kill a lot of memory hogs per tab. No real way to do that in FF. Chrome also has better VM structure, keeping plugins a safe distance from the OS.

    33. Re:Never mind run Chrome extensions... by Darinbob · · Score: 1

      I would think that the inconvience of having a password for pinterest is a good thing if it keeps people away from pinterest.

    34. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      Nice vague statement, there. Mind explaining why?
      Unless you can prove that there's an easy way for the passwords to be stolen, it's just a password manager similar to other password managers.

    35. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      FF is a perfect example of a project going completely off the rails. I don't hear anyone saying good things about it anymore.

      Because there's nothing exciting to report about Firefox anymore, and there hasn't been for years. But who cares? I like that.

      Chrome is what's hip and in right now but every time I try it I'm amazed at how such a buggy, unpolished browser could be so popular and highly rated.

    36. Re: Never mind run Chrome extensions... by Guspaz · · Score: 1

      Is there still? In the early days of Chrome, there was no way to stop content from loading, so AdBlock only removed ads after they were displayed (they'd flash briefly on-screen). So back then, it wasn't very good. At some point (years ago) they added APIs to filter content before it loads, which basically solved that problem (although there was a transition period where AdBlock was a bit buggy as they worked the kinks out). Nowadays, it's been quite some time since I've used FireFox, but AdBlock seems to work as well as I remember AdBlock working when I used FireFox.

      But in terms of my previous reply, I specifically was referring to there being methods to do stuff in the DOM while it's still loading, which contradicts the claim that you can't do anything until after it loads. I don't know if you can do anything before it loads at all, but you can definitely do stuff before it finishes.

    37. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      It's actually rather disappointing because Firefox used to be the "better" browser. Chrome came out and did a lot of half-assed stuff, Chrome's basically the new Internet Explorer. Chrome Extensions are often terrible and slow.

      To give you an example of the difference between how a Firefox extension and a Chrome extension works. The "adblock" used to be only for Firefox. It actually worked pretty good for a while, but on Chrome it was only able to "delete" pieces of the DOM by adding CSS stylesheets into places that were illegal to hide things. This made it super-slow, and easy defeated.

      There are other extensions that do similar things. Basically the web server can detect that extensions are present, without any API checks, the fact that certain illegal DOM elements exist is enough.

    38. Re:Never mind run Chrome extensions... by Espectr0 · · Score: 1

      That has pros and cons as well. For example, i use firefox in our company so users can change their proxy settings when the main internet connection goes down. But when i need to deploy a certificate to 250 users with no tools whatsoever, having a different certstore sucks.

    39. Re:Never mind run Chrome extensions... by Espectr0 · · Score: 1

      You are simply wrong. Proof: ad blocking extensions available in Chrome.

    40. Re:Never mind run Chrome extensions... by JanneM · · Score: 1

      I use both Firefox and Chrome. And Firefox is faster and lower on resources than Chrome today. If I were to jump anywhere, it would be away from Chrome and to Firefox only.

      --
      Trust the Computer. The Computer is your friend.
    41. Re:Never mind run Chrome extensions... by thegarbz · · Score: 1

      The good news is that if after a full year the developers haven't ported to the new API you get to stop using unmaintained and likely privacy leaking and exploit ridden plugins in favour of something being actively maintained.

    42. Re:Never mind run Chrome extensions... by thegarbz · · Score: 1

      Really? I guess you missed the Slashdot post about offering advertising tiles customised to suit users in the Firefox home screen then.

    43. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      Pale Moon is a totally clean break to an older ESR without proper addon compatibilty, and a lot of broken shit.

      Besides, they're not planning on dumping support for addons, just improving the status quo (which is really shitty, though our rose-colored glasses won't allow us to admit that).

      Honestly, I hope everyone who's so shallow as to leave Firefox over this does so sooner rather than later, though. Firefox needs to be brought into the future, and it can't do that with all the baggage of legacy addons and legacy users who complain about every pea under the mattress.

    44. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 1

      That's not enough: you don't want to modify the DOM before it finishes loading, you want to modify the DOM as it's being built.

      For NoScript to work, it has to actively remove <script> tags before they get a chance to run. At all.

      Chrome allows you to embed JavaScript onto a page, at which point you can run JavaScript in the context of the page. This is sufficient to modify the DOM "before the document finishes loading" but not enough to allow you to prevent JavaScript on the page from running at all, which is what NoScript does. There's a reason there's no NoScript for Chrome, it's because Chrome doesn't offer the APIs required to implement NoScript.

      With this change, neither will Firefox.

    45. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      > I don't hear anyone saying good things about it anymore.

      Its no longer the piggy browser...

    46. Re:Never mind run Chrome extensions... by tepples · · Score: 4, Informative

      in Chrome, I can do a shift-esc, and kill a lot of memory hogs per tab. No real way to do that in FF.

      about:memory estimates how much memory each tab is using. Close the hogs and then click "Minimize memory usage".

    47. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 2, Insightful

      You know how AdBlock only works on Chrome by hiding the ads rather than actually preventing them from being downloaded? You know why there's no Greasemonkey for Chrome, only a crippled Tampermonkey? Because the API way of doing business prevents these extensions from doing what they do. Mozilla is trying to kill off the most popular extensions because their advertising sponsors HATE them.

      It's like every day the Mozilla team wakes up and thinks, "shit, we're not going to hell in this handbasket fast enough. What could we do today to further alienate our users and developers to accelerate the decline?"

    48. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      Their plan is to extend the Chrome API so it contains all the functionality needed for current Firefox add-ons.

      If that's their plan, let's see if they'll commit to keeping support for "old" extensions until the API contains all the necessary functionality to allow plugins like DownThemAll and Greasemonkey to do what they do. I volunteer you to hold your breath while we wait for that commitment from Mozilla. You know why you won't get that commitment? Because it's not their intention at all. They're blowing smoke and trying to calm people down so they'll swallow this piece of shit without mounting a rebellion.

    49. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      The relevant passage sounds like a slimy politician trying his best to avoid committing to anything. That's a press release written by someone in marketing in damage control mode. Lots of vague promises of working with the community they constantly give the finger to, promises to support functionality users want, but only if it's "possible." There's no commitment to support the "old" way of doing things until the new API works for the top 1,000 or so extensions.

    50. Re:Never mind run Chrome extensions... by roca · · Score: 2

      PPAPI is dying.

      PPAPI has two main use-cases: supporting Flash and other browser plugins, and being the API for (P)NaCl applications --- C/C++ applications compiled to run on the Web, which have no more privileges than Web content.

      "Browser plugins", i.e. native code that you can download and install in the browser, that runs content from the Web and has access to the same OS APIs at the same privilege level as the browser itself, are going away and not coming back. Flash is the last significant hold-out, but it's on a path to extinction.

      WebAssembly, not (P)NaCl, is the future of compiling C/C++ to run on the Web, and WebAssembly uses the standard Web APIs, not Pepper.

    51. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 1

      It doesn't spy on you.

      You mean like the new tab ads that collect data on any user clueless enough to leave them enabled? Or do you mean how they don't collect usage data and send it back to Mozilla by default? Perhaps you were thinking of how Firefox submits every site you visit to Google to check if it's "bad"?

    52. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      Some people release well written code instead of bug ridden crap. How did the norm become write crappy code and support it for years instead of write good code and only deal with clueless users? Why does an image resizing plug-in need constant updates and support?

    53. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      That doesn't work. Most of the memory is used by js- type entries and they don't reduce their size when you do that.

    54. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      i hope by 'we' you mean you're part of the team that will be developing this, and have the authority to make such claims.

      without the flexibility and capabilities of existing firefox addons, such as noscript... firefox loses its entire advantage over chrome and most other browsers, except microsoft's.

      i'd sooner rather quit using the browsers altogether and go back to traditional media outlets, the library, etc, than use a browser without noscript and adblock functionality (at least as capable as they are today). that's how absolutely horrible the internet is without them.

    55. Re:Never mind run Chrome extensions... by Guspaz · · Score: 1

      Except Mozilla already explicitly stated they were adding an API call specifically so that NoScript would be possible.

    56. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      chrome api allows you to inspect every http request, including those to scripts, and take whatever action you want.

      No, NoScript does not need to remove script nodes before they are added in order to work.You dont know what youre talking about.

    57. Re:Never mind run Chrome extensions... by Giorgio+Maone · · Score: 3, Informative

      Some hints at what's happening with NoScript, with my proposal to preserve the edge Firefox has over Chrome in terms of innovation through extensions, despite the limitations of a Chrome-compatible API: https://hackademix.net/2015/08...

      --
      There's a browser safer than Firefox, it is Firefox, with NoScript
    58. Re:Never mind run Chrome extensions... by Barefoot+Monkey · · Score: 1

      Thanks for that information :)

    59. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 1

      Someone doesn't know how NoScript works! Yes, you can block third-party script requests using the network stuff. That's part of NoScript.

      NoScript blocks JavaScript from running on pages at all. To do that, it has to be able to block something like: <script>alert("Hello!")</script>

      Plus there are scripting surrogate things that replace existing third party scripts with stubs to block trackers. That also does not appear to be possible using the new extensions API.

      Bottom line: NoScript absolutely is killed using this new API.

    60. Re:Never mind run Chrome extensions... by WndSks · · Score: 0

      That is not strictly true, there are currently 3 types of extensions where one provides a abstraction layer: 1) Legacy/Overlay. These access the XUL DOM directly. 2) Bootstrap/Restartless. Like 1 but without UI overlays so they can be added/removed without restarts. 3) Using the addons SDK. These are supposed to be abstracted away from the Firefox XUL and are "based on HTML5" and all those buzzwords. https://blog.mozilla.org/addon...

    61. Re:Never mind run Chrome extensions... by tepples · · Score: 1

      If what you say is true, I'd like to run some tests on some JS-heavy web app. When you close a tab, what "js-type entries" don't go away?

    62. Re:Never mind run Chrome extensions... by Bite+The+Pillow · · Score: 1

      Ad blocking does not mean the necessary implementation details are in place. Proof needs to be a careful reading of Chrome documentation, compared with Noscript functionality. It seems to me that you are simply wrong.

      Less simply, if Mozilla plans to extend the API to allow noscript, I believe that the current API does not allow for it to work.

    63. Re:Never mind run Chrome extensions... by phantomfive · · Score: 1

      Well, that's good to know.

      --
      "First they came for the slanderers and i said nothing."
    64. Re:Never mind run Chrome extensions... by Zaiff+Urgulbunger · · Score: 1

      It's not been my main browser for years, but I use linux and Mozilla said they were primarily targeting Windows with Firefox... so that maybe explains why it's always been kind of slow on my Ubuntu anyway.

      But I do welcome this news. I've only ever really "played" with extension development, but Firefox was always much harder to work with than Chrome, not least because a lot of the documentation seemed to be out of date. I seem to recall the Firefox extension tutorial/example thing used the status bar... that had been removed a long long time before.

      Also, I suspect Firefox will need this because I seem to recall hearing that Microsoft Chrome^H^H^H^H^H^HEdge was going to support Chrome extensions. At that point, MS-Edge would, for most users, be superior to Firefox.

    65. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      Mozilla can't win these days, any decision they make, even good ones is instantly sensationalized as 'ZOMG FIREFOX IS BECOMING CHROME, DAE H8 MOZILLA?!'

    66. Re:Never mind run Chrome extensions... by phantomfive · · Score: 1

      Mozilla can't win these days,

      tbh I don't care about "winning", I care about good software.

      --
      "First they came for the slanderers and i said nothing."
    67. Re:Never mind run Chrome extensions... by roca · · Score: 1

      I'm not on the team, but I work at Mozilla and I've talked to Bill McCloskey about this.

    68. Re: Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      I've never seen my instances of FF use that much memory, I have seen chrome chew up all available memory though.

    69. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      If you need to cherry-pick specific popular addons instead of creating an API that is comprehensively better than (or at least equal to!) the current methods available to addon developers, then you've already failed.

    70. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      That's probably graphics driver issue. It happened to me 5+ years ago, with bad ATI catalyst driver on Windows, and not just FF, it also happened in VLC and other programs.

    71. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      It doesn't spy on you.

      You mean like the new tab ads that collect data on any user clueless enough to leave them enabled? Or do you mean how they don't collect usage data and send it back to Mozilla by default? Perhaps you were thinking of how Firefox submits every site you visit to Google to check if it's "bad"?

      Er, no. Firefox regularly downloads a list of bad sites from Google and compares your URLs to it locally. At no point does it send your browsing history to Google.

      Can you tell us where you heard this? Because it seems to be a persistent and yet entirely wrong meme.

    72. Re:Never mind run Chrome extensions... by Anonymous Coward · · Score: 0

      > Mozilla said they were primarily targeting Windows with Firefox...

      Er, what? I don't think we've ever said that. We have 3 tier-1 platforms: Windows, Mac and Linux.

  2. Great, I just switched BACK by p51d007 · · Score: 1

    to FF a few weeks ago from Chrome. Chrome just kept eating resources, getting slower and slower. How about this, turn on the "it's own resources" by default, but allow those of us that want the SPEED to turn it off.

    1. Re:Great, I just switched BACK by phantomfive · · Score: 1

      Don't worry, the new extension API is a good thing.

      --
      "First they came for the slanderers and i said nothing."
    2. Re:Great, I just switched BACK by firex726 · · Score: 1

      I switched as well but somehow FF is even worse performance than Chrome. Often idling with 10% CPU use and spiking up to 90% when visiting certain sites like Amazon.

    3. Re:Great, I just switched BACK by roca · · Score: 2

      Amazon recently started doing something pathological where they restyle and relayout their search results page every 100ms. The particular restyling and relayout scenarios happened to be very well optimized in Chrome, but not Firefox, so less noticeable in Chrome (though still waking up and doing unnecessary work every 100ms). The optimizations are mostly implemented in Firefox nightly, and will be completely implemented very soon, but obviously it takes a little while for them all to reach the release channel :-(. (And would take even longer if we didn't have that rapid update cycle that other people complain about in the comments in this article!)

  3. Commendable by Anonymous Coward · · Score: 1, Insightful

    That's very commendable. But, the fact that they are choosing to follow someone else's standard(Chrome), rather than the other way around when they were the first to implement the add-on capability speaks volumes about their future.

    I'm not so much saddened by Mozilla's decline. I'm devastated that the only viable replacement is Google Chrome.

    1. Re:Commendable by jez9999 · · Score: 1

      Pale Moon is a viable replacement.

    2. Re:Commendable by Dracos · · Score: 1

      Mozilla has been copying everything Chrome does for years.

      I've come to rue every time I upgrade FF because every time I do, some extension I've used for years no longer works or I can no longer trick FF into letting it work. I'm writing this in FF33 right now; my laptop is still on FF29.

      The last good complete theme died with FF 3.5. Almost everything on the addons site is abandoned, and only the few most popular addons keep up with the relentless release cycle.

      Mozilla has been damaging itself and its entire product line since the day Mitchell Baker stepped down as CEO. Messed up priorities, time-driven releases, and thoughtless "me too" feature strategy are killing a once-great web innovator.

      XUL had such potential, but now they're abandoning that too. Is anyone really surprised by this announcement?

    3. Re:Commendable by roca · · Score: 2

      You are confused.

      The problem of extensions breaking due to Firefox updates requires the solution of having a stable supported API for extensions to use. That is exactly what this announcement is about!

      Mitchell Baker was never the CEO.

      XUL was never great and almost everything good in XUL has been incorporated into Web standards supported across browsers (e.g. CSS flexbox).

  4. What? by MagickalMyst · · Score: 1

    Noooooooooooo...

    --
    Political correctness is really just herd psychology pushed by insecure people who desperately seek social conformity.
  5. a reason? by Anonymous Coward · · Score: 1

    There's got to be a good reason for this. Obviously, Firefox extensions are superior to Chrome's. They can modify the browser far more than Chrome extensions. Maybe it has to do with performance?

    1. Re:a reason? by Anonymous Coward · · Score: 0

      Soon they won't be superior, as the elevated privileges Firefox extensions have had will be removed entirely. It's ironic that Addon-SDK/Jetpack extensions losing the ability to do require('chrome') will make them compatible with Chrome extensions.

    2. Re:a reason? by phantomfive · · Score: 1

      There's got to be a good reason for this.

      Because the extension API was kind of lousy.
      Because the extension API was going to need big changes to deal with the new multi-process browser capability that Mozilla is implementing.
      Because the extension API was never very stable to begin with.
      Because the extension API wasn't really an API, it was basically allowed full access to whatever was in Firefox (which explains why it wasn't stable).

      You are right that the Chrome API lacks functionality. The Mozilla plan is to extend the API, so that everything that is (reasonably) possible now remains possible. They are asking for help identifying functionality that will need to be added, so maybe you can volunteer some ideas.

      --
      "First they came for the slanderers and i said nothing."
  6. Old extensions by penguinoid · · Score: 3, Funny

    How about they upgrade it so it can run Firefox extensions?

    --
    Don't waste your vote! Vote for whoever you want, unless you live in a swing state it won't matter anyways
  7. So what's the point of Firefox anymore? by LichtSpektren · · Score: 3, Interesting

    Interoperability means everybody will start developing extensions solely for Chrome, since it's less work to make one build for every browser. So what's the point of Firefox after that happens?

    I advocate for Pale Moon and Chromium. They're both FLOSS. Firefox no longer is, because it has integrated third-party binaries (Netflix DRM, Pocket). Consequently, Firefox is now less secure (see http://it.slashdot.org/story/1... ). This is also to say nothing about the build-in advertisements that read your browsing history, and the awful performance chokes it suffers from.

    1. Re:So what's the point of Firefox anymore? by Merk42 · · Score: 1

      Interoperability means everybody will start developing extensions solely for Chrome, since it's less work to make one build for every browser. So what's the point of Firefox after that happens?

      Pretty sure interoperability means the extensions made won't be solely for Chrome

    2. Re:So what's the point of Firefox anymore? by roca · · Score: 3, Informative

      The Pocket issues had no effect on Firefox users not actually using Pocket, i.e. you (I assume). Furthermore the Pocket integration code in Firefox is open source.

      The Adobe DRM module is closed source but integrated in the best way possible given the DRM requirements. You can delete the module without breaking anything except DRM. If you don't, the module is very tightly sandboxed so it can do nothing but decode video and audio. It is thus much more privacy and security friendly than, say, Flash. (You have already removed Flash, right?) I'm glad you don't want to watch Netflix, but it turns out a lot of people do, and "can't watch Netflix!" is not a great feature.

      The new Firefox extensions model will support extensions like Tree Style Tabs and better ad blocking than Chrome's API provides. We're not limiting ourselves to Chrome's API.

    3. Re:So what's the point of Firefox anymore? by Anonymous Coward · · Score: 0

      To view pages with NPAPI plugins like Java, Unity, etc. while Chrome is not going to support it?

  8. So this kills AdBlock and NoScript, right? by Anonymous Coward · · Score: 2, Insightful

    I have only one question about this move:

    Will AdBlock Plus and NoScript still work? Chrome's extension model simply doesn't give extensions the control necessary to implement something like NoScript, which is literally the only reason I still use Firefox. Otherwise, there's no point: Firefox is the slowest, least memory efficient browser out there. It regularly breaks several GB of memory after only a day's use. In fact, Firefox is already up to nearly 3GB of memory use, which is somewhat worrying for a 32-bit process. Looks like I'm going to have to quit and restart after this comment.

    I can make do without AdBlock Plus (there's always hosts, Firefox can't kill that), but I can only imagine this move is driven by the marketers in charge of Firefox to kill extensions like NoScript and AdBlock Plus.

    1. Re:So this kills AdBlock and NoScript, right? by Anonymous Coward · · Score: 1

      From TFA:
      We plan to add our own APIs based on the needs of existing Firefox add-ons.
      * NoScript-type functionality. This would come in the form of extensions to webRequest and possibly contentSettings. ...

    2. Re:So this kills AdBlock and NoScript, right? by Anonymous Coward · · Score: 0

      So, in other words, yes, this kills NoScript, and no, they won't really fix it, just sketch up vague plans to maybe fix it.

    3. Re:So this kills AdBlock and NoScript, right? by Anonymous Coward · · Score: 0

      >

      I can make do without AdBlock Plus (there's always hosts, Firefox can't kill that), but I can only imagine this move is driven by the marketers in charge of Firefox to kill extensions like NoScript and AdBlock Plus.

      uMatrix+uBlock are more than enough to cover the holes left by the loss of those two.

    4. Re:So this kills AdBlock and NoScript, right? by Blaskowicz · · Score: 1

      Adblock Plus is a huge hog, with ublock and privacy badger I'm now at only 880MB use with a bunch of shit open (though usually it's more 1.1GB to 1.5GB)

    5. Re:So this kills AdBlock and NoScript, right? by robsku · · Score: 1

      Firefox is the slowest, least memory efficient browser out there. It regularly breaks several GB of memory after only a day's use. In fact, Firefox is already up to nearly 3GB of memory use, which is somewhat worrying for a 32-bit process. Looks like I'm going to have to quit and restart after this comment.

      I've actually never witnessed this, but I hear it so often I'm beginning to believe the issue exists - but perhaps only for the Windows version. The few times I've had to use windows in the past few years has given me the experience that all browsers tend to be rather sluggish on it... oh well, that's what you get for using subOS. Oh, and I keep Firefox running for days, even weeks, and have generally around 100 tabs open at any time. There was a time when my average was closer to or even over 200 tabs, and back then I had only 512MB's of RAM - yet I have no idea what this memory use issue so many talk about is.

      --
      In capitalist USA corporations control the government.
    6. Re:So this kills AdBlock and NoScript, right? by perryizgr8 · · Score: 1

      If you're still using Adblock plus, you are doing it wrong. Have a look at uBlock origin.

      --
      Wealth is the gift that keeps on giving.
  9. Goddamnit Mozilla, snap out of it! by Anonymous Coward · · Score: 0

    You are not the authors of Chrome. You do not need to make a clone of Chrome. If your browser becomes too much like Chrome, there is no reason not to use the original. Snap the fuck out of it! Now!

  10. Fucking morons by damicatz · · Score: 3, Insightful

    The sole advantage of Firefox over Chrome these days is the fact that it's add-on SDK allows addons to modify just about any part of the browser. Chrome extensions are extremely limited in what they do. How will things like FileZilla work with this new API?

    I'm convinced that either the Mozilla Foundation is run by complete mental midgets or plants by Google who are determined to sabotage the browser until the whole foundation shuts down.

    1. Re:Fucking morons by LichtSpektren · · Score: 2

      I'm convinced that either the Mozilla Foundation is run by complete mental midgets or plants by Google who are determined to sabotage the browser until the whole foundation shuts down.

      Nah, it's not Google holding the reins. The default search for Firefox used to be Google, but it was switched to Yahoo, which is a front for Bing. So if anybody's hiding under a Trojan horse at Mozilla, it's Microsoft.

      But that's unlikely. No, I think what happened is that around the time Brendan Eich was forced to resign due to some manufactured outrage, the board of directors decided to just monetize the balls out of Firefox and ride a golden parachute down to its destruction. Three weeks later they implemented Australis and told the complainers to piss off. Then came Pocket. Then came the spyware ads. Then came the DRM. Soon comes the silently-installed crapware, charging for extensions, directors' resignations with generous severance pay.

    2. Re:Fucking morons by ITRambo · · Score: 1

      Concerning your last sentence, since Firefox moved to Yahoo as the default search engine, I'd go with complete mental midgets.

    3. Re:Fucking morons by ic3m4n1 · · Score: 1

      If this has Google hands this looks far worse than Microsofts policy of Embrace...Extend...Extinguish.
      The direction browser is taking is simply in-explainable for any open source project on its own.
      The King is dead...Long live the King.

    4. Re:Fucking morons by ic3m4n1 · · Score: 1

      Or maybe this is what Google want you to think ;)

    5. Re:Fucking morons by phantomfive · · Score: 4, Informative

      The sole advantage of Firefox over Chrome these days is the fact that it's add-on SDK allows addons to modify just about any part of the browser. Chrome extensions are extremely limited in what they do.

      They are planning on extending the add-on API so it still has most of the functionality of the current add-ons. It will be much more sophisticated than what Chrome allows now.

      --
      "First they came for the slanderers and i said nothing."
    6. Re:Fucking morons by chefmonkey · · Score: 1

      [T]he board of directors decided to just monetize the balls out of Firefox and ride a golden parachute down to its destruction.

      The IRS has some pretty rigorously enforced guidelines about executive and employee compensation at 501(c)(3) nonprofits, like Mozilla. It's a complicated topic, but this gives a good introduction to the overall idea: https://www.councilofnonprofit...

      The executive summary is that there's nothing anyone can do to make a nontrival personal profit off of anything Mozilla does. So you can sling mud all you want, but accusations that decisions at Mozilla are driven by some kind of profit motive are borne of plain ignorance.

    7. Re:Fucking morons by LichtSpektren · · Score: 1

      [T]he board of directors decided to just monetize the balls out of Firefox and ride a golden parachute down to its destruction.

      The IRS has some pretty rigorously enforced guidelines about executive and employee compensation at 501(c)(3) nonprofits, like Mozilla. It's a complicated topic, but this gives a good introduction to the overall idea: https://www.councilofnonprofit...

      The executive summary is that there's nothing anyone can do to make a nontrival personal profit off of anything Mozilla does. So you can sling mud all you want, but accusations that decisions at Mozilla are driven by some kind of profit motive are borne of plain ignorance.

      You're technically right that it's born of "ignorance" since I lack any inside information about the matter and I'm speculating. That being said, how naive does one have to be to believe that Mozilla integrated Pocket directly into Firefox (as opposed to ABP, NoScript, Force HTTPS, Privacy Badger, etc.) out of the goodness in the directors' hearts, and not to make a buck?

    8. Re:Fucking morons by chefmonkey · · Score: 1

      You're technically right that it's born of "ignorance" since I lack any inside information about the matter and I'm speculating.

      Sure, but even a lay understanding of the word "profit" and the negating prefix "non" should give you some hint about how non-profit organizations are legally required to operate.

    9. Re:Fucking morons by Anonymous Coward · · Score: 0

      Plus, the main reason, as I understand, for most extension breakages is that there is no standardised interfaces for extensions - they just use whatever they can access. Now Mozilla tries to fix this by standardizing with added compatibility with other platforms. For me it looks as very sane step

    10. Re:Fucking morons by phantomfive · · Score: 1

      Yes, that is exactly right. After this, there will be a standardized API, so it should be a lot more stable. That doesn't exist right now. This is definitely a step forward.

      --
      "First they came for the slanderers and i said nothing."
    11. Re:Fucking morons by roca · · Score: 1

      So basically you're making stuff up and posting it to the Internet. Thanks.

    12. Re:Fucking morons by damicatz · · Score: 1

      And rules can be made to go away when you have enough money to hire lawyers and accountants that know all the loopholes and people to bribe.

    13. Re:Fucking morons by Dagger2 · · Score: 1

      Which is awesome, if Mozilla add the standardized interface to do whatever it is you need to do.

      Which, for many things, they won't. Otherwise you wouldn't be writing the damn extension in the first place.

    14. Re:Fucking morons by Anonymous Coward · · Score: 0

      I'm convinced that either the Mozilla Foundation is run by complete mental midgets or plants by Google who are determined to sabotage the browser until the whole foundation shuts down.

      Neither, but you're getting warmer. The US government is in the Mozilla machine now, and anyone who doesn't see that simply isn't paying attention.

    15. Re:Fucking morons by Anonymous Coward · · Score: 0

      Speaking of mental midgets - good plan by those Google plants making Yahoo the default search engine. Stupid fuck,

    16. Re:Fucking morons by Anonymous Coward · · Score: 0

      Fork it, dipshit, and quit your complaining.

    17. Re:Fucking morons by thegarbz · · Score: 1

      So based on the recent experiences with Firefox the new API will look like Chrome's, run like Chrome's, and include several 3rd party closed source "features" that users actively campaigned against?

      Mozilla has a lot of trust to regain before I will believe anything they say about their development goals. Oh I'm sure they'll try and do what they say, and I'm sure they'll screw it up along the way while their users shout "no" at them louder and longer than Darth Vader in the upcoming 4K remix of StarWars.

    18. Re:Fucking morons by phantomfive · · Score: 1

      No one cares if you believe Mozilla about their development goals. You're cool, though.

      --
      "First they came for the slanderers and i said nothing."
    19. Re:Fucking morons by LichtSpektren · · Score: 1

      I did say "I think what happened" to indicate speculation on my part, but ok.

    20. Re:Fucking morons by LichtSpektren · · Score: 1

      Um, ok? So you think that Mozilla being a registered nonprofit means it cannot be the case that their board of directors are getting under-the-table money?

      IANAL, but skimming over the link you provided, I can find some loopholes in any case. For instance, in the three-step process to determine appropriate compensation, #2 is: "[an] independent body should take a look at "comparable" salary and benefits data, such as data available from salary and benefit surveys, to learn what employers of a SIMILAR BUDGET SIZE that are located in the same, or a similar geographic region, pay their senior leaders" (caps added by me).

      So if Mozilla increases their budget size by monetizing the balls out of Firefox and inserting ads and third-party binaries, then they can pay themselves more, no?

  11. The plug-in feature I do want is... by xxxJonBoyxxx · · Score: 1

    When I launch a new incognito/private window, I want to let some plug-ins, especially Flashcontrol or Flashblock, run by default. There's nothing like launching a new window to get around someone's X-story paywall and getting blasted with their auto-play video.

    1. Re:The plug-in feature I do want is... by Anonymous Coward · · Score: 0

      Chrome's extension page has a checkbox under each one that reads something to the effect of "allow in Incognito mode."

  12. Firefox by Anonymous Coward · · Score: 0

    Why does Firefox use 30% CPU just sitting there doing nothing on a page with no JS?

    1. Re:Firefox by firex726 · · Score: 1

      Exactly my issue.

      It's sitting at 10% CPU use and 2GB memory. And god forbid I go to a site with JS which can bog down the whole thing.

  13. I like firefox over any of the alternatives. by sjbe · · Score: 3, Informative

    FF is a perfect example of a project going completely off the rails. I don't hear anyone saying good things about it anymore.

    I use firefox as my primary browser and it continues to serve my needs better than any of the alternatives. It's available on linux unlike IE or Safari and for my needs at least it is less buggy than Chrome. Google can't seem to stop breaking things in Chrome and while they usually fix them it's annoying in the meantime. I see no meaningful speed or performance differences between the major browsers. Firefox seldom has site compatibility issues. While I won't argue that FF is without warts, it is to my mind the best available option at this time. That may change of course but I don't see anything better out there for my needs at present.

    It started as an effort to be lighter and faster than the old Mozilla suite. I actually like the mail client...

    At one time I did too. However it stagnated and I move on to other things. 12 years have passed since the project was started and the web has evolved substantially since then. Things have gotten more complex and so has the software to deal with them. This isn't 2002 and expecting the software to be the same is kind of silly.

    Completely lost sight of what they'd been trying to do.

    What they originally were trying to do is not as relevant today. Perhaps you want a stripped down browser with minimal frills. That's fine but most of the rest of us are concerned with other things. So long as it let's me view the bits of the web I want and gives me options to configure to my particular quirks without crashing or causing problems, I don't really care if it takes up extra space or has a few features I don't use.

    1. Re:I like firefox over any of the alternatives. by thegarbz · · Score: 1

      Firefox was not about being stripped down. The Mozilla Manifesto had many points to address, among them was the ability for individuals to shape their experience, adherence to open source, and community / participation based programming.

      Yet we now have a browser that actively limits customisation, forcing changes on users, ignoring user requests, and at one stage even including proprietary closed source APIs natively in the browser.

      Not being lighting fast is not the reason I think Mozilla has lost its way, giving its users the middle finger is. I want Firefox, not Chrome Lite.

    2. Re:I like firefox over any of the alternatives. by Anonymous Coward · · Score: 0

      The instant Mozilla became a corporation was the day I stopped participating. I have filed over 2,000 bugs since 1998, and triaged, testcased, or helped fix thousands more. That all stopped the day it became Mozilla Corporation, a for-profit enterprise. I do not make a habit of donating labor to for-profit business.

      The history of the United States is littered with hundreds or even thousands of cases of a top-notch product going to shit once it become a labor of money instead of a labor of love - from bands who "sold out" to products that went from made in the USA with quality materials to made in China with lead and melamine. Firefox is just another example in the dust heap of history. Just like when I was whining about Netscape driving themselves into a ditch in 1996, many will poo poo me. You just wait and see.

  14. Another shitty /. article by Anonymous Coward · · Score: 0

    Both the title and content of the /. excerpt completely miss the point of TFA.

    The key take-away is that Mozilla is redesigning the Firefox engine to be a clone of Chrome, thereby killing the thousands of existing add-ons, and eventually Firefox itself.

    Where do so many successful corporations find such idiotic management?

  15. Rants by Anonymous Coward · · Score: 1

    Yeah, rants rants rants. No need to read, no need to understand or at least ask.

    From TFA:

    We plan to add our own APIs based on the needs of existing Firefox add-ons.

            NoScript-type functionality. This would come in the form of extensions to webRequest and possibly contentSettings.
            Sidebars. Opera already supports sidebar functionality; Chrome may soon. We would like to be able to implement Tree Style Tabs or Vertical Tabs by hiding the tab strip and showing a tab sidebar.
            Toolbars. Firefox has a lot of existing toolbar add-ons.
            Better keyboard shortcut support. We'd like to support Vimperator-type functionality.
            Ability to add tabs to about:addons.
            Ability to modify the tab strip (Tab Mix Plus).
            Ability to take images of frames/tabs (like canvas.drawWindow)

    1. Re:Rants by Anonymous Coward · · Score: 0

      Oh, I bet you also believe anything your local politicians tell you.

      Public admission to trusting Mozilla's promises should be grounds to deny voting rights on the next election.

    2. Re:Rants by Anonymous Coward · · Score: 0

      So its better bitch instead of waiting (and maybe providing constructive ideas) to see how they execute their ideas?

    3. Re:Rants by Anonymous Coward · · Score: 0

      It doesn't matter whether we bitch or not. We bitched about destroying the old sync method, but it still happened. We bitched about Australis, but it still happened (and now the extension fixing Australis will get the API yanked from under its feet, hooray). We bitched about integrating crap like Pocket, but it still happened anyway. Guess you can see a trend here.

      Besides - what, you expected people to praise the fact that 99% of popular Firefox addons will need to be rewritten from the ground up? :)

    4. Re:Rants by Anonymous Coward · · Score: 0

      I expect people to look to the current situation and be reasonable about it. Current FF extensions has no stable API. As a result extensions often break because they access too mutch of the guts of the browser. Mozilla tries to fix by standardising it. Everyone not happy. WTF?

    5. Re:Rants by Dagger2 · · Score: 1

      Uh, no. Mozilla tries to fix it by just breaking them once and then never letting anyone fix them*. Everyone not happy, and if that's a WTF to you then I don't know what to say.

      *: At least for some subset (the interesting subset) of extensions. Some extensions will be fixable, as they'll merely require a complete rewrite rather then being impossible.

    6. Re:Rants by Anonymous Coward · · Score: 0

      And alternative is what? To stall the whole development of FF? Because every single inner change may break some extension. Sooner or later your interesting subset of extensions will break. Don't forget that people also rant that performance is poor, responsiveness is bad etc. Addressing those issues need changes (like Electrolysis) that will definitely break current "API". Its a hard position to be in - damned if you do, damned if you don't.

    7. Re:Rants by Dagger2 · · Score: 1

      The alternative is to introduce a stable API for extensions to code against if they want to, and make the API powerful enough that most extensions actually can be written with it. And then, for extensions that can't be done in the API, just accept that breakage might happen.

      (And note that I said "might", not "will". Many extensions only touch the browser UI and not content pages, and won't be affected by e10s.)

      As usual, Mozilla gets most of the way there and then fucks up right at the crucial point; in this case by declaring that if their new API doesn't do the trick, then you can just bugger off somewhere else.

    8. Re:Rants by Anonymous Coward · · Score: 0

      Dropping support for old extensions as I understand are closely related with plans of migrating away from XUL and XPCOM which *will* definitely break such legacy extensions.

  16. WTF by Anonymous Coward · · Score: 0

    At this point, I really don't understand why Mozilla doesn't throw away Firefox and just become a clone of Chrome. They could put the ads and third party services back in of course.

  17. NoScript for chrome then? by 140Mandak262Jamuna · · Score: 1

    So we can expect NoScript in chrome? Will it run in Android Chrome too? How do you block the really annoying pop-ups in android? The screen real estate is tiny, it does not go away, it prompts back why are you deleting this popup etc.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    1. Re:NoScript for chrome then? by Anonymous Coward · · Score: 0

      On android:
      Root your phone, install AdAway from FDroid (https://sufficientlysecure.org/index.php/adaway/ )
      If the phone cannot be rooted, Wifi-connect to a router with DDWRT where you have configured a blocking hostfile*, or to a DNS server on a PC that has a blacklist

      * Linksys E1200 is the cheapest I have seen that is supported, around USD$70

  18. It wouldn't happen if I made it. by Anonymous Coward · · Score: 0

    I know everything there is to know about making software, so I will armchair critique every change (or lack thereof). I won't actually make any equivalent myself though, so as to be free from the same sort of diametrically opposed critiques from the masses.

  19. Soon... by Anonymous Coward · · Score: 0

    Firefox will be going Blink.

  20. Yay by Barefoot+Monkey · · Score: 1

    This is great news. Firefox is my browser of choice, but having written extensions for both Firefox and Chrome I must say that Chrome is far easier to develop for.

    I wasn't expecting this, but it makes sense - with Mozilla focusing on Electrolysis (their project to make Firefox multi-process) the existing API wouldn't work well because it wasn't designed with a multi-process browser in mind. I was expecting them to design a whole new API and then have to go through extensions breaking every few updates as the new API stabilised. Going with an existing API that's already mature and known to work for exactly the kind of architecture they're going for will make the transition a lot easier for both the browser devs and extension authors.

  21. Makes a browser irrelevant by Anonymous Coward · · Score: 0

    If extensions will end up being cross platform. It really makes the browser just a name. We already see so much similarities in UI of browsers. The extension capabilities are really all that set them apart. Actually if you do not use extensions you really have not cared much which browser you use. Just as long as its fast and renders web pages correctly. I really think when I see any browser comparison article it must be a slow day. The author cant think of anything to write about but how every browser out there is just about the same.

  22. I'd rather see Firefox... by rnturn · · Score: 1

    ... not screw up when executing JavaScript. Probably not possible given the sheer number of JavaScript programmers out there and the bloated web sites that employ them add just one more "nifty" piece of eye candy to the site. But a guy can dream, can't he?

    --
    CUR ALLOC 20195.....5804M
  23. Re: PaleMoon 4 Linux, including portable option by Anonymous Coward · · Score: 0

    Already a SourceForge project, complete with installer. Fairly universal: no distro-limited "packages" needed.

  24. Please leave Google out of this by Anonymous Coward · · Score: 0

    Even though Google had nothing to do with this the shitheads will always find a way to blame it for something. If you don't like Mozilla's decision then take it up with them and quit trying to blame someone for your problems.

  25. And then it will start using the Chrome engine ... by cascadingstylesheet · · Score: 1

    ... and along with Opera, I can have three versions of Chrome running!

  26. "There's more to see"? Block them by tepples · · Score: 1

    There are a lot of websites which demand an account to do much (pinterest).

    Solution: Start putting -site:pinterest.com in your Google searches, and block the site in hosts.

  27. Excellent! by Anonymous Coward · · Score: 0

    Now I know that Hurd 1.0 will be released before non-beta 64-bit Firefox for Windows. Thanks!

  28. Why not a new browser by tecker · · Score: 1

    If this is going to be such a radical shift in the way that the browser functions why not create a new project? The Phoenix/Firebird project (its name before Firefox) was born out of the need for a lightweight browser that focused on one thing. They rewrote the browser from the Mozilla suite and made it fast. The model they brought along is still close to what we have today. Now they want to overhaul and break the system radically. Just like then.

    At this point why dont they create a Firefox2 or a FirefoxNG browser with all of the new features, bring over the users automatically and essentially fork the dev? Just like with Seamonkey that kept the browser suite that was Mozilla going, we can keep the old FF1v44 version going. That way the old guys like us can backport the software improvements of FF2 and keep our old extensions. I have a feeling that many of the awesome extensions that exist solely on Firefox will die out because of the loss of functionality. Without those the browser starts to look a lot less appealing.

    At this point they might as well just rename it PrivacyFox and go the way of Opera, just use Blink but strip out all the tracking. Crankshaft JS could use a bunch more devs.

    --
    Procrastinating life a way at a rapid rate of speed.
  29. Re: PaleMoon 4 Linux, including portable option by jkflying · · Score: 1

    And if I want to uninstall?

    --
    Help I am stuck in a signature factory!