There’s a reasonable probability that I’ll be heavily downvoted for this, but it’s my two cents, so here I go. For clarity, I’ll in the following use “male” and “female” to refer to biological groups identified by their reproductive organs (by far most people can clearly be identified as one or the other), and “man” and “women” to refer to groups of people that identify as such.

Sex (the action) is pretty fundamentally tied to your reproductive organs. As such, I think it makes most sense to define “straight” vs. “bi” vs. “gay” in terms of sex (the attribute). I would say that a male that is exclusively attracted to females is “straight”, while a male that is exclusively attracted to women “bi with a strong preference for women”, and that a male that is exclusively attracted to males is “gay”.

My reasoning here is twofold: First, a male that is attracted to women can have a range for how “female presenting” the woman has to be before they are interested. Some will only consider women that have gone through surgery and full hormonal therapy attractive, while others will find women without any surgery or hormone therapy attractive. This brings up the second point: A lot of sexuality becomes a lot easier to talk about (and de-stigmatize) if we accept that sexuality is a continuous spectrum. If we accept that, it makes sense to me to use one word for each extreme, and a more fluid language for the bulk of the spectrum. I know plenty of bi people that have more or less strong preferences towards one side of the spectrum, and some that are completely agnostic. I think a lot of stigma can be removed if we’re more open to people being “just slightly bi”, while we can keep the language clear by reserving “straight” and “gay” for the two extremes.

Finally, if we use “straight” to refer to e.g. males that are exclusively attracted to women, we open an unnecessary can of worms regarding males that are attracted to people who identify as women, but don’t present as female. In short: Sex (act) is fundamentally tied to sex (attribute), so it makes sense to me to define sexuality in terms of sex, rather than gender.

These two are not interchangeable or really even comparable though? Make is a program that generates non-source files from source files, cmake is a high-level tool to generate makefiles.

If you’re writing anything more than a completely trivial makefile I would heavily recommend learning cmake. It makes your build system much, much more robust, far easier to maintain, much more likely to work on other systems than your own, and far easier to integrate with other dependent projects.

My primary experience with plain make was when I re-wrote a 2000+ line make-system in a project I maintain with about 200 lines of cmake, because we were setting up some CI that required us to clone and build some dependencies, which was an absolutely PITA to handle cross-platform with plain make, but was trivial with cmake.

PS. The cmake docs suck for anyone that hasn’t used cmake for 10 years already.

I don’t mean to say that C++ is in any way without faults. If performance is crucial, that can definitely be a reason to forgo some of the guard-rails, and then you’re on your own.

I guess my issue with the “C++ is unsafe”-trope, is that it usually (in my experience) comes from people not having heard of all the guard-rails in the first place, or refusing to use them when appropriate. They write C++ as if they were writing C, and then complain that the language is unsafe when they’ve made a mistake that is easily avoided using stl-containers.

As I said: There are tools in place in modern C++ that are designed to catch the errors you make. If you are using a raw pointer when you could have used a reference, or accessing an array without range checking, those are choices you’ve made. They may be valid choices in your use-case, but don’t go complaining that the language is “unsafe” when it gives you the option to code with guard rails and you choose to forgo them.

Memory unsafe C++ is a choice. With modern C++ you have no excuse for accessing raw pointers or arrays without range checking if memory safety is a priority.

What you say is true, but doesn’t really answer “Could someone take down Wikipedia [without completely shutting off the internet]”. For obvious reasons, shutting internet access completely off isn’t going to happen short of an insurrection or a war.

Shutting down Wikipedia specifically is much harder. As others have pointed out, there are many thousand copies of Wikipedia lying around on peoples private devices. If Wikipedia were actually taken down (blocked by the government in some sense) hundreds of mirrors would likely pop up immediately, and it would be more or less impossible for the government to go after each individual site that some person decides to host, short of just cutting internet access completely.