Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sounds like the trend is to follow Java (to certain extend, if you ignore the debacle of the old J2EE, Struts, and Tapestry).

ORM? Hibernate or JPA2 can be run anywhere: inside or outside container (i.e.: desktop app, web-app, or simply daemon/service)

DI? Spring or CDI

Unit-test? JUnit or TestNG or others

Mocking? EasyMock, Mockito

Message Queue? Pick one out there

Templating? JSP, JSF(ish), Velocity, FreeMarker.

RESTful? Restlet, Jersey

Everybody plays well with one and the other.



Not exactly. The current trend is towards the JVM, but not Java. I wrote about this last week: http://www.smashcompany.com/technology/the-jvm-is-part-of-a-...

Even the cutting edge of Ruby is now on the JVM, as Rubyists see a need for threads and find jRuby the most convenient way to move forward: http://tonyarcieri.com/2012-the-year-rubyists-learned-to-sto...

Rails took off in 2004 as a rebellion against the overly-heavy Java frameworks like Struts. But now what good ideas Rails offered have been incorporated into languages that run on the JVM, and a lot of innovation, in particular with concurrency, is happening on the JVM, and some of those things are areas where Ruby (other than JRuby) is weak.


I see 2 trends here:

Trend #1: modular components

Trend #2: platform (performance optimization as well)

What you described falls into #2 while what I refer to falls into #1.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: