> Let’s put it another way. What happens if Intel enables AVX2 for AMD and it doesn’t work? The "safe" thing to do is rather than work through all of these cas

> Let’s put it another way. What happens if Intel enables AVX2 for AMD and it doesn’t work? The "safe" thing to do is rather than work through all of these cases you've considered, is to just give up on it. > No offense but it is hard to respectfully respond to something like this, even though I know it wasn't directed at me personally. I hope you don’t think about coworkers with this mindset. I didn't intend it to be disrespectful. It's not a value judgement. Maybe these aren't the best terms, but I've worked on both what I would call "low consequence" software, and "high consequence" software. The tolerance for decision making about things like swapping out hardware is different. In some cases, this can be done with little hesitation. In other cases, it would cost millions of dollars to test the system to the point where it could be trusted. Maybe the solution to the internet pitchfork wielders is for intel to simply stop trying to serve both of these sets of users with the same software. But I suspect they simply don't care about this problem enough to do anything.