I assumed that by them saying "installing desktop Safari" they are using an OS other than macOS since Safari comes preinstalled on macOS and can't even be uninstalled at least not without disabling System Integrity Protection.
Yeah and this time they won't let them get away.
According to Finnish Minister of Defence: "The authorities in the Baltic Sea region have learned from the mistakes of the Baltic Connector investigation and are prepared, if necessary, to stop a ship in the Baltic Sea if it is suspected of being involved in damaging communications cables."[1]
And it looks like according to marinetraffic.com that the Yi Peng 3 is indeed at full stop surrounded by at least 3 Danish navy vessels.
20 hours later they are cited that they cannot board without China's approval. Legally uncharted grounds whether they could or could not. Looks they take the cautious side for the time being.
Superior methodology (transcending numerous cultural / psychological / cognitive norms and obligations) is how I would go about it.
For example: banning the conflation of opinion and fact, like what's going on (and always goes on) in this thread, a behavior that is protected (doing otherwise "is not what this site is for").
If an imperfection is noted: log it, investigate, improve. Rinse, repeat.
Also: best prepare one's will, life insurance, etc before undertaking such a project.
That provides the basis for solving precision and rounding issues but for a money library you need more abstractions. The ability to assign a currency code and supply conversion rates and convert between currencies at a minimum.
The thing is, it doesn’t really help. A system I’m working on can have hundreds of monetary amounts in the same currency. Storing the currency against each one is an awful waste of space.
Equally the allocation trick is good, but you’ll find that the people who really care about this stuff really care about the exact algorithm you’re using and who it favours.
I think it helps to have the inputs and outputs of the system fully representing a "money" (i.e., a monetary amount + its currency code in places like API resources, events, and so on). This way you can internationalize or support multi-currency processing if that's the case. That's (if I remember correctly) what the payment card services companies (e.g., Mastercard, Visa) do by default in their message exchanges when calling the issuer for transaction confirmation.
Might be a minimum for a money library (not completely sure what the absolute minimum would be). It would be an application design choice to not use one and stick to general fixed point/Big Num constructs.
Even though my gut reaction is to agree with you, it’s true that it is an app design decision, so in certain scenarios it might very well be a good design decision.
it depends, if it was a currency exchange, it'll be labeled in one of 3 ways, either average rate per unit, absolute, or it'll be a reference to a MSSQL table containing exceptional spot transactions. Otherwise, a complete history of exchange rates is stored in KDB, most days you can take the average, and for small amounts on weekends or days the exchange is closed you can just interpolate, there's also a half dozen XLSXs full of certain exceptional days, so you'll have to check that you're not on one of those lists. Then if you're not dealing with USD->X or CAD->USD->X things start to get hairy.
"For as long as we’re able (and assuming the cooperation of the extension authors), Brave will continue to support some privacy-relevant MV2 extensions—specifically AdGuard, NoScript, uBlock Origin, and uMatrix"
Why take the word of the developers of a Chromium-based browser, some of whom may not even be part of the project in the long run? Firefox is built on an entirely different engine and doesn't have this problem.
reply