3 ms·
Can anyone provide an intuitive use-case for including stuttering in a model? I get that you can't model what 'eventually' happens: will a purchase flow end in
by mrkeen 2y ago
Can anyone provide an intuitive use-case for including stuttering in a model?
I get that you can't model what 'eventually' happens: will a purchase flow end in a good state? NOT IF THE USER WAITS FOR AN INFINITE AMOUNT OF TIME BEFORE CLICKING THE 'BUY' BUTTON!
So the first thing I always have to do is turn off that nonsense so I can get back to modelling the purchase flow.
Any counter examples?
- hwayne 2y agoThe main reason for stuttering is it makes composing specs a lot easier. Say you have two specs, one which is [](x' = x + 1) and one which is [](y' = y + 1). If you put the two together, you get [](x' = x + 1) && [](y' = y + 1), meaning both are always synchronized. If both also have stutter steps, though, you also get interleaving, where on a step only of the two increments.
- hansvm 2y agoFair locking is a classic example. Stuttering can happen at a hardware level, and you need to create a composite data structure / algorithm which is correct regardless.
- thaumasiotes 2y ago> will a purchase flow end in a good state? NOT IF THE USER WAITS FOR AN INFINITE AMOUNT OF TIME BEFORE CLICKING THE 'BUY' BUTTON! You seem to be presenting this as a ridiculous thing to consider, but it's very common behavior. Visit the site, add something to your cart, close the tab, never come back. What am I missing?
- mrkeen 2y ago> What am I missing? A use-case for the <> "eventually" operator.