3 ms·
I think that is both fair and unfair. Fair because what you say is absolutely true. But unfair because if you stick to the non-bloatware libraries, Java is ve
by justinsb 12y ago
I think that is both fair and unfair. Fair because what you say is absolutely true. But unfair because if you stick to the non-bloatware libraries, Java is very good, very fast and surprisingly productive. For me, that stack is Guava, Jetty, Jersey, Gson, Guice.
I believe though that you can make poor library choices in any language & framework. With languages that have been around for a while, there are a lot of bad libraries...
- nogridbag 12y agoThe last time I tried using a similar stack, I found out the latest Jersey doesn't play nicely with Guice, since jersey uses its own DI library (HK2). Only one user was actively trying to solve the problem and eventually I gave up and looked at alternatives like Ninja framework (which uses Guice, but not jersey).
- justinsb 12y agoAh, true. I still use Jersey 1. Jersey 2 has gone bloatware, sadly. We need a cleaner implementation of JAX-RS (which is really what we want, not Jersey per-se); I've worked on Apache Wink a little bit, but really Jersey 1 is good enough & good. I don't know what happened with JAX-RS 2. It feels like the J2EE team got hold of it... (PS Thanks for the Ninja suggestion; I will check it out)
- bkurtz13 12y agoHave you looked at Dropwizard? It uses Jersey under the hood I believe but it streamlines using all of its libraries together.