I’m still onboard with rust as being better than C, however…
My understanding is that it is considerably harder to correctly write unsafe rust than it is to correctly write c, because if you accidentally violate any of safe rust’s guaranteed invariants in an unsafe block, things go bananas.
So what, Japan just colonized most of Asia to spread zen vibes? Or, you know that time Ghengis Khan raped and pillaged his way all the way to Eastern Europe? Or, failing that the repeated wars between Egypt and the Hittites? Even the native Hawaiians fought wars between the islands prior to their colonization. Conquest, genocide and enslavement have been the human condition for all of history everywhere without exception.
Preemptive edit: This doesn’t excuse any of it and we are finally, maybe barely moving past it, but the only reason it seems like this is a western phenomenon is because the most recently globally dominant nations are from there.
Modern optimizing compilers are magical. I would need to check assembly but I would actually expect the if to be hoisted out of the loop entirely to relieve pressure on the branch predictor.
It does. I use this port
You need to me careful about benchmarking to find performance problems after the fact. You can get stuck in a local maxima where there is no particular cost center buts it’s all just slow.
If performance specifically is a goal there should probably at least be a theory of how it will be achieved and then that can be refined with benchmarks and profiling.
Sync that has never broken for me and works on a phone. My attempts at keypass with both google drive and syncthing invariably ended up with me needing to periodically do manual reconciliation. I’ve never had this problem with bitwarden. Also, bitwardens passkey hooks work on iOS. They appear unsupported by keepassium.