> ould just be a matter of iterating from A until you hit the end point and counting, right?
Yes, you could brute-force all the points. The good thing is, ECC is done on fields that are very large, so that actually enumerating them is not practical. Check out Curve25519[1] for some numbers.
The rules are somewhat imprecise, but basically any functional cookies do not need to have consent as it is implied by the user using the service. This includes thinks like the user-identifier to know who is logged in for example.
The issue is usually less what species gets endangered or faces extinction, but the fact that this is not done for progress but for greed (be it humanity or corporations).
Destructively changing anything should be approached with extreme care, since you cannot un-extinct a species.
I'd illustrate it like what happens on Linux when you are approaching OOM situations. You can either kill other processes, not knowing what they did or if they were vital, or just stop doing what you were doing. And so far societies have usually decided that mines are not as important as raw materials at some point.
What do you mean by 'hard to please'? The joke about the compiler being some beast you need to sacrifice a goat to seems to put the blame on the wrong end of the computer imo.
Unless what you are doing is not fit for what guarantees Rust gives you, the compiler should just be a crutch in case you missed a step.
If you can see the exchange happen, then it is not really private. You don't need to know how much I spent, but just that I spent something. That already is enough to not make it private anymore.
There is the choice of preact[1], that has a very similar api, is more lightweight and even has a compatibility layer for the few react packages that need it.
Yes, you could brute-force all the points. The good thing is, ECC is done on fields that are very large, so that actually enumerating them is not practical. Check out Curve25519[1] for some numbers.
[1]: https://en.wikipedia.org/wiki/Curve25519