|
|
|
|
|
|
|
|
|
|
|
|
|
Richard Chesterwood wrote:
Runrioter Wung wrote:Before I mainly used Hibernate in my project. I know that now Hibernate will become an implement to JPA. I need a book to refer to for studying. So I wonder which one is better.Give me reasons.Thank you.
Hi,
If you know Hibernate already and you've used it extensively, it's possible that you don't need much to switch to JPA. You could certainly get by skimming through a book - even the knowledge that Session becomes EntityManager, and SessionFactory becomes EntityManagerFactory will get you a lot of the way there! Especially if you've been using the annotations for your hibernate mapping - for many years now the Hibernate Annotations have actually been the JPA annotations.
So it's quite possible you don't need a book or a course.....
Richard
Mike Cantelon wrote:
Runrioter Wung wrote:Node is very, very hot, and I just coded in javascript for the front-end before.I wonder when I should choose JS for backend not .NET or JavaEE(I am a J2ee programmer). Which type of application is the one that Node is designed for?Asyncronous and evented nature of Node is very cool,but sometimes sequential programming is a must.How can I implement it by JS.I don't know that if all I ask is in the book named NODE.JS IN ACTION.
Hi Runrioter,
Node.js is great for applications that require high concurrency and minimal CPU/memory usage. So things that should feel "real-time" like online games, chat, and web applications. For a balanced look at what use-cases Node.js is most suitable for, I recommend Chris Richardson's talk "Node.JS: The Good Parts? A Skeptic's View" (https://www.youtube.com/watch?v=CN0jTnSROsk).
If you need part of your application to be sequential, you can a technique called "flow control". Flow control makes asynchronous logic behave in a synchronous fashion. You can either implement flow control yourself in your application or, much easier, simply use flow control modules. One such flow control module is async (https://github.com/caolan/async).
Cheers,
Mike
Chris Devine wrote:Clojure views data as code and code as data.
Rick Copeland wrote:I think that you'd get the most out of it if you already had a basic knowledge of Python and MongoDB (completing the online tutorials would be more than enough). If you have basic familiarity with Python, you should be fine with the examples in the book. Likewise with Javascript (I'm not much of a Javascript programmer myself, but it's impossible to say much about MongoDB without mentioning Javascript, since it's the embedded scripting language).
Eric Elliott wrote:Both. The first half of the book is packed with modern JavaScript techniques and style guide. The second half of the book walks you through the process of building an application using Node / Express on the back end, and Backbone / jQuery on the front end. More importantly, it teaches you the principles of how to organize and architect JavaScript applications in general, so you can apply that knowledge no matter what libraries or tools you decide to use.
Saif Asif wrote:oh thats great ! What exactly was the issue ?
