2 ms·
+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.
by hendershot 14y ago
+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.
- danielsju6 14y agoThanks. 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.