4 ms·

If you or your friend are not comfortable with anything else, stick with plain Java. Check out the Play framework if you really want to prevent boredom because

by roam 17y ago

If you or your friend are not comfortable with anything else, stick with plain Java. Check out the Play framework if you really want to prevent boredom because you've all done it before. Or Groovy. If you don't want to do Java projects in the future, I suggest getting comfortable enough with other languages and frameworks on your own time. For now: what's wrong with "RESTful" URLs? And you do understand you're not required to use 4 different layers in Java either, right?

Tichy 17y ago
Thanks - play looks good, will definitely consider it. I like RESTful URLs, the problem with Django seems to be that it doesn't really cater for them (or at least the routing system does not know about GET, POST, PUT and DELETE, as far as I could see). Java layers: I know, but using Java usually also entails using Spring and Hibernate and "doing things the proper way" :-/ I know I should get comfortable with other frameworks, I just haven't found one I was happy with (tried Rails, and atm doing a small Python project - where I settled for bottle.py, which is great fun, but probably too plain atm.).
- strlen 17y ago
  > Java layers: I know, but using Java usually also entails using Spring and Hibernate and "doing things the proper way" :-/ I highly suggest looking into Guice (why defeat the advantage of Java's static typing by passing strings around through XML documents?) and jDBI (ORMs are evil, jDBI takes a lot of the boiler plate out of writing JDBC calls: http://jdbi.org/ http://jdbi.org/). If you absolutely must use Spring, at least use Spring's JavaConfig (as opposed to XML based configuration) and SimpleJdbcTemplate (another way to avoid the boiler plate of JDBC without going to an ORM). JVM doesn't mean having to use Java (but your partner seems to be dead against Scala, which is his loss). Java, however, doesn't mean having to use Spring and JEE.
- towndrunk 17y ago
  There is absolutely nothing wrong with using just JSP/JSTL and Servlets. With a properly built base servlet as a foundation for your other servlets, things become quite easy and enjoyable in the Java world. You do not have to use Spring and Hibernate to do things proper in Java.
  - kls 17y ago
    I don't even use JSP/JSTL, I do straight HTML, CSS and JavaScript for the front end now and use a CMS for all of my static templating (by-by tiles). The only thing I use Java for now is RESTful services using JAX-RS. I do use JPA for my data access so for the most part, if I am just doing CRUD, I can generate the JPA class and the RESTful service off of that class without "writing" java. It is a far less convoluted stack and is far more efficient at getting work done quickly.

by roam 17y ago

Tichy 17y ago

Thanks - play looks good, will definitely consider it. I like RESTful URLs, the problem with Django seems to be that it doesn't really cater for them (or at least the routing system does not know about GET, POST, PUT and DELETE, as far as I could see). Java layers: I know, but using Java usually also entails using Spring and Hibernate and "doing things the proper way" :-/ I know I should get comfortable with other frameworks, I just haven't found one I was happy with (tried Rails, and atm doing a small Python project - where I settled for bottle.py, which is great fun, but probably too plain atm.).

strlen 17y ago
> Java layers: I know, but using Java usually also entails using Spring and Hibernate and "doing things the proper way" :-/ I highly suggest looking into Guice (why defeat the advantage of Java's static typing by passing strings around through XML documents?) and jDBI (ORMs are evil, jDBI takes a lot of the boiler plate out of writing JDBC calls: http://jdbi.org/ http://jdbi.org/). If you absolutely must use Spring, at least use Spring's JavaConfig (as opposed to XML based configuration) and SimpleJdbcTemplate (another way to avoid the boiler plate of JDBC without going to an ORM). JVM doesn't mean having to use Java (but your partner seems to be dead against Scala, which is his loss). Java, however, doesn't mean having to use Spring and JEE.
towndrunk 17y ago
There is absolutely nothing wrong with using just JSP/JSTL and Servlets. With a properly built base servlet as a foundation for your other servlets, things become quite easy and enjoyable in the Java world. You do not have to use Spring and Hibernate to do things proper in Java.
- kls 17y ago
  I don't even use JSP/JSTL, I do straight HTML, CSS and JavaScript for the front end now and use a CMS for all of my static templating (by-by tiles). The only thing I use Java for now is RESTful services using JAX-RS. I do use JPA for my data access so for the most part, if I am just doing CRUD, I can generate the JPA class and the RESTful service off of that class without "writing" java. It is a far less convoluted stack and is far more efficient at getting work done quickly.