Funny enough, he was actually executing many of his supporters. The SA's/brownshirts helped Hitler rise to power; they were the Nazi party's own paramilitary wing.
However, they were also a political liability. As mostly working-class people (often left jobless in the lurch of the Great Depression), they wanted Hitler to follow thru on his promises of redistributing wealth. This brought them into the conflict with middle/upper classes and the army (which had deep root in the Prussian aristocracy). Taking out key SA leaders gained him massive approval from the army (which, as chancellor, he had not previously been able to control). Shortly after, he justified his action against "treasonous ringleaders" and passed retroactive legislation authorizing the killings.
Everyone seems to be attacking or defending the clock along thinly-veiled pro/anti-Trump lines. Let's pause for a moment and start a discussion about the underlying state of the world the clock is supposed to represent. To help with this, here's a short list of why the clock moved closer to midnight, taken from the 2017 Clock Statement written by the scientists who made the decision to move the clock:
As a reader of various online forums, I would like a community where I can read a broad spectrum of polite, well-thought out responses to current events. Leading up to the election, I wanted to hear from the Trump supporter, the Hillary supporter, and even the Sanders/Johnson/Stein supporters.
What I don't want is (1) spam, (2) astroturfing, (3) straight-up lying ["fake news"], (4) personal attacks, (5) abusive language, (6) people who can't follow context, and (7) simplistic/repetitive comments that don't add anything new.
I'm not looking for a bubble or a safe space or an echo chamber, but neither do I want to swim thru the sewers.
I wouldn't be completely surprised if they did open source Windows, but in a way that leaves out key drivers, subsystems, and applications.
We've entered the age of OPINO: open-source in name only. Android teeters on this boundary, because you've got to install the Google Play spyware to access most applications. (Tip-o-the-hat to the F-droid guys here... they almost make it possible to avoid Google.)
My first thought was revulsion: people don't want to be treated like children. They will start bringing decoy phones or even box cutters.
Then I saw that they're also being marketed toward schools. Treating children like children makes more sense.
Also, it's better that we have technology like this instead of denial features getting baked into the phones (as has been proposed in the past) by law or by corporate collusion.
Unfortunately, habituating your developers to call
What you have with Result<T,E> and especially Option<T> is the concept of null delivered in a purposefully non-ergonomic form, with the theory being that the extra explicitness will drive developers to write better code by default. However, that unwrap() escape hatch is mighty convenient; time will tell if the theory was right or not.
Failure is the best default. It's a harsh path that leads to stronger guarantees about data and behavior.
Sentinel values (like 1900-01-01) generate hard-to-find bugs and threaten the trustworthiness of your data. If you can't remember to check for null, you're certainly not going to remember to check for a sentinel value.
The recent shift in language design to favor non-nullability by default is probably a good thing: if you don't need null, it's nice to let the compiler/database enforce that for you. However, if you do need null--if the value of a variable/field can be unknown, for instance--it's best to use it and do the extra work. Muddle things with a sentinel value only if the inevitable consequences are acceptable.
"Anything can be used as money." => Nope, not really. The item must be in suitably common supply while still being somewhat scarce; it must be hard to forge; the recipient must be able to readily trust the authenticity and denomination of the item; it must be be fairly divisible; it must be durable/preservable, transportable, and convenient to exchange. And of course, it must be accepted by a critical mass of commercial participants.
in time developers will be glad Angular went this route
Maybe since Google's backing this, it will ultimately succeed. Corporate backing seems to trump everything.
Defending the constitution against a corrupt government sets a pretty damn great precedence if you ask me.
Let's have trials for the people who enabled and engaged in warrant-less surveillance first.
I've noticed several design suggestions in your code.