>Only if you use the time saved to write more data than you would have with a slower drive
Well, NVMe SSDs do get quite hot due to much higher data transfer speeds, and higher temperatures lead to faster flash memory degradation, although I have no idea how important it is in practice (probably on the order of an SSD dying in 10 years instead of 20)
> co2 and pm should both go down with windows open.
Very much depends on where you live. I have a few DIY air quality stations with data being piped to Grafana. I just looked at the latest data, the average outside PM level for the past 5 months has been around 100 µg/m³, while inside it's around 10 µg/m³.
This spring happens to be pretty windy and this skews the outside levels down, otherwise the ratio would be much worse.
>It's not uncommon that zooming will make the text smaller
At least in Firefox you can enforce the minimum font size through settings without using any third-party plugins or custom themes (look in about:preferences → "minimum font size"). I have it set to something like 16 or 18.
This doesn't fix the actual problem, but I gave up on trying to change the world a long time ago.
So? Do you think filesystem metadata is stored in a magical pixie cloud, or on the same unreliable physical hardware where it can easily get corrupted, especially after a crash or an unexpected power loss?
f2fs (at least in its state a couple of years ago) is/was a prime example of how a filesystem can get into a barely working state with massive amounts of data and metadata corruption, and not even notice it.
God I love this site. In case of a minor disagreement with someone don't even bother to think, just press "downvote".
The other way to interpret this would be "it was the only filesystem to detect corruption on my malfunctioning hardware", because that's what usually happens in the last few years.
I am sure that Western Digital (whom the author of this patchset works for) will be very interested in your opinion. He implements whatever makes business sense for WD, and not what some random forum commenter wants. I am not at all surprised that a storage vendor would want upstream Linux support for its upcoming devices before they're actually being sold in stores.
Wouldn't that draw more attention to the research patches, compared to a "normal" lkml patch? If you (as a maintainer) expected the patch to be malicious, wouldn't you be extra careful in reviewing it?
Do they only break for users in the United States? I've been using Firefox exclusively since about 2.0, and I've never had any of the Google projects break for me. Not once. Yet this seems to be a pretty common problem around here.
Well, NVMe SSDs do get quite hot due to much higher data transfer speeds, and higher temperatures lead to faster flash memory degradation, although I have no idea how important it is in practice (probably on the order of an SSD dying in 10 years instead of 20)