As an aside, Peepcode has a 3 part video tutorial on Backbone.js, which is exceptionally great (more than 3 hours, but it's really condensed and it took me 2 days to completely digest it). Each episode is $12; a little expensive at first sight, but really worths it.
... but there are often many more interesting things out there in the wild than we're necessarily aware of -- for example: Rdio, the new GoogleArtProject.com, and Pitchfork.com. Are you currently working on a fun Backbone app, or have you seen one recently that we might not have heard about?
http://nosweaters.com is beginning to incorporate Backbone into its setup (currently utilized in user /home feed and idea suggestion path), and my personal project site, http://showhopping.com is moving from its spaghetti crufty mess to a completely BB/Require setup.
We're using more and more backbone in https://paydirtapp.com - it's currently an integral part of our time-tracker, with the same code base reused in our Chrome and Firefox extensions. We're also using it to drive d3.
The online version was submitted 10 days ago (by someone else) but it didn't get any attention. So I submitted a link to the epub version. It seems like a very good tutorial and I hope someone finds it useful.
Also, I'm watching a terrific presentation from the book's author right now:
Whilst this works great for apps that are built at a smaller-scale, what happens when your project really starts to grow?
You'll learn how to keep your application logic truly decoupled, build modules that can exist on their own or be dropped into other projects and future-proof your code in case you need to switch to a different DOM library in the future.
Your question strikes me as an odd one. Meteor just came out. I'm not sure that there are any folks who have built any substantial systems using Meteor yet (aside from it's authors) who would be able to give you a firm recommendation.
That said, Meteor and Backbone do different things. Meteor is an attempt to solve (obviate, really) the mismatch between client/server development. To what extent it does this in a reasonable fashion is yet to be fully explored (although it does look awesome!)
Backbone is a client-side JS application toolkit. It's purpose is to bundle up the things that are common to every JS application, and provide a solid API to hook your application code to, and to hook your app to your RESTful server API. That said, Backbone offers more than just a convention for how your JS app talks to your API.
You will note that Backbone is included in the default set of installable Meteor packages.
I'm a newbie, although I feel somewhat informed on these subjects (although not skilled in coding).
Obviously meteor was big news yesterday, but it's quite immature. The YUI Mojito project also recently made news and is more stable/robust. While the tightly integrated approach used in YUI sounds convenient, I get the impression that there isn't much excitement behind YUI -- certainly not like backbone.js, node.js, et al.
I'm in the process of learning Backbone and just read about Meteor, so I might be completely wrong on this. But it seems like Backbone and Meteor are trying to solve different problems, and aren't mutually exclusive. Backbone is server-agnostic, and Meteor is somewhat client-agnostic, so you could use Meteor to do the data synchronization and automatic updating, while structuring your client app using Backbone.
- backbone - jquery - meteor <- the low level of the high level :)
You use meteor as a foundation to build your application as backbone is more or less your application itself. Think "CoreFoundation" vs "AppKit" kind of difference.
I was very impressed with Meteor, but it is very new and isn't really bringing anything of substance to the table yet. Everything (other than client-side database interaction, which I am confused about who would want), that they spotlighted can be duplicated easily with backbone, node, and socket.io...right now. Moreover, backbone, in particular, is clearly a tool, like a screwdriver, that does a few things well and gets out of your way, whereas Meteor, like rails used to be, is more like an electronic lockpick...awesome magic for the limited scope of applicability, but not currently useful for most of the things you want to do in real life.
My team just finished building two new features of our application using Backbone and now we're actually looking into switching to Ember.js to take advantage of the automatic databinding and lack of a need to do manual DOM manipulation.
Can anyone comment on their experience with the two frameworks?
There's always Calibre, but it's really bloated. It's a very powerful and capable ebook management system though, it's just not really Mac-ish.
Adobe has a very good ePub reader, called 'Adobe Digital Editions' that runs on Mac, Windows and (I assume) Linux. It's an Adobe Flash/Air application and is much prettier than Calibre. If you don't mind Flash on your mac (I gave up last year), It's currently the best choice.
If you just want to read, Amazon's free Kindle.app is by far the best Mac reader. Use KindleGen to convert .epub to .mobi (or scroll up, someone's already done this here).
However, be warned that it won't allow you to copy text even from an non-DRMed ebook, which is quite silly and makes it useless for anything that has code samples in it. For reading a book on screen it's pretty good though.