Rails Has Turned into Java

Re:Rails Has Turned into Java by hendershot on Wednesday February 20, 2013 @04:30PM (#5253493)

+1 on keeping things simple and not using a "F"ramework for every concern from the very beginning.

>in Java you have to make those architecture choices day 1.

That's just not true. Very easy and advantageous to start out with say a simple container-less app with in-memory/flat file persistence and build up as you need. It's no different in Java and much more the norm in other JVM languages like Scala/Clojure.

[ Parent | on HN ]

Re:Rails Has Turned into Java by danielsju6 on Thursday February 21, 2013 @01:29PM (#5259102)

Thanks.

Perhaps the Java bit isn't true... or isn't true anymore; I haven't done much serious development in Java since I started doing Rails consulting in college. I remember it being XML hell where you needed to plan ahead a lot more in terms of choices, but that said I've probably become a much better developer too.

[ Parent | on HN ]