We will be discussing the topics Node.js Alternatives on the JVM and Why you should take a look at Ember.js (again) on Thursday, January 22 at Frankfurt.JS. There are still places available! Take a look now and register at http://bit.ly/1zhw5XV
Node.js Alternatives on the JVM
– Niko Köbler
Both approaches deal with the ability to be able to execute JS code not only asynchronously and in a non-blocking manner, but also in multiple threads and with the ability to communicate between these threads with an event bus or shared state — even in highly distributed systems! Additionally, there are major advantages of using a JVM-based scripting engine when developing for enterprise environments.
Why you should take a look at Ember.js (again)
– Henning Glatter-Götz
Ember.js was out of the gate a bit later than others and was said to have a very steep learning curve. Its data layer was not ready and changed on a daily basis. There were no clear best practices for structuring an application and the documentation needed a lot of attention. Early adopters definitely had to endure a lot of pain if they stuck with Ember.js, especially in the pre 1.0 days.
I will outline the reasons why I chose Ember.js over the competitors and why I think Ember.js deserves another look if you previously concluded that it was not for you. We will look at some Ember apps in the wild to see what we can learn from them and we will do some coding ourselves.