[mindcrime]

COBOL on COGS? http://www.coboloncogs.org/HOME.HTM

All joking aside, nobody can really tell you what tech to use. Everybody is just going to reply with their personal favorite, if they reply at all. At the end of the day, you just kinda have to pick something and give it a try.

My vote would be Groovy and Grails, with whatever cool javascript thing on the front-end that you might want to play with, maybe Angular?

But some other "trendy" things that are popular these days include node.js, Meteor, Scala/Play, Clojure and Go. Giving any of those a shot would probably be a good use of your time.

[_em_]

finally someone replied. thanks for your input. I do want to use Angular.js but i am not sure if it is compatible with vaadin or not.

Btw, why Groovy on Grails ? Any specific reason ? I want to learn something which can land me a better job (if i want to cash that skill). So is GoG more popular or RoR ?

[mindcrime]

Btw, why Groovy on Grails ? Any specific reason ?

No, that was me doing what I said everybody would do - recommending my personal pet favorite. :-) I just happen to really like Grails as a framework for developing web-apps and Groovy as a language. The combo hits a "sweet spot" for me in terms of productivity and ease of use, and leverages a lot of pre-existing knowledge of the Java / JVM ecosystem that I already had.

From a pure "market demand" standpoint, my guess is that RoR or even Node is going to be more valuable than Grails, but I haven't empirically validated that - it's just a hunch. In my case, I'm using Grails in the context of a startup I founded, so it doesn't matter to me what the market is screaming for - it just matters what I can use to Get Shit Done. :-)

[vorg]

The comment you replied to actually said "Groovy and Grails" which is correct because Groovy was originally intended by its creator to be a standalone product with applications using it to be separate products, as with other languages. The phrase "Groovy on Grails" was promoted afterwards by some Grails developers who wanted their product's name to sound like "Ruby on Rails", regarding Grails as the only viable use case for Groovy of any adoption potential.