No. You want a parametrized "Money" type, one that can do calculations in varying numbers of decimals, and configurable rounding. There are legal requirements that make this necessary.
One (from memory, not exact) calculation I've had to implement for a customer:
Multiply prices by whole numbers. Prices are given in cents subdivided to 5 digit precision, result should have 10cent precision, rounded down. Then, for the tax calculation, get taxes from some tables, 3 different taxes for each line item. Apply the first two taxes, Euros with 10 digit subdivisions, then round "according to trade custom" (which is the usual "up from .5 cents, down from below .5"). Then add the third tax, Cents with 5 digit subdivisions, round down. Then add all the line items and their taxes, separately as well as together.
And if there is a Skonto, take care to properly unravel the tax stuff again.
I've had to do it in plain Typescript, it is possible, but it really sucks. Those days when you yearn for COBOL... ;)
Out-of-order execution isn't the reason for this. The C standard assumes an abstract machine that allows OoOE, of course, but even with strict in-order hardware UB can hit you at any time, even before you'd think it could. That is because the C standard doesn't limit UB to any constraints like "following lines" or "subsequently executed instructions". Independent of the hardware, the compiler is allowed quite a bit of reordering of instructions. The standard just requires that (some) effects of those executions are ordered as written, but that doesn't include UB.
So if you have UB in your future path of execution, the compiler might just do whatever _right now_.
> The fact that it appears on the Senate building probably refers to the Roman meaning.
The roman meaning is very much fascist, if phrased in modern terms. Fasces were carried by lictors accompanying a roman official, symbolizing the "imperium", or absolute, king-like power, held by that official over his domain. While for a time, the imperium of lower officials was somewhat curtailed during the republic, military commanders with imperium still held the absolute and immediate power over life and death of their subordinates (other officials still had power over life and death, there just was an opportunity for citizens for appeals and vetoes by equal-ranked officials) . Lictors with their fasces were not only bodyguards but also a small police force at the discretion of the commander, who would seize an offender, hold him for a drumhead trial by the commander and then punish (e.g. execute) him if so decided. Under the later roman dictatorships the dictator (imperator, emperor or caesar) of course also held those powers, with the same symbolism of imperium represented by the fasces. Fasces always have been a symbol of capital punishment, justice by drumhead or thumbs down, and absolute power.
No, the Roman fasces are not fascist. Imperial Roman power is not fascism, even if fascism tries to fashion itself to Imperial Rome. If A claims inspiration from B, it does not mean that they're the same thing nor interchangeable.
The difference between the two is 2000 years and one being an entire civilization that spanned hundreds of years, and the other a relatively short lived political ideology, based on reactionary nationalism, autarchy and later anti-semitism (racial purity was more a Hitler kinda thing).
Roman imperial power isn't fascism in that some important aspects do differ. E.g. fascism uses a special kind of modern aesthetics that Romans wouldn't recognize, even if fascist monuments copied Roman building style. Fascism also practiced a cult of youth and rejection of conservativism that is quite the opposite of what the Romans practiced (as far as the 2000 years of separation allow us to compare this). In that sense, you successfully built a straw-man argument ("Imperial Roman power is not fascism") and disproved it.
But, more importantly, "imperium" doesn't mean what you think it means. There are two meanings to "imperium", one being the overall realm that Rome controlled, the Roman empire. This is the meaning you did use in your above straw-man. Usually, this meaning of imperium is represented by symbology such as the eagle and the S.P.Q.R. signature. Italian fascists also used those symbols, but the international fascist movement mostly didn't, because just the Italians wanted to rebuild their Roman empire. However, the fasces represent the second meaning of "imperium", which is the absolute power of one single individual official to rule and impose order in his assigned domain or subdomain. They represent the ordering principle of fascism and nazism that a strict hierarchy of individual leaders ("duce" in Italian, "Fuehrer" in direct German translation) should rule the state ("Fuehrerprinzip" in German). Fasces also represented the primacy of punishment and violence in imposing order, of swiftness and immediacy in carrying out justice, very much what modern day fascism wanted to return to. So Roman fasces are representing what modern day fascists intended for the principles of leadership, justice, punishment, and order to look like. But beyond those aspects, there can be no inference made, because modern-day Fascism encompasses more aspects than just those.
That there is a 2000 year difference between the cultures in which to interpret the aforementioned symbolisms is a problem indeed. However, it is a problem that was created by people like the americans thoughtlessly using symbols because "well, Rome was a republic, we want to build a republic, let's just steal all of their iconography". Even back in that day, the actual meaning of fasces was known and clear. It was known and clear to the Romans as well. Hell, look at the list of uses for fasces in the wikipedia article: mostly police forces and departments of corrections, monarchies and off-with-the-heads mobs (such as the early french post-revolution order).
In German, there are no two terms for those, both are called "Hakenkreuz". And the Nazi ideology actually made references to eastern culture and peoples, claiming that Germans were descendents of the Aryan peoples: https://encyclopedia.ushmm.org/content/en/article/aryan-1
And while Nazi antisemitism was of course descended from the traditional christian antisemitism, there were also parts of the Nazi movement that called for a replacement of christianity by an "Aryan" or "German" religion, which seems to have been a mixture of Germanic/Norse religion and more modern esotericisms.
So yes, while eastern religions are blameless for what the Nazis made of their symbol, it also isn't of christian descent either.
Because, while the same problem exists, it doesn't exist to the same extent. The average size of the vehicles is smaller, even bigger European SUVs are far smaller than what americans call trucks. And there are less of the really big and deadly ones, almost none with a neck-breaking-bar, etc.
You don't need oil, just rope works as well. Every DIY store (at least over here) has loose manila fibre for that purpose. Wrap into the thread, screw it together, done. The not-so-nice problem: It might leak at first. The nice feature: The fibres will soak up water (thats why oil is actually counterproductive), swell up and make a tight fit after half an hour or so. You can even readjust the angle (other than with PTFE tape), it'll just drip for another half hour.
Right, there are multiple variations but they generally work in skilled hands although I learned from plumbers who always used oil (although using oil was always an imperative with gas pipes). Using oil usually negates the initial leaking whilst waiting for the hemp to dampen and swell.
Edit: I agree that using oil is counterproductive with water pipes—initially at least. I was taught by both plumbers and my father (who wasn't a plumber but a mechanical engineer who worked on power station boilers) that using oil is better in the long run as it prevents the hemp from rotting and thus premature failure of the seal. Moreover, using one oil-based method means that
a plumber cannot get confused and leave oil off gas connections where it's essential.
(I'd add that when referring to oil I'm specifically referring to linseed oil (even though I've seen some plumbers inappropriately use engine oil) because it slowly polymerizes and hardens even in the absence of air. This adds to the seal's effectiveness and further protects the hemp.)
Lab bench to product can be 15 years or more, so doesn’t mean it doesn’t work.
The other hard thing is beating Li-Ion. It would have to be a lot better or cheaper to beat the economy of scale. Just a little better won’t displace the incumbent.
That's the thing: Lithium ion batteries are not a fixed technology, they're a moving target. They've evolved dramatically and encompass many different chemistries since they first appeared in the lab in the 70's. But since they're all grouped under the name "Lithium ion" people just think of them as a fixed, static, mature technology.
It would really depend on the situation to be decided, whether MS would have to pay up, or rather the company using MS products to handle customer data. One can imagine a way to use MS products that might not be illegal, e.g. never use it to process personal data, use anonymized accounts that are not bound to a real person, swap around accounts and computers to prevent association with a person, etc. Then, all it would take for MS to get its 'get out of jail free'-card is to publish that in a whitepaper and make all the problems just be an unfortunate misconfiguration by the company using MS products.
Microsoft can already claim that you can use Excel legally by only ever using it as an expensive calculator or table layout generator.
A theoretical methodology to do so is not enough to make their spyware legal.
There are alternative products that can do almost everything Excel does in almost every real life company without consuming data like the Very Hungry Caterpillar. It's up to them to prove why they need all that data that others don't need, and in what specific ways this data is used for the good of the customer.
Microsoft will need to act and change to solve this problem.
That’s a good point: The use of general-purpose tools like Excel is by essence non-GDPR compliant, since there is no way to mark a column as “person” and therefore attach it to that person’s rights.
Therefore, all corporate tools must be specific for one purpose when managing PII, and no tool should allow free-text fields. Excel, Access, notepads shouldn’t exist in companies.
The point isn't about the tool, it's about where and by whom the tool is run.
Office 365 is cloud based, that's what makes it potentially non-compliant. Having Excel in your company, on your computer, and the data never leaves that computer is a totally different scenario.
Imho, the "FUD" is largely right and most cloud platforms are indeed illegal.
However, due to enforcement being absent or taking ages, there are too few legal decisions and big expensive enforcement actions that one can point to. Currently everything is really still fear, uncertainty and doubt, the hammer hasn't come down yet. I'm not sure if it ever will, at least not before EU institutions or other member states such as France force Germany to stop dragging its feet.
It's a bit tedious to work in that climate of uncertainty. Every time we want to use some AWS service it prompts endless discussions.
On the other hand it made us research and use European alternatives such as Hetzner (they have a cloud too, although with less SaaS offerings), OVH or Scaleway.
One (from memory, not exact) calculation I've had to implement for a customer: Multiply prices by whole numbers. Prices are given in cents subdivided to 5 digit precision, result should have 10cent precision, rounded down. Then, for the tax calculation, get taxes from some tables, 3 different taxes for each line item. Apply the first two taxes, Euros with 10 digit subdivisions, then round "according to trade custom" (which is the usual "up from .5 cents, down from below .5"). Then add the third tax, Cents with 5 digit subdivisions, round down. Then add all the line items and their taxes, separately as well as together.
And if there is a Skonto, take care to properly unravel the tax stuff again.
I've had to do it in plain Typescript, it is possible, but it really sucks. Those days when you yearn for COBOL... ;)