I said

solar and wind are intermittent and therefore not ideal for dealing with real-time grid demand

The grid has to meet demand in real time. You can’t make the wind start blowing within a few seconds to ramp up supply, and battery technology isn’t capable of storing enough juice to handle this either

That’s why the grid uses different power sources, each with different response times, each serving a different purpose

• Nuclear has slow reaction time, so is used to handle the bulk of daily power
• Then natural gas and coal have faster reaction times, and can be used to fill in as demand varies minute to minute

I never said solar and wind cannot be added to the grid

The reason i discount solar is that, (i’m assuming) carbon capture requires equivalent amounts of energy that was produced by burning the hydrocarbons

This means, we would need to produce roughly double our current energy consumption (1x to continue current consumption, 1x to carbon capture at a rate comparable to historic carbon emissions)

Also, solar and wind are intermittent, and therefore not ideal for dealing with real-time grid demand. However, that may make them ideal for passive carbon capture

Carbon capture is the inverse of burning hydrocarbons (fossil fuels). You have to dump energy (from the grid) into a chemical processes that “refines” the air back into concentrated carbon

The only way this thermodynamically is viable is with a surplus of carbon neutral energy

So either nuclear, or fusion

(There’s no way solar or wind generate enough energy, for several decades at least)

Think of it more like pre-canned build scripts. I can just write a script (DockerFile), which tells docker how to prepare the environment for my app. Usually, this is just pulling the pre-canned image for the app, maybe with some extra dependencies pulled in.

This builds an image (a non-running snapshot of your environment), which can be used to run a container (the actual running app)

Then, i can write a config file (docker-compose.yaml) which tells docker how to configure everything about how the container talks to the host.

• shared folders (volumes)
• other containers it needs to talk to
• network isolation and exposed ports

The benefit of this, is that I don’t have to configure the host in any way to build / host the app (other than installing docker). Just push the project files and docker files, and docker takes care of everything else

This makes for a more reliable and dependable deploy

You can even develop the app locally without having any of the devtools installed on the host

As well, this makes your app platform agnostic. As long as it has docker, you don’t need to touch your build scripts to deploy to a new host, regardless of OS

A second benefit is process isolation. Should your app rely on an insecure library, or should your app get compromised, you have a buffer between the compromised process and the host (like a light weight VM)

How do you know those formulas are correct?