3 ms·

If I could only get my priorities straight and stop building the distributed system (I'm close, I swear), I'm building a digital version where people can build

• gentleman11 4y ago
  Interesting concept. I found the page to be a little confusing. You mean you made a language and db to program board game rules? What does the language and db offer that is uniquely helpful for those tasks? Is the db relational?
  • mathgladiator 4y ago
    The language operates on a document model, so the memory model is a document. A key language aspect is await/async semantics for asking users questions like "which piece would you like to play". While using async is not unique, the document memory model is transactional such that the async messages can be rewound. This allows a single incoming message to translate into exactly one data differential which means now the entire experience can be done in spite of machine failure. When I was writing games with JavaScript await/async, it was a giant PITA. First, either the transactional boundary was too large and I had to replay an entire round while testing, or I had a lot of bugs. And bugs were exceptionally common which require building a lot of framework. The database is basically how to productively work within the document, so the primary collection is a table which has basic integrated SQL. I haven't had a need for joins yet, but I plan on them in the future.
    • la64710 4y ago
      Good but the pictures on your website are not attractive specially if you are trying to promote.
      • mathgladiator 4y ago
        Oh, I know. Let's just say that glad I'm basically retired.