System.out.print(); and System.out.println();
print statements, those evasive semicolons (;) and error messages - oh, the error messages! They never really did help me as much as confuse me every time they popped up on the left side of the computer monitor, especially when a semicolon was misplaced. As you can probably tell, I'm one of the many that have issues working with java and it became something that I thoroughly enjoyed at the beginning to something I silently loathed every time an instructor assigned a programming assignment... until I was introduced to Ruby.
With Ruby, I thought 'there's still hope yet!' after completing several exercises on codecademy. I realized while working with it just how much I really enjoy the simplicity of it and its syntax and how I was able to ease through it compared to java's verbal redundancies. Thank you so much, Yukihiro Matsumoto! You've done many up-and-coming programmers, including me, a great service by providing us with this.
As I am still new to working with Ruby, I can't say 'Oh, Ruby is so much better than Java blah blah blah...' - though, of course I could because I am entitled to my own opinions in this case. However, I don't think it would be right to base it solely on what I've come across briefly versus what I have worked with in Java. So, I went searching through various Ruby versus Java articles and I stumbled upon a blog, Ruby vs Java, written by this guy named Diego. In his blog, he lists out the advantages of working with Ruby and the advantages of Java. I'll jot down a summarized list of the things he wrote below:
- Everything is an Object
- Blocks of Code
- Duck Typing and Syntactic Sugars
- No compilation Required
- Multi-threading and Concurrency
- IDE Support