AngriestLettuce

> how do you respond if they ask for proof that nobody has fallen off the edge of the earth?

The same way you should respond to all questions. Truthfully. You have no proof, and you don't care to waste your time looking for it. If that is a showstopper for the conversation, it was never worth having in the first place. Simple as that.

I'm saying that they have different motivations behind their views, and should therefore be argued against in different ways. Lumping them together like that is not helpful, it is shameful.

I know all about not being allowed to exist, just for being who you are, trust me, I do. I also know a lot about convincing people to LET you exist, rather than choosing between crushing your enemy, subjugating yourself to them, or running away. There is usually a better way. That seems to have been forgotten in modern days, but it certainly still exists.

It starts with following the site guidelines of arguing in good faith and assuming the best out of your opponents. In your view, "cannot exist in public view" and "cannot exist in practice" are one and the same. In their view it is not.

What you are doing is ASSERTING your reality over someone else. That's not a very nice thing to do, whether you're right or not. You WILL have pushback. If you want to convince people of the veracity of your views, you cannot hold that pushback against them. Certainly react to it, certainly defend yourself, but don't hold a grudge against people just for daring to fight you in the first place.

They might be wrong and you might be wrong. In this case, I'm inclined to agree with your view here, but that doesn't mean that people who don't are bad people. Just misguided.

If you want people to show compassion for you and your plight, start by showing compassion for them and theirs. Anything else is quite frankly a waste of time.

Isn't that just taking absolute authority from an external source again? Am I missing the joke here, or is the joke yet to unveil itself?

Yes. They are not the same, and you know this. These social pressure tactics do little but turn people against your cause at this point. The difference is in intent. While it is possible they look the same from the outside, one intends to protect what they love, while the other intends to hurt what it hates.

Making these people out to be the same serves to turn people who might be convinced to help you into your worst enemies instead. No one likes being made out to be a bad person simply for seeking to protect what is important to them. The two are not the same, and too many people screeching that they are, and that conservatives all hate trans people is the issue in the first place. It's weird.

> Why does your cohort want to force MIT to allow Nazis to march through their campus, but not force a baker to bake a cake for a gay couple?

Compelled action, versus compelled inaction. One requires you to force someone to do labour to further a cause they disagree with, the other requires you to stand aside and not physically prevent people from expressing themselves the way they want.

Seems pretty clear cut and easy if you ask me.

A front end is simply an application that talks to a different application to receive its data instead of processing it directly. It can be as threaded as you like.

Keep it simple. Have global state where it needs to be global.

The easiest way to avoid problems with multithreaded writes to globals is to not have multithreaded writes to globals. Ensure all writes to said global only occur in one thread. One possibility is to use e.g. locks and semaphores to ensure only one thread writes at a time, but nothing can beat the amazing synchronity that is imperative programming. Try it out some time. Tell your friends.

The real secret here is that there are very few things that actually need to be globally writable. Most things that are global should be constant, so not a problem. For those which aren't, you probably have some kind of IPC message passing thing in your programming tool of choice. Use it to pass any state changes to global state to your main thread, which changes it. Be aware that race conditions may happen. If they cause you issues, make them not happen any more. Don't worry so much about life.

There will be problems with every approach. Pick one with few problems, and deal with them as they come. Multithreaded programming is inherently complex. No need to make it worse than it is.