The add-on, First Party Isolation, linked from the article, to

https://www.bleepingcomputer.c...

is something of a turd. There is no indication that it is doing anything. The preference page has no controls. The icon that is placed in the menu bar shows no state information—supposedly if you click on it, the FPI feature will be disabled for five minutes. There is absolutely no indication that anything happens when you click on it. plus, the icon is so hard to see that at first I thought there was no icon at all. The linked article mentions that you can also edit two entries in the about:config page. Nice if a little obscure. But you might think that the add-on would simply toggle these items, but installing the add-on does not affect these about:config items. So, again, the FPI add-on is poorly designed.

Does it still suck memory like my ex-wife sucks dick?

Someone at Gizmodo should be shot or sued for editing the memo, "Google’s Ideological Echo Chamber," by removing the references—"hyperlinks," as they call them. The hyperlinks are to many scholarly journal pieces and otherwise respectable publications. Without the references to back up the author's claims, he just looks like a boob to most folks.

Here is a link to a PDF that contains all the hyperlinks to references and also two missing figures left out from the Gizmodo version.

https://assets.documentcloud.o...

Why don't those Mozilla imbeciles spend a a few days making Firefox so that releases some memory after it is done with it? It's normal to have FF sitting there WITH NO OPEN WINDOWS using 1.5-2 GB of RAM.

LibreOffice, after these many years, still has many problems. Here is an example of a very basic one: at least on macOS, it does not properly render text, leaving unevenly-spaced characters within some words—one letter will appear e.g. too far to the right, colliding with the character to the right, while leaving a too-large space to the left. It is ugly and impedes reading.

The Writer component, continues to be essentially worthless for technical writing. Its rendering of inline math leaves giant white space to both the left and right sides of math. It has no idea how to break equations across line breaks of inline math. It does not correctly reduce the height of inline equations. I can't help but notice that the entire 50+page user's guide to the math typesetting function doesn't once display an inline equation. And Write has no ability whatsoever to intelligently place figures and tables—they are treated simply as giant characters.

"Three times as many pixels means three times the resolution."

WRONG. Three times as many pixels means sqrt(3) times the resolution.

Of course, the Google-powered Raspberry Pi devices will all phone home. Right?

I think one reason 3D TV never caught on is that the screens generally were not large enough. There is a problem with a finite screen when objects appear near the left or right edges and relatively close to the viewer: the required binocular disparity is such that the image in one eye goes black (blank), leaving the image in only one eye. This is very uncomfortable, even if it happens for a brief instant. The screen needs to be large enough for the left and right edges to be nearly out of ones peripheral vision so that then one eye goes blank it is less noticeable. Most movie theater screens are large enough. But still, the director needs to be aware of this problem and be careful not to place up-close images near the edges of the screen. I think James Cameron knew this in making Avatar. I'm sure that Martin Scorsese did not know this when he made Hugo, as this happens many times during that movie. With TV, especially live action sports, I suspect that this might be hard to control.

Of course, the other problem is the disparate needs for the viewer to focus at one distance (the screen) and cross the eyes at another distance (the object). Most people adapt to this nearly instantly but I suppose even they find it a little fatiguing.

Surely it is faster to block an ad than it is to load it and render it.

This work goes beyond the normal logical confusion of "correlation implies causation." It's just a really poorly designed experiment. A better experiment would have compared blood flow in brains of people who have never used marijuana and them had them use marijuana and then again measured blood flow. (This also lacks a control but at least it measures something useful. And I spent all of five seconds coming up with it and I'm not in the field. So.....)

So what's wrong? Maybe people who have abnormally low brain blood flow are prone to using marijuana, perhaps even to _increase_ blood flow, but less than perfectly. And instead of _causing_ psychosis, maybe people who are psychotic are prone to using marijuana. I know people who have told me that they need to use marijuana to feel normal, and maybe normal for them means non-psychotic.

Does Servo leak memory like a sieve like Firefox, causing one to relaunch one or two times a day or watch memory use climb to > 1 GB?

It is absolutely astonishing that it has taken _this_long_ for someone to make these basic fixes to C.