jonnadal

41 ms·

1. 1.▲
   by jonnadal 5y ago

   I can also add a supplementary chapter explaining how it works under the hood. You’re correct about `ActorModel`: its a reusable model of actor system semantics parameterized by an `Actor` implementation. Its “dual” is the `spawn` function
2. 2.▲
   by jonnadal 5y ago

   Thanks for these insights! I think retaining the actor example while postponing the content on model checking and linearizability might be the way to go. More details on related Rust concepts could be helpful too, given that this may be the
3. 3.▲
   by jonnadal 5y ago

   I’m thrilled to hear that as I’m a big fan of your work! Thank you for the suggestion as well. Do you have thoughts on specific places where I should either split a chapter and/or associated project to make the ramp up more incremental
4. 4.▲
   by jonnadal 5y ago

   Yep, Kyle has done an amazing job demonstrating how pervasive bugs are within real world distributed systems.
5. 5.▲
   by jonnadal 5y ago

   Regarding the last point — correct, Stateright aims to verify both. It’s important to clarify that this doesn’t provide a proof of correctness, but it can dramatically improve confidence in both the design and implementation compared with f
6. 6.▲
   by jonnadal 5y ago

   Thank you!
7. 7.▲
   by jonnadal 5y ago

   Author here. I'm also working on a related book covering distributed algorithms: https://www.stateright.rs/ It includes a comparison w/ TLA+/TLC for those familiar with those technologies.