3 ms·
Two thoughts: 1) You're absolutely right that writing extensions for Firefox is harder than writing extensions for Chrome. But that's in no small part because
by smacktoward 12y ago
Two thoughts:
1) You're absolutely right that writing extensions for Firefox is harder than writing extensions for Chrome. But that's in no small part because Firefox has been around for something like twice as long as Chrome has; and really, Firefox's add-on infrastructure goes back even further, all the way back to the original Mozilla suite. Which means Firefox is carting around something like 15+ years' worth of legacy infrastructure with it. There are lots of bits of technology that Made Sense At The Time™ (XUL and RDF manifests, for instance) that just seem needlessly baroque today.
It's possible to imagine them ripping all that out and starting from a clean sheet of paper, but that wouldn't necessarily be an unalloyed good for developers. After all, backwards compatibility is a Good Thing for developers too; just for developers who have already gotten into the platform, rather than those seeking to get in now.
Rather than have a Great Break and throw out all those years' worth of extension developers' work, Mozilla has instead been making incremental improvements to extension development -- creating things like bootstrapped extensions (https://developer.mozilla.org/en-US/Add-ons/Bootstrapped_extensions https://developer.mozilla.org/en-US/Add-ons/Bootstrapped_ext...) and reducing the dependency on things like RDF that nobody wants to work with anymore. This is a pragmatic approach, but it will require a very long time for it to get Firefox to a place where it can compete directly with Chrome on this front.
Which leads me to point 2...
2) Imagine that Firefox didn't have to worry about all that legacy support, and really could start from a clean sheet of paper.
Would it be worth it?
My personal sense is that browser extensions in general are a technology that's on the far side of the adoption bell curve. As the Web itself becomes a more capable platform, many scenarios that used to require an extension can now be handled quite well by sites on their own. And anecdotally, I see a lot less interest in extensions among the "normal users" I interact with these days than I did, say, 10 years ago.
So, if you're Mozilla, maybe you could make extension development cleaner, but it's just not worth the effort to do so. Why plow developer time into improving something that few people care about today and fewer will care about tomorrow? Maybe it's best to just remove the most obnoxious problems by tweaking around the edges, and let time take care of the rest.
Which, come to think of it, sounds a lot like what they are already doing...
- tbirdz 12y ago>My personal sense is that browser extensions in general are a technology that's on the far side of the adoption bell curve. As the Web itself becomes a more capable platform, many scenarios that used to require an extension can now be handled quite well by sites on their own. I disagree. Many kinds of extensions are designed to work across multiple sites, and add functionality most websites would either be unwilling or uninterested in adding. Consider extensions like Ad Blockers, Privacy Extensions preventing tracking, HTTPS Everywhere, No Script, download managers, extensions which affect the browser display as a whole (such as Tree Style Tabs), etc.
- smacktoward 12y agoTrue, but (1) for better or worse, these are all things that are of interest primarily to the clued-in nerd audience, not the public at large; and (2) the greater capabilities offered to extensions are a double-edged sword. It's true that extensions can do things that sites cannot, but that also means that they can compromise users' security and privacy in ways sites cannot too. In a world that's a lot more security-conscious than it was 15 years ago, a decent argument can be made that the security risks highly empowered extensions present outweigh the value they bring to the table. (That's a decision that ultimately rests on how popular they are with the mass audience, too; it's easier to shut down a security hole that nobody depends on than one that millions of people do.)
- reubenmorais 12y ago…which is why the add-on review process is time consuming, and why AMO shows you half a dozen warnings before letting you install an unreviewed add-on.
- smacktoward 12y agoRight -- which is (part of) why interest in extensions is declining. It's a self-reinforcing pattern: platform vendors tighten security on extensions; extensions can now do less and are harder to get, so fewer people try them; which makes it easier to tighten the security screws on extensions the next time around.