> I suspect the intent is to move stale things out of RAM so it can be immediately used for more productive purposes when needed.
These are separate problems, though. You can clean a page by updating its backing store without purging it from memory; and purging a clean page doesn’t require a write. It’s definitely reasonable to take advantage of idle IO resources to clean dirty pages, but pages should only be purged (clean pages first, usually) when there’s an immediate need for them for something else.
That depends if the goal of handling your own traffic is integrity (which a VPN can give you) or availability (which requires dedicated pathing through a leased line).
It does if you are ray tracing. They are trying to find the source of a theoretical photon that hits the screen at the present time, the source will therefore have been in the past so they need to run time backwards as the photon moves away from the camera.
> But wouldn't we want to see the black hole? One could send a ray through every pixel of a screen, and let them go around the black hole and hit its surroundings. And if the rays are sent back in time, it's as if one received the light emitted by the surrounding objects in the past!
Ordered one for OpenFOAM. Excited for it. Will be nice to not have my laptop running CFD 24 hours a day, but my M1 Max is currently my fastest machine… I’m expecting about 3.5x from the M5 Ultra.
How would that work for all the software that distinguishes between them? The standard (see e.g. Mathematica) is for `return` to create a new line in a multi-line text field, and `enter` (`fn+return` on a keyboard without a dedicated key) to execute/evaluate/commit the field.
> How many customers do you expect to be running on Duo for the first year of its existence?
I’d be surprised if it was >0.01% for anyone.
How do you figure? Assume the average Apple cell phone replacement cycle is somewhere between 3 and 4 years. At the longer end, you’d need the sell-through rate of the Duo compared to other phones to be less than 0.04% to hit your number. We know from the Mini and other phones that Apple tends to avoid designs that it expects to have less than a 5% sell rate, two orders of magnitude higher. Even if you assume they’re aiming for 5% of dollars instead of units, and you take into account the non-Apple market (which certainly should not be unit-weighted for folks thinking about app revenue), you’re off by well over an order of magnitude.
Why? If you’re spending 2000 hours a year servicing your current customers, surely it’s worth 20 hours to add on 1%, even ignoring that that 1% is probably more valuable than your average customer, and the halo effect of giving a good experience to existing users migrating devices.
Although maybe they should because someone willing to buy a $2000 phone on launch is probably more willing to buy a lot more things versus someone who keeps phones a long time.
These are separate problems, though. You can clean a page by updating its backing store without purging it from memory; and purging a clean page doesn’t require a write. It’s definitely reasonable to take advantage of idle IO resources to clean dirty pages, but pages should only be purged (clean pages first, usually) when there’s an immediate need for them for something else.
reply