Except that the system that removes culpability, visibility and consequences of this kind of abuse is set up deliberately to avoid liability and consequences of such actions.
This isn't a tee-hee accident, this is deliberate organizational design which removed any kind of bad consequences or even thought about what the software does to user from the engineers at Microsoft. They're happy about that. They now don't need to deal with that. And if you'll ask them, they will refuse a change that will make them responsible for abuse of their users.
and even with all of that in mind, this was not a coordinated microsoft attack against wireguard. which was my point.
i am in no way defending microsoft. just pointing out that the conspiracy-theorists suggesting that some exec at microsoft specifically targeted wireguard for whatever nefarious purpose was, well, a conspiracy.
You're trying to make a difference where there is none. Yes, they didn't say "we'll attack wireguard". They said "we'll setup our processes so apps like will end up being abused to save us effort", which is the same, just packaged into bureaucracy.
It's kind of bizarre how y'all pretend that systematic bearocratic evil doesn't exist. After being brainwashed about its evils in USSR for your young live.
So you buy exact same generation of Intel and AMD chips to your developers than your servers and your cutomsers? And encode this requirement into your development process for the future?
No? That would be ridiculous. You’re inventing dumb scenarios to make your argument work.
It’s more like: some organizations buy many of the same model of server, make one or two of them their build machines, and use the rest as production. So it’d be totally fine to use march=native there.
You just wouldn’t use those binaries anywhere else. Devs would simply do their own build locally (why does everyone act like this is impossible?) and use that. And obviously you don’t ship these binaries to customers… but, why are we suddenly talking about client software here? There’s a whole universe of software that exists to be a service and not a distributed binary, we’re clearly talking about that. Said software is typically distributed as source, if it’s distributed at all.
There’s a thousand different use cases for compiling software. Running locally, shipping binaries to users, HPC clusters, SaaS running on your own hardware… hell, maybe you’re running an HFT system and you need every microsecond of latency you can get. Do you really think there are no situations ever where -march=native is appropriate? That’s the claim we’re debunking, the idea that "-march=native is always always a mistake". It’s ridiculous.
Did you consider that your talking about GROUPS of people where _some_ individuals from ALL groups regularly behave poorly and deserve criticism and action?
Or is that too much of a nuance against tribal thinking?
Why do you think I'm not aware of this? Did I not just explain how different people who do the activity have different perspectives, priorities and proclivities? Did I not just explain how I disagree with the way some cyclists conduct themselves, while plainly being aware that not all cyclists are like this?
Maybe none of this way apparent to you, despite it being plainly written out in simple English, because... I don't know actually. Can you explain your failure to read?
That's an interesting mindset, since those 30+ tech savvy millennials are the ones that actually still have some money to spend left on apps and similar crap.
You're angry about a huge amount of outright misinformation here.
reply