Java developers and rails
Rails has been getting a lot of buzz lately, and quite a few people have been joining us on irc as a result. However I’ve noticed an interesting tendency among Java bloggers when they talk about rails.
They seem determined to look for any fault, any crack in what’s presented and seize it (often violently) as proof that rails isn’t a silver bullet that solves all problems. Well, of course it isn’t a silver bullet, nothing is. Fred Brooks prooved that a long time ago. Rails isn’t a silver bullet, but neither is your favourite java framework.
Fundamentally it’s all a matter of choosing the technology that best suits your particular requirements. If that’s rails, cool, if it’s Spring and Hibernate, that’s cool too. Most technologies have a place, if it seems like a religious choice to you, perhaps it’s you that has a problem…
Nigel Ramsay February 24th, 2005 @ 09:02 PM
hacqed by chinese haxors
Jason Barker February 25th, 2005 @ 07:46 AM
Rails hurt Java fascists’ ego. They’re trying to point any flaw on Rails as if they’re covering their balls from being kicked.
Dion Almaer February 25th, 2005 @ 05:29 PM
Hi,
Note that all Java developers don’t feel this way. There are many people who have to work in many worlds (e.g. Ruby and Java and …).
http://www.almaer.com/blog/archives/000735.html
Cheers,
Dion
Koz February 25th, 2005 @ 07:51 PM
Hey Dion,
I realise that not all Java developers feel that way, after all I’m a Java developer. That’s what concerns me so much! ;)
George Moschovitis July 30th, 2005 @ 05:38 PM
Too much convention is not always good. There are alternative Ruby Web Frameworks that may be better suited for your project. For example have a look at the Nitro Web Engine: http://www.nitrohq.com