We have been doing an app rewrite at work to do a rich HTML/JS client, reducing the Java back-end to just REST services. As far as I'm concerned, there is still too much "Enterprise!" in the back end, but we have a legacy codebase to try to recycle.
I'm not ready to go pure Node.js, but I wouldn't mind coding the backend on Nashorn, skip the Object-{Relational/View}-Mapping make-work, and only drop into legacy Java as a last resort. However, I'm the only pro-dynamic language (as well as functional programming) fan at work, so that's a non-starter.
We have been doing an app rewrite at work to do a rich HTML/JS client, reducing the Java back-end to just REST services. As far as I'm concerned, there is still too much "Enterprise!" in the back end, but we have a legacy codebase to try to recycle.
I'm not ready to go pure Node.js, but I wouldn't mind coding the backend on Nashorn, skip the Object-{Relational/View}-Mapping make-work, and only drop into legacy Java as a last resort. However, I'm the only pro-dynamic language (as well as functional programming) fan at work, so that's a non-starter.