> I'm not color blind

Well... uhm, you may want to verify that claim.

Either everyone lives or you don't get to experience the mess that follows when red wins cause you're dead. Sounds like a strictly better option indeed.

> If they want GPL except it's proprietary then they can do that.

Only if they don't use the text of the GPL to do that, as it's not a freely licensed work (more specifically, they'd have to use a different name, remove mentions of GNU and remove the GPL preamble to be able to use the rest of GPL as a base for their license).

Thanks, I was baffled by this licensing thing and how it was being reported. Suddenly it all makes much more sense now.

Only if you had no hardware nor software mixing configured, which probably should be considered a misconfiguration of your system.

> this seems an impossible feat

What makes you think so?

It makes sense to me, we're talking about a highly addictive psychoactive substance. It's much harder to get out of addiction than not get addicted in the first place, and people born after 2008 did not have a legal way to get addicted yet. That's exactly how I'd approach having a transition period to not cause unnecessary suffering in the process.

More like a custom which sometimes has good reasons to be broken than a golden rule. A branch in Git is nothing but a pointer to a commit, anything more than that is social agreement that can differ in various contexts.

Yeah, I've never used Jujutsu, but from what I've seen so far everything it does can be done with Git itself, just perhaps in a (sometimes significantly) less convenient way.

Sure, true, I would say "often significantly" though, to the extent that you would never bother doing half the things with git that you can do with Jujutsu because it's such a pain.

Some will say that it's a "red flag", others will say that those saying it's a red flag lack the experience of working on diverse set of projects with various needs and requirements.

> Some will say that it's a "red flag", others will say that those saying it's a red flag lack the experience of working on diverse set of projects with various needs and requirements.

What if those who call out red flags actually do so based on experience,particularly in understanding how and why red flags are red flags and why it's counterproductive to create your own problems?

I mean, if after all your rich experience working on diverse set of projects with various needs and requirements, your answer to repeatedly shooting yourself in the foot is that you need a tool to better aim around your toes... What does it say about what lessons you draw?