I just ordered direct from O'Reilly (eBook) and, before ordered, located a coupon code that worked for me (on August 31, 2011): 4cast -- it gave me a 50% discount on the eBook ($13.99) and supposedly gives 50% off on the printed version.
The books looks to be useful for people who want to build/understand an MVC library from the ground-up with jQuery as a base. There are also chapters about the various ready-built solutions.
I bought the Early Release of this book a couple months ago. The book does a good job of introducing MVC concepts and how they can and should be implemented in a JavaScript web app. Even if you have a background in RoR, Django, CakePHP, etc., the best practices for implementing the MVC concepts client side should prove helpful.
The most worthwhile part of the book - for me - was maccman's coverage of three popular JavaScript MVC frameworks: Backbone, Spine, and JavascriptMVC. The coverage included the basics of how each framework worked, as well as sample apps for each. Other gems included dependency management options (module loaders) and testing client side apps.
My only complaint - and one that maccman can't be faulted for - is the book covers a topic that's rapidly changing. There's few de facto client-side frameworks for MVC or dependency management or maybe even testing. Personally, I think that makes this more exciting, and the book does cover the current state well.
To be fair, this book is about libraries that are strictly MVC implemented in JavaScript, and no more. At the time Alex was writing the book, SproutCore 1.4 was the current version, and is obviously a "full-stack" framework, including a UI library.
SproutCore 2.0 alpha was released on May 25th of this year, so Alex didn't have time to cover it. My hope is that a second edition would hopefully at least mention it, now that it is much more competitive with things like Backbone and Knockout, et al. :)
Appeared exactly when I needed it. I'm currently exploring the JS web app world, and I am in need of some guidance. Sometimes I struggle because my flow currently consists of taking apart other JS apps, instead of having a solid foundation and implementing my own solutions.
There are some things that just aren't intuitive, when you're reading other people's code. I hope this book either enables me to write code from scratch or significantly speeds up my "decompiling" of other people's code.
Congrats on the launch! Must've been quite a ride, since from what I read, you're traveling the world and surfing. Nicely done.
I'm with you. After 10-odd years of getting by just from reading documentation, blogs and stackoverflow (on lamp+js), I recently rediscovered the joy of good quality technical books. There's nothing like taking a nice, structured tour from the 101 all the way to the more advanced topics, is there?
Since you're one of the few published experts on this specific, evolving area :), what are your thoughts on the tradeoffs between the current popular frameworks (i.e. are they so different - yet mature - that each one could conceivably be a best fit for a certain type of applications?). And which framework do you currently prefer?
Jvascript web applications seems too generic as a title. The book covers one way, but there are many different approaches to skin that cat.
The whole javascript apps scene won't stabilize until we get cross-framework ways of building ui components and doing layout. I should be able to take a sproutcore component and use it in an extjs layout, without it becoming a giant hack.
I feel backbone.js is a great base to build a custom mvc framework on top of it. However, for simple projects, I find it to be to heavyweight. I.e. it's really hard to have nested collections (You have to rebind all events). Views could give you a better hand for 90% of scenarios.. These are only 2 examples, but this is why I say it's more of a meta-framework. (I use backbone and patch it with lots of function, event binding, etc. and only then I can use it in my code).
So, I think there's still a place for a smaller, more 90%/10% mvc framework.. and have backbone.js to fallback on in the 10%. In fact, this framework could be build on top of backbone :)
Just ordered the ebook and read through the first chapter. Great work! This is exactly the book I was looking for to take my JS skills to the next level and just the right size. Once a programming book goes beyond 300+ pages, it starts becoming an impediment to progress.
While no doubt it must be no mean task to document fast moving technology (I have just seen the toc), but many of these concepts/libraries are still evolving. Maybe a good record to check back in a few years, what worked, what didnt.
I was just about to order it, but their registration system is messed up...makes me iffy on the idea of buying it now -- if they can't get a simple checkout process right =D
The books looks to be useful for people who want to build/understand an MVC library from the ground-up with jQuery as a base. There are also chapters about the various ready-built solutions.
Nicely done maccman.