Slashdot Mirror


Mozilla To Ditch Firefox Extensions?

An anonymous reader writes "Although some have raised concerns about how sane switching to Jetpack is, it seems that Mozilla's new gadget is bound to replace the powerful extension mechanism we know. Maybe Mozilla wants to replace all the great add-ons we use daily with gadgets that add an entry to the Tools menu, or maybe they just want to draw thousands of inexperienced developers into putting together a bunch of HTML and CSS that won't integrate in the UI. It seems to me that in light of recent decisions we've discussed before, Mozilla isn't going in the right direction. What do you think ?"

20 of 415 comments (clear)

  1. TOO MANY LINKS man! by erroneus · · Score: 5, Insightful

    Seriously. Provide a link to the main stori(es) and that's about it. All this extra stuff is simply extraneous. How can we RTFA if we don't know which is the real frikken article?

    1. Re:TOO MANY LINKS man! by clang_jangle · · Score: 5, Interesting

      I disagree, the links seem appropriate in their respective contexts.
      However, TFS' question strikes me as superfluous -- FF already has lots of extensions of questionable quality. They're simply looking to transition to a new implementation of extensions, which hopefully will bog the browser down less and create fewer security issues by sticking with simpler code. Can't see how that would be "the wrong direction", frankly...

      --
      Caveat Utilitor
    2. Re:TOO MANY LINKS man! by Enderandrew · · Score: 5, Insightful

      I believe all Chrome extensions are pure HTML and JS. Many people have criticized that learning how to use XUL is a pain, and that most memory leaks and instability issues come from poorly coded extensions. Everytime Firefox has a major release, they break all old extensions. People either update/re-write their extensions or they don't work anymore. If Mozilla says the latest Firefox requires your extension to operate as pure HTML and JS, it wouldn't be the end of the world.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    3. Re:TOO MANY LINKS man! by ColdWetDog · · Score: 5, Funny

      WTF? What about all those extensions that change Firefox UI, like Vimperator? Or those that use XPCOM to write files and launch apps? How can you do that in HTML and pure JS?

      Look, it's a web browser. If you want an operating system, go download Emacs.

      --
      Faster! Faster! Faster would be better!
    4. Re:TOO MANY LINKS man! by Ziekheid · · Score: 5, Insightful

      The only reason I'm currently still using Firefox is because of some unique extensions, you can fully control how your browser looks and how it operates. With this functionality removed I would have no reason left to stick with Firefox.

    5. Re:TOO MANY LINKS man! by bheer · · Score: 5, Insightful

      Mark parent +1 insightful. Compare Chrome's adblocking vs Firefox's, for example. Firefox wins. And there are lots of cool, useful addons, like TabHunter, which is a cool way to navigate through lots of tabs. Or FireFTP -- an FTP client that works wherever Firefox does. Or DownThemAll, a download manager that works wherever Firefox does. And so on.

      I think what Firefox _really_ needs is a Chrome-like Task Manager that shows you exactly how much memory/CPU/network your add-on is consuming. For example, on Chrome I know that the Gmail checker add-on takes 10MB memory, and ~0 CPU/network. I can always uninstall it if I think that's too much. Maybe when Firefox's Electrolysis project for per-process tabs goes mainstream, this feature will be implemented.

    6. Re:TOO MANY LINKS man! by CAIMLAS · · Score: 5, Insightful

      I think what Firefox _really_ needs is a Chrome-like Task Manager that shows you exactly how much memory/CPU/network your add-on is consuming.

      I have been rallying for this functionality for years. It would improve the Firefox situation so, so much, and would likely provide a very useful tool for plugin/extension writers to troubleshoot/debug their work more thoroughly. Quality would go up across the line.

      The way things are going, browsers are becoming more OS like every couple months. Gazelle is supposed to be the furthest implementation of such things to date, but Chrome is already well within "useful and well designed" territory.

      What we need is the ability granularly manage independent elements within our browsers, because they're running a huge variety of different code: extensions which perform separate tasks; javascript on many different pages, Flash, embedded video, Java, etc. Really, when it comes down to it, most peoples' browsers are running more independently developed instances of code than they are running actual applications. (For instance, I'm running Firefox with 14 extensions and 3 plugins right now; I'm only running 6 independent applications, in addition to firefox).

      The way it stands, Firefox is on par with Windows 3.1, in terms of process management. The closest thing to managing processes we've got is "taking a long time" javascript detection. Flash crashes, and Firefox crashes (unless you're using a crap wrapper). Extensions lead to Firefox leaking, and there's no way to granularly manage any of the data.

      I saw Chrome's "process manager" for the first time the other day and was quite impressed. The fact that Google collects information via Chrome, and its limited extension/plugin repository (which doesn't provide the functionality I want) has so far kept me from giving it much of a serious look, but now, I'm having second thoughts.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    7. Re:TOO MANY LINKS man! by rtfa-troll · · Score: 5, Insightful

      With this functionality removed I would have no reason left to stick with Firefox.

      You are so right. If they really did do this then they would lose so many of their users. This is so perfectly Netscape of them and as such I'd like to link to a suitable story from Netscape's past in the hope to god that the Mozilla people can learn from the past.

      Dear Mozilla people:

      • if you are defining a new plugin interface only use it if it's better
      • if it is better; then implement the old interface using the new one. If you can't then it isn't better.
      • prove that you can refactor the plugins so that 95% or more of old plugins (and 100% of popular ones) work in the new system
      • Until you get 90% of old plugins working, don't let the new system anywhere near production.
      • Make it the responsibility of the people with the new interface to get the refactoring working for those 90% of plugins.

      It's so simple. The new should not be allowed to break the old. If the new has to do that, then it's design is bad.

      --
      =~ s,(.*),<sarcasm>$1</sarcasm>,g if any_point_you_wish();
  2. Car Analogy by Anonymous Coward · · Score: 5, Insightful

    Removing extensions from Firefox is like removing the guns from a tank.

  3. this isn't news... by new+death+barbie · · Score: 5, Insightful

    It's rabblerousing. Slashdot, news for the hard of thinking.

    Editors, please try to give these stories at least a pretense of fairness. Unless you need this for your application to work at Fox News.

    --

    It's supposed to be completely automatic, but actually you have to press this button.

  4. Is that you Steve? by Zero__Kelvin · · Score: 5, Informative
    From the linked Firebug blog, paragraph 2 states, in its entirety:

    "I don’t think these changes will have a big impact on Firebug. Firefox will continue to support extensions while the jetpack technology matures. We can adapt as we go along."

    I think that if you want to spread FUD you should make sure that you don't link to a web page that makes this statement in the second paragraph Mr. Billmer.

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  5. No more AdBlock with JetPack by Animats · · Score: 5, Informative

    Right now, it looks like AdBlock, Flashblock, CustomizeGoogle, and my own AdRater couldn't be implemented under JetPack. The Jetpack API documentation has a section "Content - Methods for interacting with web pages. That's the mechanism anything that deals with ads needs. That leads to "Page modifications", which leads to This documentation is under development. Please see the page modifications API proposal for now."

    That leads to Jetpack Extension Proposal #17 - Page Mods, which discusses how to implement Greasemonkey-like functionality using Jetpack. Current status is "Implementing (since May 27, 2009)".

    So the functionality needed for AdBlock, etc. is vaporware. It's not even clear that, if implemented, the proposed mechanism would support AdBlock. The author of Adblock Plus wrote last month "Jetpack has to support Adblock Plus, not the other way around. As it is now, Jetpack isn't suitable for complicated extensions."

    It's significant that Mozilla gave priority to implementing "themes" and such, which are needed for vendor-branded browsers, while putting off implementation of user-oriented features like ad blocking. Is this a back-door effort to get ad-blocking out of Firefox?

    1. Re:No more AdBlock with JetPack by dzfoo · · Score: 5, Insightful

      That's the actual strength of AdBlock, and the reason it currently cannot be implemented as a JetPack: AdBlock has the option of blocking the ads when the URL is found in the source, therefore not loading it. It works at a lower level than what the JetPack platform offers.

      To me, ad-blocking is more than just not showing ads, it's about not being tracked by ad brokers that leave "web-bugs" all around the World Wide Web. Blocking requests to the ad servers themselves is what makes AdBlock far more useful than CSS and layout modifiers, and the primary reason I stay with Firefox in spite of its shortcomings. Adblock, together with the ability to black-list servers in the cookie manager with a simple "Remember this setting" checkbox, are actually the only reasons I continue to use Firefox.

              -dZ.

      --
      Carol vs. Ghost
      ...Can you save Christmas?
  6. Re:Toughts About Direction by Toonol · · Score: 5, Informative

    FF had tabs long before most other browsers (except perhaps Konquerer)

    I think that feature (and many others) were primarily copied from Opera.

    While I do think Firefox is bloating, and really think they've made some questionable decisions (such as force-feeding the terrible Awesomebar), I can't think of anything wrong with this move. The extension model needs revision, and only elitist bastards would be upset that they're making it simpler and more accessible.

  7. Mozilla has been floundering for a long time by duffbeer703 · · Score: 5, Insightful

    When Firefox was first released, it was a breath of fresh air -- a fast, effective browser that discarded the bloat which plagued Seamonkey.

    Firefox laid the groundwork that has brought us to the current state of browsers... there's a competitive market, except in the business space, where the inability to manage browser settings has made the enterprise the last refuge for Internet Explorer. Unfortunately, the project doesn't have the desire to expand its impact further -- they refuse to accept bug reports or feature requests regarding issues that are critical to business users, and shout you down when you try to complain.

    So you have this great browser, but you can't script the install, can't manage update distribution (ie. autoupdate is not appropriate in many use cases), and manage config in a sane way.

    Now instead of fixing those issues, they are "fixing" something that isn't broken -- the extension system that makes Firefox so cool for so many people!

    --
    Conformity is the jailer of freedom and enemy of growth. -JFK
  8. Re:Same as microsoft, gnome, etc dumb it down by plover · · Score: 5, Interesting

    Yet the extensions I have that are specifically bound to internals are exactly the ones that provide me with the most utility. The All-in-One Sidebar, Fission, FxIF, Cookie Button, FEBE, CLEO, User Agent Switcher, Xmarks, Exif Viewer, Aging Tabs, all those are bound to specific versions of Firefox because they're doing more than simply tampering with the http stream.

    Could Firefox handle the binding any better? Sure. Could the team provide a route to handle backward and forward compatibility better? Again, yes. But that's a detail in an abstraction facade, and not what it looks like jetpacks are trying to be. Jetpacks look like "Greasemonkey scripts made official" with Mozilla's blessing. (Or maybe I'm seeing them as more limited than they plan for them.)

    Maybe that's it. Perhaps Mozilla should instead be looking at adopting and integrating Greasemonkey technology, instead of trying to reinvent it.

    --
    John
  9. Re:Toughts About Direction by Anonymous Coward · · Score: 5, Insightful

    So you're arguing that we should make creating Firefox extensions difficult because good programmers make good software?

    I wanted to be clear because there are about a thousand arguments against such a position - of which I'm enumerate a few:

    1) good programmers != good application designers
    2) good programmers may not have the next cool idea
    3) even good programmers would like programming to be easier
    4) making programming more difficult than it has to be is NEVER A GOOD IDEA
    5) good programmers might not say "Lady Gaga-fier" but will say some stupid 3l33t non-sense. ...

    That said, I do hope that they keep extensions around for a while, as it seems Jetpack doesn't do everything yet.

  10. Re:Toughts About Direction by Warbothong · · Score: 5, Insightful

    I'm also concerned that the bar is already low enough that most of the extensions out there are total crap. By setting the bar on the floor, every idiot will be able to produce terrible jetpacks. Do you really want to wade through 100,000 crappy jetpacks to find the dozen nuggets?

    Voting systems, bloggers, word of mouth, the list goes on. That argument doesn't work online if there are lots of likeminded people (and if you think that your needs are different from everyone else's then there's no point looking no matter what system is used, since nobody else would have scratched your unique itch)

  11. Let Your Fingers Do The Walking by meehawl · · Score: 5, Informative

    Have anything to back this up, or are you just talking out of your ass?

    There's this new thing called The Google. It works really well. You just type something like "Gates.Foundation drug patents" and it lets you start to find out things for yourself. In this case, the first few links will lead you to find out about UNTIAID. Basically, the story goes like this. During the 1990s, developing nations (especially India and Brazil) began to amass the manufacturing capability and expertise to produce advanced pharmaceuticals for minute fractions of the wholesale cost of those drugs on the world marketplace, the price being set by the IP holders in Western countries who enjoyed the political access necessary to keep extending patent lifetimes and extensions almost indefinitely. At the start of the Noughties, a crisis was looming when several companies, mainly Indian, began retailing vast quantities of anti-HIV/malaria/TB drugs to poorer countries (mostly African) at costs way below what Western companies were prepared to sell at. For a while it looked as if literally half the world was ready to secede from the international patent system in an effort to provide medication for as many of their sick populations as possible. After several rounds of negotiation, within which the Gates and Clinton foundations were major players, a compromise was established. Rich Western countries, NGOs, and foundations made it clear that their aid money was contingent on poorer countries recognising Western patents and refusing to buy from "rogue" companies or countries. In return, their access to grant/loan/development monies was assured, and several cartels and exchanges established whereby these countries could purchase Western patent-protected medications or the right to produce such medications at "below market" costs (but still literally several times the cost of producing such medications outside the patent system). UNITAID is one of these exchanges. The Gates foundation is one of the major players in UNITAID, and its lobbying recently has concentrated on maintaining relatively high remuneration fees to the Western IP holders, thereby maintaining relatively high costs for the drugs. For the poorer countries, it's a classic Faustian bargain: they get grant money, but they have to spend much of this money buying higher-priced drugs. Given the public-private partnerships and funding/tax arrangements, it's a classic example of corporate welfare where grant money nominally allocated to developing countries is funnelled back to Western IP holders, either as actual cash or as tax deferments.

    --

    Da Blog
  12. Perspective by meehawl · · Score: 5, Insightful

    the people are still getting the drugs they need

    Many hundreds millions of people are getting necessary drugs. But many hundreds of millions are not. Transporting drugs at cartel prices from developed nations or even manufacturing them under licence has the effect, still, of restricting access to those drugs for poorer at literally orders of magnitude less cost, and also retarding the development of manufacturing and research industries within developing countries dedicated to producing their own drugs at fractional cost. Sometimes "aid" has the effect of eliminating development, a pattern we've seen again and again enacted in post-colonial economic systems.

    grant money freely given to them

    Grant money given along with conditions that it be spent within certain cartels with pricing set not by market forces but by manufacturers' lobbies is not "money freely given". Especially because the manufacturers get a double benefit: sales proceeds and tax credits because of their "charity" in selling their drugs "below cost" (that is, below the high cost they claimed they could seel these drugs for, whereas in reality their sales at these prices in developing countries would have been close to zero).

    As for "mass murderer", well, that wa snot my choice of phrase. It's a matter of perspective. In a couple of hundred years, when people are writing the history of late capitalism, they will add up the death toll, the literally billions of people who were allowed to die over a century or so because of the need to maintain the IP cartel system. Whether they will call that "mass murder" or "acceptable outcomes" depends on what economic system occupies the greatest mindshare in the most historians, and how out contingent, transient stage of late capitalism is viewed by them.

    In an analogous system, think of the hundreds of millions who perished because of slavery, that is, the labor-intensive practices of early capitalism designed to produce agricultural commodities within monocultures at low cost. At the time, even though many agitated against it, the slavery system was regarded for generations as a necessary evil. With time, as the utilisation of fossil fuels and the employment of non-slaved masses within the system industrialisation replaced slave labor, the slave system lost mindshare. It began to be seen not as something desirable and even ordained by God, but as an unnecessary evil. For the most part, its economic output was replaced by in-situ colonialism, a system whereby the laboring masses were forcibly employed within the borders of coutnries rather than being transported en masse to remote destinations. In time, that economic system also lost relevance and was supplanted by more efficient modes of production and consumption.

    Regimes change. Until it had developed sufficiently and established its own R&D and scientific regimes, the USA was one of the world's largest "pirate" nations. Right up until the start of the 20th century it was notorious for ignoring and refusing to recognise the IP and copyright systems of the "established" economic empires, allowing its industries to "steal" what they needed to ramp up their manufacturing. The more expensive products from the empires rarely had much chance of succeeding in the USA, unless they either sold at radically low cost or sub-contracted out their manufacturer at very unfavourable terms to native USA companies. Now that the USA has a huge stake in the current economic system, it effectively erects barriers to entry that prevent other emerging economies from doing what it itself did to emerge from backwater underdevelopment and a permanent existence as a low-margin commodities producer.

    --

    Da Blog