The_Decryptor

Sounds a hell of a lot like my Australian school experience.

My high school was great, if you were doing poorly in a class then next year they’d put you in an easier class to bring up your average grade (And if that didn’t work, then they’d just ignore you).

1. If your ISP doesn’t do IPv6, then you’re fine (But should look for a better ISP)
2. If your ISP does do IPv6, then you should install the patch now (Unless you’re not using IPv6 on the LAN, in which case you’re fine but get a better router/sysadmin)
3. If your ISP does do IPv6, but you can’t install the patch for whatever reason, only then should you disable IPv6

The problem is people recommend disabling IPv6 for random unrelated reasons (Like gamers claiming it decreases your IPv4 latency), so yeah MS is going to be insistent that users not fiddle with things they don’t understand because it’s really unlikely they’ll go back and restore that config when it doesn’t actually help.

Ideally you don’t directly ship the code it outputs, you use it instead of re-writing it from scratch and then slowly clean it up.

Like Mozilla used it for the initial port of qcms (the colour management library they wrote for Firefox), then slowly edited the code to be idiomatic rust code. Compare that to something like librsvg that did a function by function port

c2rust: Am I a joke to you?

although I’m not sure what USB4 Gen 3×1 is, but it’s only x1 so can’t be that good, right?

It’s the initialisation mode of USB 40Gbps, luckily not something users will have to deal with