SoylentNews is people
SoylentNews
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?
(Score: 2) by coolgopher on Monday August 14 2017, @02:56AM (4 children)
Ah yes, Chrome/Chromium. I once had an xterm gobble gigs and gigs of memory (I like big scrollback buffers, and I cannot lie). Couldn't find which of my gazillion terminals would've gotten that ridiculously large. Installed pstree. Turns out the offending xterm was the one I'd started Chromium from (and was now hiding under the browser). Gazillions of warning printouts had piled up over some weeks. Taught me two things - code quality is questionable in that browser, and more importantly, start it in the background and close the terminal!
(Score: 2) by maxwell demon on Monday August 14 2017, @08:05AM (3 children)
Or simply don't configure xterm to save an unreasonable number of lines.
The Tao of math: The numbers you can count are not the real numbers.
(Score: 2) by coolgopher on Monday August 14 2017, @08:13AM (1 child)
> Or simply don't configure xterm to save an unreasonable number of lines.
Madness!
If you can't accidentally dump a kernel or ten into your terminal without losing the real stuff, what good is a scrollback buffer in the first place?
(Score: 0) by Anonymous Coward on Friday August 18 2017, @01:44AM
Why 9is this only voted +2?
This is pretty literally the kind of stuff that sysdevs do because thing X is blocking normal method Y.
I've done split pipes to term and remote file where the remote link was unreliable and the term was the critical backup. I'd have been pissed to find it truncated.
(Score: 2, Informative) by Bot on Monday August 14 2017, @10:16AM
> Or simply don't configure xterm to save an unreasonable number of lines.
wow, the systemd devs deflection maneuver!
If only you put a reinforcing ad hominem it would have been perfect :)
To be fair, the amount of stuff dumped to stdout/err by a browser is not much relevant imho
Account abandoned.