AnyOldName3

Someone doesn’t understand the Windows design language. Anxiety would be a yellow warning triangle. That’s a red error circle, so something really has gone wrong and you’re right to be panicking about it, and better remember what it is before the consequences become too dire.

The pun doesn’t even make sense unless the term was already in common use when Hopper wrote it. If you don’t already know what a computer bug is, the note sounds deranged.

At the moment, they’re already at risk of being removed by the government, who can make them illegal, and simultaneously at risk of being removed by payment processors, who can prevent the stores from operating. It makes no difference to the government whether they’re also the payment processor. They could remove them anyway. Having two entities with unilateral power to remove something can’t be worse than just having one of them.

They can do a really shit job of administering payment processes in a transparent and democratic manner before they end up being worse than the status quo where it’s entirely untransparent and undemocratic. Also, governments already have the power to make things they don’t like illegal, so there’s no reason to expect they’d block payments for things they’ve left legal, whereas payment processors currently block plenty of legal things.

Blahaj policy is very explicitly that it’s a safe space, and transphobia and transphobia-adjacent content (and other forms of bigotry) will be removed. It’s supposed to be somewhere people can go and have it taken as axiomatic that their neopronouns are valid, and therefore they won’t have to debate them, so while it’s pretty reasonable to say that you’d prefer people grew to be happy with they and neopronouns didn’t become a permanent feature of English because they’re awkward, it’s not Blahaj-friendly, so can’t be said on Blahaj, especially if you’re going to repeat it a lot.

It’s perfectly reasonable for people to like crisps, but it doesn’t mean I have to let people keep adding them to my cake when I’m trying to eat cake.

Soldiers are supposed to question potentially-illegal orders and refuse to execute them if their commanding officer can’t give a good reason why they’re justified. Being in charge doesn’t mean you’re infallible, and there are plenty of mistakes programmers make that the compiler can detect.

For a start, having a garbage collector doesn’t mean its use is mandatory, but even in a language where the garbage collector is mandatory, keeping an array alive as long as any references to it exist doesn’t stop you doing things like getting muddled about its length and reading/writing past the end. Mandatory garbage collection only prevents temporal memory bugs like use-after-free, not spatial memory safety bugs like buffer overruns, which need to be prevented by other mechanisms like bounds checks.

Garbage collection doesn’t guarantee memory safety and it’s perfectly possible to create a memory-safe language without garbage collection. There are plenty of garbage collectors for C++ (and until C++23, support for garbage collection was part of the standard, although no one implemented it), and languages like C# let you interact with garbage-collected objects in unsafe blocks.