I agree. Now, I'm a bit of a Smalltalk die-hard, and I do think live coding is better (in some vague, hand-wavey sense that I won't attempt to expand upon here)

I agree. Now, I'm a bit of a Smalltalk die-hard, and I do think live coding is better (in some vague, hand-wavey sense that I won't attempt to expand upon here), but I agree that a million posts saying as much won't change anything. Programming language adoption is as much about the transmission of culture as anything else, it's hard to do that with Smalltalk at a distance. One way in which many people here will regularly encounter "live" coding (i.e. with very short cycle times) is at the bash prompt - grep, awk, et al - (and my opinion of bash... is another thing I won't expand upon), but the ridiculous archaic "let's pretend it's a teletype" metaphor has an interesting thing going for it - as you work you leave behind a transcript of what you did, and what the result was. You can copy and paste that into an email, send it to someone and ask for help - maybe a mailing list, maybe a newsgroup. You can write it up as a blog post and say, "hey everyone - look at the clever way I did this". You can illustrate your tools and your working practices easily, and transmit your programming culture far and wide.