[Kranar]

Too late for that, I am in a decision making position at a quant firm with very strict engineering standards and I absolutely stand by my decision that businesses that write code that compares booleans together like that should not be in a position to hold back other businesses that don't.

They can continue using 20 year old compilers and quit making the language worse for the rest of us who have put in the effort and cost of writing modern software.

[PH95VuimJjqBqy]

It's always easy to make a decision when you're not the one paying the cost for it, or don't imagine you will be.

In fact, one of the red flags for decision makers is the inability to understand the above tenet.

[Kranar]

I agree, asking everyone else to pay the cost of writing error prone code because they refuse to adapt but yet feel entitled to use new compilers is a big red flag and poor technical decision making that offloads the cost on the rest of the community.

I'm glad we managed to get that out of the way.

Companies that wish to stick with their existing and deprecated coding standards can stick to their existing and deprecated compilers, allowing those of is who wish to have safe and modern tools the freedom to make progress without their baggage holding us back.

[PH95VuimJjqBqy]

oh snap guys, do you see what he did there in his parley? The way he took my point and pretended I was saying something else and that I really agreed with him. That technique so got me that he won!

This is most definitely the paragon that should be helping us decide which large swathe of people to fuck over.