DEV Community

Discussion on: Why should I not choose Ruby on Rails ?

Collapse
 
hrishio profile image
Hrishi Mittal

I’ve been working on a system built with Java Spring for the past 2 years

Stick to what you know. Use Java Spring.

I say this as someone who does not like to touch Java and uses Rails for a living.

The no.1 thing that will kill your project is not language/framework slowness, but messing around with tools instead of shipping software.

Collapse
 
martyonthefly profile image
Sylvain Marty

Hi Hrishi,

This is a side project that I work on my free time. So, I have the time to choose, try and learn the most adequate language for my project. :)

But yeah, you are right, if a project need to be shipped in a short time, I would rather use Java Spring to avoid messing around with tools !

Thanks for your reply !

Collapse
 
hrishio profile image
Hrishi Mittal

Ah I see. If you want to explore, then go wild! I'd say try Node as well as Rails.

Collapse
 
bgadrian profile image
Adrian B.G.

Basically you recommend the "when you have a hammer everything looks like a nail". Not a good approach for professionals.

Anyway Java can do web services, but shouldn't.

Collapse
 
lluismf profile image
Lluís Josep Martínez • Edited

Or maybe because both Spring and RoR are swiss knifes, not hammers. Both perfectly valid for the task.