Additionally, you CAN market to the n00bs, the Functional crowd, and the traditional OOP developers simultaneously.
Instead, it helps to be pragmatic, and explain what’s really happening: There is enough business demand for traditional OOP developers to get the features they desperately need in a standardized fashion, whether syntactic sugar or true implementation. This means asynchronous modules and OOP syntax. Harmony, of which much already supported, and ECMA 6’s better class support, shows that the OOP developers have made their case, and that the Functional crowd has made theirs as well: both can co-exist.
If you teach the architected future, you can easily dissect various strategies employed currently to use that future today.
I wish I had done that with ActionScript 1.0. I learned OOP after the fact and was basically taught for reasons both valid and invalid that dynamic Functional languages don’t really help you build software and I think that was a shame. I hope to remedy that in a future set of videos to help prevent developers going through what I went through.