371 karma · joined November 23, 2017
As a non-american, please don't speak for us all. Also, using word "obviously" doesn't substitute for factual evidence. There are plenty of people skeptical about WHO's handling of the situation outside US too.
I sync my org files using a low-tech solution: I have a .dir-locals file that injects a post-save hook that automatically commits changes to git and pushes them to the remote. It's stupid, but it works, and I never have to think about it.
OTP doesn't give you _state of art_ distributed consensus algorithms out of the box.
Replication is the cornerstone of fault-tolerance. When logic is written in high-level languages with some minimal good practices, most SW bugs result in crashes rather than data corruption, hence data replication plays important role in protection against bugs as well as HW problems.
> Consider a bug in software used for landing SpaceX boosters... Or a bug in a trading platform. Or a bug in an automated medicine dispense
I specifically mentioned: "Programmers _usually_ work with the data. <...>" In the examples you listed above software manipulates physical world rather than pure data. I thought it was too obvious to explain.
There is an explanation to this discrepancy. Risk = probability of fault * cost of fault. Programmers usually work with the data. Data has a pretty very unique property that it is easily and cheaply copied and restored. It also means data can be replicated more easily, which allows to build systems with large amount of redundancy. Therefore, price of a software bug is usually orders of magnitude less than the price of breaking something in the physical world. This allows to drive up probability of fault parameter and allows for much faster evolution and less regulation.
Ok, sorry for false accusations. I, too, never downvote anyone for the same reason.
My point is that different people pronounce things as they are used to, reflecting it in a writing system leads to complexity and inconsistency.
It does not? Creating a fully phonetic writing system that is also consistent is an impossible task. For example, different dialects can interchange "o" and "a" sounds, how this should be solved in a "proper" phonetic system?
This is far from being a general rule. Your example is an exception. Consider "мера", "монета", "обмен" and so on. You cannot change "e" to "э" in these cases.
So you're not arguing with my post.
If you remove infinite tape, you go from undecidable to "just" exponentially complex.
Such compiler would require solving halting problem. Most problems related to search of formal proofs are undecidable.
Hmm, I have personally trained Erlang to half a dozen juniors and interns. Any person who knows basics of programming can pick it up and write/fix mundane business code in less than a month. And I am a horrible teacher.
Chrome used Trojan horse tactics to get into the computers. Back in the 2010s when it just appeared, almost any popular freeware installer got sneaky "Also install Google Chrome and make it the default browser" checkbox.
So, underhanded tactics are extremely efficient. Therefore, I expect that Firefox will keep losing shares. Making a better browser won't help them.