Its interesting because the reason I think "JAVASCRIPT EVERYWHERE" is valid is because I think "EVERYTHING EVERYWHERE" is valid. Don't get me wrong, some langua

Its interesting because the reason I think "JAVASCRIPT EVERYWHERE" is valid is because I think "EVERYTHING EVERYWHERE" is valid. Don't get me wrong, some languages are incredibly domain specific and don't make a tremendous amount of sense at all parts of the stack (and some parts of the stack should have domain specific languages), but JavaScript is a general purpose language, that has some interesting things to offer different domains (whether it be server development, app development, etc), but most importantly... SO DO MOST OTHER LANGUAGES! I would love a world where I could choose from most general purpose languages for most tasks. I haven't found many reasons other than "why?" for being against JavaScript being everywhere. I know that if I was a Ruby guy I'd certainly like it if I could use Ruby in as much of the stack as possible, and I think that's totally reasonable. For example, I applaud transpile-to-JS languages so that you can use a language of your choice for the browser (vs thinking "why do we need Clojure everywhere!").