3 ms·
I'll pick Java, SpringMVC, Maven, JUnit+DBUnit, and FlyWay (DB migration) and any appserver (jetty, tomcat, TomEE, glassfish) thrown at me except from the BigCo
by edwinnathaniel 11y ago
I'll pick Java, SpringMVC, Maven, JUnit+DBUnit, and FlyWay (DB migration) and any appserver (jetty, tomcat, TomEE, glassfish) thrown at me except from the BigCos (WebLogic, WebSphere).
Those tools are pretty close to what Rails give you (notice the View/UI is open for anything... Rails View is slightly nicer as it has better templating capabilities but ... not a deal breaker for me).
It's not sexy, it gets the job done, and I know it'll run for at least 5-7 years with minimum hassle.
Plus it's easy to be productive on Java project...
- nemild 11y agoEven as someone who uses the newer languages/frameworks, I wish I could upvote this statement multiple times: "It's not sexy, it gets the job done, and I know it'll run for at least 5-7 years with minimum hassle."
- jazzyk 11y agoUpvoted. I am tired of getting the "uncool old fart" looks every time I propose similar stack. You CAN do cool stuff with established tech plus have a peace of mind that you will not run into any "surprises".
- criddell 11y agoIt makes total sense to mitigate risk on a commercial project by going with established (well supported, well understood) technology. No argument. But for a personal toy project where you want to be surprised, would you choose something like Ruby on Rails?
- agentgt 11y agoYeah I got trashed karma wise on a previous comment explaining how I had to port some Ruby apps to Java. I don't even care that much about either technology but just mentioning that I had to port something to Java earned me -4.... seriously.