To me as a language pluralist, none of this particularly sounds like anything new. My initial programming training was FORTRAN (in 2006!) and I then "taught my

To me as a language pluralist, none of this particularly sounds like anything new. My initial programming training was FORTRAN (in 2006!) and I then "taught myself" C++ (I didn't know anything about C++ by the end of it), wrote a ruby-on-rails "site" for a friend, and then got a job writing C# and MS SQL, where I wound up actually writing a lot of Actionscript 2. This was all while I was still learning about new programming concepts, e.g. I was using lambdas/anonymous functions in Actionscript before I knew that there was anything special or difficult about having inline functions as objects. When I finally tried to write a non-trivial program in C, I started to understand the difficulties and trade offs of all the complex, mutable collection types I had been using in higher level languages. and so on. I say all this, because when you come into programming on that journey (now rounded off with 3 years of Python-and-C/C++-extensions) you don't have time to develop a religion (that lasts any length of time). It becomes apparent that lots of different technologies work in different circumstances, and that each of them shares a lot of ideas, and have some unique features (good or bad). That said I do have a preference, indeed I posted a language rant last year[1]. I still think homoiconicity is wicked, even if not always useful - and I've not yet ever written something that anyone uses in lisp. [1] http://joe-jordan.co.uk/blog/2012/10/one-syntax-to-rule-them-all/‎ http://joe-jordan.co.uk/blog/2012/10/one-syntax-to-rule-them...