YogurtFiend

4 ms·

1. 1.▲
   by YogurtFiend 5y ago

   While this isn't true with Go's GC, a GC that's stop-the-world can avoid these cache coherency issues altogether. If you pause every thread before marking and sweeping, then you won't run into problems--only the GC is ru
2. 2.▲
   by YogurtFiend 5y ago

   I don't know why you're being downvoted. Memory reclamation is hard in the face of parallelism. It's much easier to design lock-free algorithms in languages with a garbage collector, because memory reclamation issues are take
3. 3.▲
   by YogurtFiend 5y ago

   I agree 100% with the need for the threat model. I think the current system is, at-best, a system with a tamper-evident audit log. Which, could still be interesting, but the authors' use of ill-defined terms makes it easy for people to
4. 4.▲
   by YogurtFiend 5y ago

   I'm not sure that this is a _useful_ tool. Let's talk about the threat model or the attacks that this defends against. If a Client is malicious, they might try to manipulate the data in the database in an untoward way. In a "