bjorney

Pagers operate at a lower broadcast frequency than cell phones. Longer wavelengths (low frequency) are less impeded by walls and interference.

Yes, but if someone trips over the cord there is a 50% chance the wrong side comes unplugged and potentially kills them, hence why they don’t make these cords

It’s unavoidable - once the cheese gets hot enough the steam will either force the liquid cheese out of existing holes, or it will make its own holes.

Make sure they are fresh out of the freezer when you put them in, as this lets the outside crisp up more before the inside becomes lava. Once you get close to the prescribed cooking time, you need to just sit in front of the oven door and watch them, and as soon as 2-3 break open, take the whole tray out

You can just point your domain at your local IP, e.g. 192.168.0.100

Not with 64gb ram and 16+ cores on that budget

You could set it up in docker whilst still on windows, and then all you need to do is copy/paste your compose file onto your new Linux machine, that way you aren’t struggling to learn two things at the same time (alleviates the “I don’t know if the problem is with my docker config or my host OS”)

“how dare they use the right tool for the job without taking the time to learn how to do it sub optimally first”

Python 3.12’s compiler tells you to fuck off

OSError: File or directory not found “C:WindowsSystem32”

It’s markdown, if it detects “[number][period][space]” at the start of a line it converts it to an HTML ordered list, which always starts at one. You should be able to escape it with a \ before the period to bypass the markdown

4. I wrote "4\. "

Crunch wrap & fries supreme (🇨🇦)

The fries supreme are just a shadow of their former self though, 20 years ago they were the best fast food item you could get

To elaborate a bit more, there is the MySQL resource usage and the docker overhead. If you run two containers that are the same, the docker overhead will only ding you once, but the actual MySQL process will consume its own CPU and memory inside each container.

So by running two containers you are going to be using an extra couple hundred MB of RAM (whatever MySQL’s minimum memory footprint is)

it won’t necessarily take twice the resources of a single mysql container

It will as far as runtime resources

You can (and should) just use the one MySQL container for all your applications. Set up a different database/schema for each container

Yeah but then ALL even numbers would be slow to compute because you would have to chain through every odd before you know that 2 is even.

Depends on the expected distribution of input values