You’re approaching this with the attitude of a parent who’s already got their future grandkids named.

Happy cake day.

The article just before that about the “missing missing reasons” hits just as hard. That whole site makes for an informative read for someone frustrated with dealing with their parents as an adult.

Make a bingo card out of the phrases:

• “We didn’t do anything wrong.”
• “We paid Company X to do that.”
• “What’s a computer license?”
• “How much do they want?”
• “If it’s free then why are we talking?”
• “If it’s free then what did we pay Company X for?”
• “What does GNU mean?”
• [… some time later …]
• “Can’t we just pay them?”
• “Don’t pay Company X because they fucked this up.”
• “Why do we have to give everyone the changes we paid for?”
• “Whatever. I don’t want to hear about this again.”

Add your own phrases. It’s a fun game for all ages.

RHEL9 and forward require v3, and the numpy in pip as of a few versions back uses either v2 or v3 instructions, so v1 is silently broke for certain workloads. FreeBSD works on it just fine as do Debian based distributions as long as you don’t need recent versions of numpy, but there’s no telling what else out there just tries to run and fails with an illegal instruction.

Try the c++23 standard. There’s been a lot of cross pollination. Contrived example follows:

#include <format>
#include <numbers>
#include <print>
#include <string>

int main(int argc, char *argv[]) {
    double pi = std::numbers::pi;
    std::string fstr = std::format("{}, {:>.2}, {:>.5}, {:>.10}", pi, pi, pi, pi);
    std::string h = "Hello";
    std::string w  = "World";
    std::println("{}, {}!", h, w);
    std::print("This won't have a {},", "newline");
    std::println(" but this will add it."); // Add a newline.

    // Can't put a non-constant string as the first argument to
    // print or println so they can be checked at compile time.
    std::println("{}", fstr);
    return EXIT_SUCCESS;
}