Monday, May 26, 2008

Reason 2: Ruby is better than Java

Profiling.

With Java you have to use a 3rd party framework to get any useful profiling information. There are some good ones out there, but regardless, this is again a big production. Without a profiling tool, this information is next to impossible to gather.

With Ruby, you just run your program with command line "-r profile" and you get a comprehensive dump of where all the time is being spent.

Score 1 for Ruby.

No comments: