engendering confusion

[Raoul Duke]

asynchronicity is kind of evil and incompatible with human thinking, at least if we dont want bugs, at least with our current programming tools.

order of operations matters a lot when it comes to state. 

it is far too difficult to find out what-all other code or events might cause changes to the state we have currently in mind. 

[Paul Tarvydas]

--
You received this message because you are subscribed to the Google Groups "PiLuD" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pilud+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pilud/CAJ7XQb5ngWz8LnB_yLeTCjuhQLiydwNFJDttrLJc9XU2eHfQdA%40mail.gmail.com.

[Raoul Duke]

tl;dr per chance the old fairy tale moral:

hardware is hard to change so good waterfall and good specs and good abstractions (both logical & physical) are valued, required in order to succeed

whereas

software is "easy" to change, so way less incentive to not do it wrong. it feels successful in the short term (ship it!!!), but bites us on the ass all too soon. 

[David Barbour]

Asynchronous behavior conflicts with imperative expression and reasoning, at least. Other paradigms can be much more effective.