Right. If you want to talk about your language, there are two effective ways: 1. Talk about it in isolation: we enjoy Haskell, here's where we think it should

Right. If you want to talk about your language, there are two effective ways: 1. Talk about it in isolation: we enjoy Haskell, here's where we think it should go. 2. Place it in the context of the wider software ecosystem, as in these are the pros and cons, barriers to adoption etc. What isn't effective is doing #2 while not trying to really engage with reality. If you just assume, contrary to evidence, that Haskell is the right way and the reason it's not adopted more is that everyone insists on doing things the wrong way, you will not convince anyone who doesn't believe this fairy tale already, and worse, you'll ensure you won't help yourself, because you focus on the issues you wish you had rather than the issues you actually have. Self-reflection is supposed to help you, and it only helps if it's a long hard look in the mirror. The approach of, "things aren't going the way we hoped but our assumptions could not possibly be wrong so we'll just examine everyone else's" is not generally useful, as it's nothing but a waste of time: you know you'll end up exactly where you started.