Developers View Ruby vs. J2EE
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Developers View Ruby vs. J2EE

on

  • 3,069 views

Compared to Java, Ruby is a much less verbose, much more flexible language. Its arrays and hashes provide much of the same functionality split into multiple different classes in Java (implementations ...

Compared to Java, Ruby is a much less verbose, much more flexible language. Its arrays and hashes provide much of the same functionality split into multiple different classes in Java (implementations stacks, queues, lists, maps etc.) with a more comprehensive API. The provided each, map and inject methods allow the code to be written in much more compact and readable way compared to the traditional way of wrapping the code inside loops (though the functionality is overall the same) through passing in Ruby code blocks. Strings in Ruby are also mutable and provide a very comprehensive API.

Statistics

Views

Total Views
3,069
Views on SlideShare
3,069
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Developers View Ruby vs. J2EE Presentation Transcript

  • 1. Developer’s view: Ruby vs. J2EE http://extremia.fi/
  • 2. Advantages of Ruby• Compared to Java, Ruby is a much more flexible language• Map and inject methods allow the code to be written in much more compact and readable way compared to the traditional way of wrapping the code inside loops through passing in Ruby code blocks• Strings in Ruby are mutable and provide a very comprehensive API http://extremia.fi/
  • 3. Advantages of Ruby• More compact syntax and some more flexible classes allow many tasks to be performed much more quickly in Ruby than in Java• Having to deal with less boilerplate code also leads to a much smaller, more maintainable codebase• A smaller, better maintained codebase leads to a more complete test coverage and less wasted time in refactoring, all leading to a much more productive and fun software development http://extremia.fi/
  • 4. Ruby on Rails vs. J2EE• The Ruby on Rails is probably the most comparable framework to a usual J2EE stack• Many of the libraries found in J2EE have a counterpart in one form or another in Rails• Ruby counterparts are often less powerful and flexible, but do also require less maintaining and less code from a developer to perform the same task• Rails is profoundly more invested in convention than in configuration http://extremia.fi/
  • 5. Ruby on Rails vs. J2EE• J2EE libraries like Hibernate and Spring are highly customizable and configurable but come with an increased cost in maintainability• Both Spring and Hibernate provide an extremely flexible structure through easily replaceable modules• Hibernate gives an experienced developer much more control on how the application flow will be processed• Spring offers a lot of different modules for complete customization, providing much of common functionalities for a web application http://extremia.fi/
  • 6. Ruby on Rails vs. J2EE• Rails comes with plenty of handy and powerful generators that make it extremely easy to follow the set of conventions• Setting up a project quickly from scratch makes building RESTful applications in MVC architecture with Ruby on Rails is orders of magnitude faster than with its J2EE counterparts http://extremia.fi/