Ask HN: Should I learn and use ROR or stick with what I'm comfortable with?
I've been working for a software company that uses Java Struts for building web applications and I've become very, very good at it. It's boring, verbose but the runtime is efficient and I can crank it out.
I started looking at ROR tutorials, but have been a little bit turned off by the hand-waving of scaffolding and usage of GEMs (granted, I bailed mid-way through even the first tutorial).
What are your thoughts on building a Java Web Application (using Struts, likely - other suggestions welcomed), versus building a Ruby on Rails (etc.)
9 comments
[ 3.3 ms ] story [ 34.1 ms ] threadMaking the big jump to Rails is the best way - plenty of people do it. There's no point learning Grails programming if youre not going to stick with it.
If it's the former I'd check out other Rails-like frameworks for Java. If it's the latter, then make the change to RoR.
I think you should learn RoR (or Django) and then decide for yourself. Keep in mind that we are in the middle of another 'change' in web development which lead us to two aspects:
1) Traditional web development: If you are building experiments or software that can change quickly due to some sort of pivoting, you should avoid Java at all costs. It takes way too much time to test/change things using Struts (even 2) or spring.
2) Using AngularJs, Ember et al: Java does great, just use Jersey and you will be fine. But, why not use Go? It is faster than using netty, it is something new (we all like shiny things).
That's my two cents, have a great day!!!