Then which Apple phone are you talking about? The iPhone 15 is pretty much the same size as the Pixel 8. The iPhone SE is the only small phone Apple seems to make, and from what I can tell from a quick search, they aren't selling a lot of them.
The iPhone 15 is 147.6 height x 71.6 width x 7.8 depth (mm).
The Pixel 8 is 150.5 height x 70.8 width x 8.9 depth (mm)
I would call that pretty much the same size.
No they don't? The iPhone 12 mini and iPhone 13 mini were the worst performing phones out of their lineup. Small phones are dead because hardly anyone buys them.
Then Linus responded pretty poorly (and ended up stepping down as CEO and is now a chief creative something or other iirc)
Linus didn't step down in response to this. I don't remember the exact timelines, but he either stepped down before this, or was in already in the process of transitioning to the new CEO when this happened.
No. Modern SSDs are quite sophisticated in how they handle wear leveling and are, for the most part, black boxes.
SSDs maintain a mapping of logical blocks (what your OS sees) to physical blocks (where the data is physically stored on the flash chips). For instance, when your computer writes to the logical block address 100, the SSD might map that to a physical block address of 200 (this is a very simplified). If you overwrite logical block address 100 again, the SSD might write to physical block address 300 and remap it, while not touching the data at physical block address 200. This let's you avoid wearing out a particular part of the flash memory and instead spread the load out. It also means that someone could potentially rip the flash chips off the SSD, read them directly, and see data you thought was overwritten.
You can't just overwrite the entire SSD either because most SSDs overprovision, e.g. physically have more storage than they report. This is for wear leveling and increased life span of the SSD. If you overwrite the entire SSD, there may be physical flash that was not being overwritten. You can try overwriting the drive multiple times, but because SSDs are black boxes, you can't be 100% sure how it handles wear leveling and that all the data was actually overwritten.
Micay stepped down as lead developer and foundation director. I'm not sure what role he has with the project currently, but it seems like he plans on leaving the project entirely, long term. I haven't heard of any controversy since then. They've been hard at work and actually added support for Android Auto last month.
It's been a while since I took statistics, but yes, I guess that is a binomial distribution. It does not influence the results in the way you are implying it does, though. The calculator does actually account for it (the Population Proportion input), and the sample size actually decreases the lower/higher your proportion is. My point was that a question like, "Do you watch anime weekly," is not like a question like, "How many hours of anime do you watch in a week," where you certainly couldn't assume a normal distribution for the number of hours watched.
Normal distribution with regards to what? "Do you watch anime weekly" is a binary question. There really isn't a distribution associated with that.
You don't need a massive sample size for surveys to give meaningful information. Play around with this sample size calculator if you want to see what the margins of error are: https://www.calculator.net/sample-size-calculator.html?type=2&cl2=95&ss2=4000&pc2=5&ps2=500000000&x=Calculate
- SLC -> Single-Level Cell, i.e. 1 bit per cell
- MLC -> Multi-Level Cell, i.e. 2 bits per cell
- TLC -> Triple-Level Cell, i.e. 3 bits per cell
- QLC -> Quad-Level Cell, i.e. 4 bits per cell
The more bits per cell you store, the more dense and therefore cheaper your flash chips can be for a give capacity. The downside is that it is slower and less reliable since you have to be able to write and read exponentially more voltage states per cell, e.g. 2 states for SLC, 4 states for MLC, 8 states for TLC, etc.
The Trine series is pretty fun. It's a 2.5d puzzle platformer game. There are some combat bits, but most of the game is puzzles. I'd recommend the second one.
the timer has no idea if it was triggered during last boot. It only has the context of "this" boot, so it will do it right after a reboot and set a timer to start the service again after a week of uptime.
This is not correct. Persistent=true
saves the last time the timer was run on disk. From the systemd.timer
man page:
Takes a boolean argument. If true, the time when the service unit was last triggered is stored on disk. When the timer is activated, the service unit is triggered immediately if it would have been triggered at least once during the time when the timer was inactive.
OP needs to remove Requires=backup.service
from the [Unit]
section so it stops running it when it start the timer on boot.