Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cmrx64
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
35 ms
·
421.
▲
by
cmrx64
10y ago
> > any nontrivial project will make use of unsafe blocks. I don't think that's actually true? Most projects make use of no unsafe outside of stdlib and a handful of crates.io crates.
422.
▲
by
cmrx64
10y ago
> Shouldn't community members get a voice in the decision making? They _are_ asking for feedback, after all...
423.
▲
by
cmrx64
10y ago
OP wasn't referring to GitHub.
424.
▲
by
cmrx64
10y ago
Currently, you don't serve files etc unless you manually pin them yourself.
425.
▲
by
cmrx64
10y ago
The Wayback Machine on archive.org has it, at least.
426.
▲
by
cmrx64
10y ago
Indeed. Even better, someone is already doing good work in that space ;) http://hwacha.org/
427.
▲
by
cmrx64
10y ago
See also http://www.neural-symbolic.org/
428.
▲
by
cmrx64
10y ago
Basically, https://en.wikipedia.org/wiki/Cache_coherence . You want to ensure all the devices on the bus have the same view of memory contents.
429.
▲
by
cmrx64
10y ago
I use hub whenever working with GitHub. It's quite nice, since the rewrite in Go.
430.
▲
by
cmrx64
10y ago
And as an aside, the ACM is currently collecting comments on revisions to their code of conduct. http://ethics.acm.org/code-of-ethics/code-2018/
431.
▲
by
cmrx64
10y ago
For anyone reading the thread, this is an absolute must-read paper if you're at all interested in the near-future of production cryptosystems in high-risk settings.
432.
▲
by
cmrx64
10y ago
No, not even close to a few hundred years. No more than ~20 years at this point. https://www.keylength.com/en/4/
433.
▲
by
cmrx64
10y ago
The C code is manually written.
434.
▲
by
cmrx64
10y ago
Depends on what level of detail you're interested in. You could check out ADA/Spark or Dafny. Or, investigate something like Isabelle/HOL or Coq - perhaps via http://concrete-semantics.org/ or http:/&#x
435.
▲
by
cmrx64
10y ago
There are more papers coming out soon about eliminating covert channels at the design/kernel level!
436.
▲
by
cmrx64
10y ago
Delivery of page faults is, handling of them isn't (although the kernel does abstract the exact mechanism, into message delivery).
437.
▲
by
cmrx64
10y ago
That's not what isolation is meant here: if there is a connection between applications that allows cap transfer, they aren't isolated at the cap level. See www.nicta.com.au/pub?doc=7371 for more details, page 35 ("Author
438.
▲
by
cmrx64
10y ago
The "real" specification (if it can be said to exist) is the abstract spec, in Isabelle/HOL.
439.
▲
by
cmrx64
10y ago
Not really true. See https://www.nicta.com.au/publications/research-publications/... for how the compiler and its internal semantics are completely removed from the chain for l4v.
440.
▲
by
cmrx64
10y ago
Yes. See the manual or the tutorials.
441.
▲
by
cmrx64
10y ago
It's a simplified model, but it's well validated. Without connecting the proofs to a formally verified chip, it's about the best you can do.
442.
▲
by
cmrx64
10y ago
If this interests you, check out https://intelligence.org/rationality-ai-zombies/ .
443.
▲
by
cmrx64
10y ago
Interesting habit! I think I'll try this...
444.
▲
by
cmrx64
10y ago
I got the awesome Europa poster hanging in my room. Absolutely love these!
445.
▲
by
cmrx64
10y ago
The technology exists: trusted timestamping and commitment schemes are well-understood. But does it matter in today's adversarial patent environment? You still need to actually appeal the thing, which takes time and lawyers.
446.
▲
by
cmrx64
10y ago
Note: nitpicking follows :) RAM machines are an abstraction, there's no such thing as constant-time access to a random address in any physical store. At best you're looking at O(n^0.5) where n is the number of bits in the store. S
447.
▲
by
cmrx64
10y ago
It's neat to see a "modern" web page and extensive documentation for such an incredibly old piece of software. While hacking on some old computers (one of my hobbies) I came across picolisp but never thought to look for it on
448.
▲
by
cmrx64
10y ago
IME, important papers are sometimes re-typeset using modern tooling, yielding more or less OK documents. In the worst case this is done with shoddy OCR that completely breaks the formula. Additionally, "digitizing" in this context
449.
▲
by
cmrx64
10y ago
Thanks for the clarification. I was rather confused with the subject matter of this handbook without that knowledge. I guess I shouldn't have glossed over the introduction and jumped to what looked meaty.
450.
▲
by
cmrx64
10y ago
Excellent introduction! That implementations sometimes don't implement the full range of priorities has bit me in the past with really hard to debug issues. Not knowing much about FreeRTOS, I look forward to the next part in the series
More ›