> I know precisely zero people who have EVs and do not charge them at home. The cost differential is enormous and completely changes the economics of cost per mile.
I know multiple people who have EVs and don't have a home charger, so do 90%+ of their charging at work. You're there 8+ hours a day anyway, and many workplaces provide free charging, so it ends up even cheaper than charging at home.
My 35 floors building has exactly 2 chargers. Both are FIFO, max 5 hours or you start parking and both are slow af and pay for charge. Charging M3 on one of those is probably a whole day activity and would cost you probably more than if you get a diesel generator running to power charger.
So I might not know those people, but know of at least 10 teslas that aren't charging at home every day, because usually those spots are taken by polestars.
If you have a free work charger, that's almost as good as having charging at home. Most people do not have this, and even if you do then you would be SOL if you switch jobs.
It's not like you get the permit before you have even bought the land and designed the plans/architecture/engineering for the data center.
You have to do all of that first, and only once all of that is done, can you submit for a permit.
Which can take not just months, but maybe even a year (or more).
So the situation is, regulation changed during the planning phase. So what do you do now? You obviously can't deliver on a contract that would cause you to break new laws/regulations - that didn't exist when you started all of this.
> The only way to know if software does what is intended is to use it.
No, testing and code audits also work.
No amount of use of the software will tell you what else the software does beside what is intended (exfiltrate data, etc); testing and code audits both help with that.
Testing is not a replacement for use, but it can help exercise code to the extent that the author can predict how the software will be used. A significant source of test cases come from using code and finding defects. No amount of auditing or proactive testing replace real world use.
> 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!
reply