Recently in a conversation with a Ruby dev. I was trying to make an analogy about the differences between Ruby and Java. For some reason I used cars. It went something like this.
Going with Java is like driving a Ford Crown Victoria. The Vic. might not be much fun, but it is reliable, easy to find parts for, and boy, you sure can fit lots of stuff in the trunk. Going with Ruby is like driving a little roadster. It is fast, and you will have lots of fun with it until you try towing your boat. Oh, and by the way, finding a mechanic for that exotic Japaneese machine might be tough.
The main point of the analogy is that from a developer perspective programming with Ruby is often far more attractive than programming in Java. But it makes some other points as well: Java is ubiquitous, it has a library for everything and it is embraced by enterprise. It also highlights how powerful Ruby is, and how much smaller the developer base is. Unfortunately depicting Ruby as a sports car makes it sound impractical. It really isn't. Oh, and if you really know what you are doing you'll have no trouble towing that boat. Stupid analogies.
Recently in a conversation with a Ruby dev. I was trying to make an analogy about the differences between Ruby and Java. For some reason I used cars. It went something like this. 
1 comment:
Great blog, thanks.
I'm a django coder myself and I do feel like I'm in a sports car. Lucky for me, python does have a library for anything.
I heard somewhere that "Java is 21st century Cobol" and when I try to fit a car to Cobol an old crown victoria does come to mind :-)
Post a Comment