Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Sunday August 13 2017, @12:08PM   Printer-friendly
from the firefox-loses-yet-more-users dept.

Firefox 57, which is slated for release on November 14, will "only run WebExtensions", according to Mozilla.

This is expected to break compatibility with many existing Firefox extensions, and in many cases there aren't WebExtensions-compatible alternatives available for these extensions.

During some recent discussion at Slashdot, it became clear that some users have nearly all of their extensions classified as "legacy", and susceptible to breakage.

Members of the SoylentNews community, if you use Firefox, how many of your extensions are set to no longer work with Firefox in the near future?

If Firefox 57 breaks compatibility with your existing extensions, will this finally be enough for you to discard Firefox and find an alternative browser to use?

Will this extension breakage, and subsequent loss of users, effectively end the viability of Firefox as a modern web browser?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Sunday August 13 2017, @07:28PM (2 children)

    by Anonymous Coward on Sunday August 13 2017, @07:28PM (#553337)

    I don't think BSD's approach made the difference. If BSD was as popular on the desktop as Linux it would attracted the same shitstains and end up with the same sound server problems. You've still gotta have PulseAudio if you want Skype, etc.

    It's hardly fair to blame Linux when half the time the sound server isn't serving the client or the hardware, it's just sitting there in the middle, taking up space. People want to write these deep stacks. Look at Android, with ~120ms latency typical not that long ago, on what is essentially a proprietary stack, the devs just don't care. When they realized this was a problem for musicians, they started targeting 50ms. (Musicians want about 9ms.) As far as latency in sound stacks go, developers by and large don't care, or even when they do, are so out of touch they miss the point.

  • (Score: 2) by kaszz on Monday August 14 2017, @03:09AM

    by kaszz (4211) on Monday August 14 2017, @03:09AM (#553447) Journal

    Skype is a spy tool for En-Ez-Ay that delivers a copy of your face every 5 minutes to their storage. So not much reason to keep it around.

  • (Score: 1, Informative) by Anonymous Coward on Monday August 14 2017, @11:35AM

    by Anonymous Coward on Monday August 14 2017, @11:35AM (#553597)

    Musicians want about 9ms

    Most places say 20ms is the limit before it becomes audible, but that's end to end. E.g. if you are using a soft synth app, that's 20 ms from the keyboard, through the midi router, through the USB driver into the midi stack, into the app, generating the sound, back out through the sound stack to the line out.

    So yeah, 9ms for just the audio stack is probably on the high side.