2 ms·
I think another question is how much you want done on the server (HTML rendering?) and how much on the client. It seems like we're definitely moving towards hav
by pron 13y ago
I think another question is how much you want done on the server (HTML rendering?) and how much on the client. It seems like we're definitely moving towards having the client handle all the UI. I understand this may not be appealing, especially as client side frameworks have even a shorter lifespan than server-side frameworks, but that seems to be the direction. If that's acceptable, for the backend I'd choose Java and Dropwizard (or Jersey+Jetty instead of Dropwizard). Spring Boot also seems nice. I discuss the state of modern Java web development in a non-comprehensive recent blog post[1]. For a more complete discussion of JVM web frameworks, you can take a look at this[2] and this[3].
[1]: http://blog.paralleluniverse.co/2014/05/15/modern-java-pt3/ http://blog.paralleluniverse.co/2014/05/15/modern-java-pt3/
[2]: http://zeroturnaround.com/rebellabs/the-curious-coders-java-web-frameworks-comparison-spring-mvc-grails-vaadin-gwt-wicket-play-struts-and-jsf/ http://zeroturnaround.com/rebellabs/the-curious-coders-java-...
[3]: https://www.youtube.com/watch?v=ygW8fJVlDxQ https://www.youtube.com/watch?v=ygW8fJVlDxQ