I don’t like Java Language but I like Java VM, is there some alternative?

Groovy is a fantastic language, but its main audience is Java developers, and with Ruby so much in the headlines at the moment, I guess Sun is quite keen to grab as many as they can…

My £0.02

I don't like Java Language but I like Java VM, is there some alternative?

Groovy is a fantastic language, but its main audience is Java developers, and with Ruby so much in the headlines at the moment, I guess Sun is quite keen to grab as many as they can…

My £0.02

Thanks for your concern for my welfare. I am not alone. I am sick of the last 3 years of the “Ruby Rulez, Java sucks crowd”. Ruby/Rails has always been overhyped by pyschocotic devotees. This is just a little backlash.

Groovy seems to make more sense for the Java space. That’s all.

Ruby on the other hand is a whole separate language with a syntax that keeps me from even considering it. The rudeness of the Ruby community is also terrible and I do not want to support their Java bashing cause.

I love Java. Why should I even care about Ruby when I can continue to use the language and frameworks I love, backed with a Java like JSR scripting language.

“Then if I still had some money, I would donate it charity and leave Ruby out in the cold like the match stick girl.”

Wow! Rick you’re coming across as being really weird, pyschocotic almost. Why the hatred for Ruby? It’s just another language dude! Get counseling or something.

I like groovy as a language and imagine it to be quite helpful in a variety of activities to bring easy scripting to java. A good example is executing an inline groovy script through maven groovy plugin. (I would treat Rhino in a similar way).

It however seems that much of recent popularity of groovy is not because of its initial intentions (grails was nowhere on the radar then) but due to grails (This might be an interesting link : http://www.indeed.com/jobtrends?q=groovy%2C+grails&relative=1 ). Now while grails might be serving its own constituency quite adequately, ruby+rails also happen to serving their base quite well. Rails is a partially disruptive development but it has helped create a large number of ruby developers. If I want something rails like I would much rather go for ror than for grails.

Java and Ruby are distinctly different languages with very different developer productivity and performance profiles Groovy to me occupies the intermediate territory between java and ruby, and given a much wider share (both in terms of momentum and actual projects / developers) of both ruby and rails, I think the software community will be served much better (Ruby not being a JSR notwithstanding), if java and ruby were made more interoperable (calling java routines from ruby methods or calling a ruby library from a J2EE app). That way I would use ruby if I wanted a really concise and powerful metaprogramming language with a framework on steroids, and Java if I wanted the entire industrial strength infrastructure that backs it up. Unless I find a reason to change my mind, I would still use groovy and js (rhino) to script in and around java for specific tooling or custom scripting – not yet to write full blown applications with.

Disclosure: I earn my bread using Java – not with ruby or groovy. – as yet I am playing around with them.

Then I would pick Python via Jython since is it a) more popular b) more mature.

Then I would pick Scala since it provides great langague feature that are not found anywhere else and it augments what Java bring to the table.

Then I would pick PHP since it is a) more popular b) people actually use it.

Then I would pick Ecmacscript 4 via the next Rhino since it is a) more popular b) people actually use it c) it has great langague features in a very commonly used syntax d) looks a lot closer to Java than JavaScript.

Then if I still had some money, I would donate it charity and leave Ruby out in the cold like the match stick girl.

I like groovy as a language and imagine it to be quite helpful in a variety of activities to bring easy scripting to java. A good example is executing an inline groovy script through maven groovy plugin. (I would treat Rhino in a similar way).

It however seems that much of recent popularity of groovy is not because of its initial intentions (grails was nowhere on the radar then) but due to grails (This might be an interesting link : http://www.indeed.com/jobtrends?q=groovy%2C+gra... ). Now while grails might be serving its own constituency quite adequately, ruby+rails also happen to serving their base quite well. Rails is a partially disruptive development but it has helped create a large number of ruby developers. If I want something rails like I would much rather go for ror than for grails.

Java and Ruby are distinctly different languages with very different developer productivity and performance profiles Groovy to me occupies the intermediate territory between java and ruby, and given a much wider share (both in terms of momentum and actual projects / developers) of both ruby and rails, I think the software community will be served much better (Ruby not being a JSR notwithstanding), if java and ruby were made more interoperable (calling java routines from ruby methods or calling a ruby library from a J2EE app). That way I would use ruby if I wanted a really concise and powerful metaprogramming language with a framework on steroids, and Java if I wanted the entire industrial strength infrastructure that backs it up. Unless I find a reason to change my mind, I would still use groovy and js (rhino) to script in and around java for specific tooling or custom scripting – not yet to write full blown applications with.

Disclosure: I earn my bread using Java – not with ruby or groovy. – as yet I am playing around with them.

Then I would pick Python via Jython since is it a) more popular b) more mature.

Then I would pick Scala since it provides great langague feature that are not found anywhere else and it augments what Java bring to the table.

Then I would pick PHP since it is a) more popular b) people actually use it.

Then I would pick Ecmacscript 4 via the next Rhino since it is a) more popular b) people actually use it c) it has great langague features in a very commonly used syntax d) looks a lot closer to Java than JavaScript.

Then if I still had some money, I would donate it charity and leave Ruby out in the cold like the match stick girl.

So “relatively” speaking 31st is pretty impressive