On Thu, 2017-10-12 at 19:54 +0100, Richard W.M. Jones wrote: > On Thu, Oct 12, 2017 at 09:05:33AM -0700, Kevin Fenzi wrote: > > It's true that a number of older extensions will not work. > > Well, looking at the most popular extensions: > > https://addons.mozilla.org/en-GB/firefox/extensions/?sort=users > > hardly any of them are parked as "compatible with firefox 57+". > I'm counting 5/20 on the first page linked there, and 4/20 > on the first page of the highest rated extensions. > > So I stand by my slightly modified claim that installing this update > will disable most of your extensions. I think you might be surprised how many *new* WebExtension alternatives are available, but they are not yet popular when competing against the *old* standbys. IMHO, Mozilla could have done better with epoch weighting, displaying the legacy tags far earlier -- those are really quite recent. I was also annoyed that I couldn't easily limit my search for non-legacy extensions when using firefox < 57. I learned about this incompatibility while dealing with an unrelated issue in VimFx several months ago and was sad to learn that extension would not be ported given the differences and the amount of time it would require. I began a panic search for replacements because of how utterly dependent I am on some. I think many popular extensions are going to fall into this category if they're not backed by companies or enthusiasts with lots of time. So I'm happily testing from u-t now so I can convince myself everything is going to be alright. I'm not going to judge whether this via u-t was correct or not; I've heard great arguments while perched atop of the fence. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
