Comment Re:Wasn't allocation always the problem? (Score 2) 306
If MIT had to give up some of their IPv4 addresses, maybe we'd get IPv6 openafs this century
If MIT had to give up some of their IPv4 addresses, maybe we'd get IPv6 openafs this century
New Zealand needs a free, open, and thriving Internet. The Internet should be an open platform built on free speech, innovation, and democracy. It’s time to develop positive, rights-affirming Internet law to protect human rights in both the online and offline world.
Consistency and availability are competing requirements. It is trivial to keep the files in a SageMathCloud project consistent if we store it in exactly one place; however, when the machine that project is on goes down for any reason, the project stops working, [...]. By making many copies of the files in a project, it's fairly easy to ensure that the project is always available, even if network switches in multiple data centers completely fail, etc. Unfortunately, if there are too many users and the synchronization itself puts too heavy of a load on the overall system, then machines will fail more frequently, and though projects are available, files do not stay consistent and data is lost to the user.
and boldly summarizes
The architecture that we have built could scale up to a million users.
It is actually possible for the language to prevent certain classes of vulnerabilities. See Ur/Web. That's not what Perl is doing, but...
Ur/Web is an interesting language with a type system designed to reject vulnerable web programs as ill-typed. The compiler itself is written in a safe language — Standard ML, and there is a proof of language correctness included.
And it should be the law: If you use the word `paradigm' without knowing what the dictionary says it means, you go to jail. No exceptions. -- David Jones