@jdegoes I disagree. Types are not (only) about the structure of data. It's an abstraction mechanism for both code and data, or, as John Reynolds famously put it, types are a syntactic discipline to enforce levels of abstraction. Also, types are a part of the code.
@DrLutzBoehm@NetzwerkW@BMBF_Bund Die Ursache war lediglich ein kleiner Bug in unserer Software. Leider nicht so aufregend wie es von Herrn Böhm gemutmaßt wird.
@john_chandler These terms are all somewhat fuzzy. Also, "dynamic typing" is, arguably, not even "typing" because all it does is to equip values with one of finitely many different tags and check for tag equality. That's very different from an unbounded universe of static types.
@culturaltutor But words also result from choices. I think the difference is that, in general, actions have more consequences than words and are hence chosen more carefully.
@georgemporter Agreed. The review process has become too heavyweight in general. A million deadlines. Multiple rounds. Artefacts and supplemental material. Author responses. Review and discussion summaries. Lists with mandatory changes. And so forth. It's over-engineered.
@prdoyle To the contrary, can we just start using "+" for the operation of any monad? That way, we can reuse more code. For instance, you can generically combine a list of things. I think you really mean "let's stop using implicit coercions", to which I agree.