Every language has a reason behind its creation. Ignore it at your own peril. 

>> import this

Ruby vs Python

>> The Zen of Python, by Tim Peters

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

Python

1. There should be one way of doing things
    
2. It may not be obvious unless you are Guido Van Rossum

Ruby

1. There should be many ways, do not limit creativity.
    
2. Principle of least suprise, you should n't be shocked beyond your eyeballs

Before Python..... after Python

Ruby vs Javascript

Javascript

• Created in 10 days
• Syntax had to be similar to Java
• Meant to be a 'Glue' language

Ruby

• Work started Feb 24th 1993
• Alpha release December 1994
• Used ideas from Perl, Python, C and C++ and took only the best features from each language
• Anything language

Javascript

• No guiding philosophy
• Design issues that are still unchanged to date
• Multitude of web frameworks

Ruby

• Programmer productivity
• Design involved with new changes
• Fewer web frameworks

Before Javascript...after Javascript

Before Ruby...,after Ruby

Ruby's guiding philosophy is fun and programmer productivity

END