Yes, it's worth learning. 3 good reasons why: 1. It's ambitious. Meteor is not yet another nodeJS web-framework or client side JS framework. It also doesn't

Yes, it's worth learning. 3 good reasons why: 1. It's ambitious. Meteor is not yet another nodeJS web-framework or client side JS framework. It also doesn't stop at combining the both (with a beautiful DDP to share data between C/S). Meteor' s architecture will make it possible to use it's components for all sorts of applications (other then the obvious web-apps). 2. It's as easy or as complex as you want it to be. You can write a meteor app in 4 files or in a complex packaged structure. No need to overcomplexify, if you dont't want to. But you cán write large, complex, stable and maintainable code. 3. It embraces the eco-system. You can rely on all of the NPM packages out there for your serverside logic and use all of the available frontend UI libraries and scripts. It will also enable writing complete reusable components in 1 package: servers-side logic, data-model, client-side logic, UI, ... all in one. Biggest upcoming updates: * Meteor UI. Better approach then any other UI framework out there (including Facebook's react or FTLab's fruitmachine) * Galaxy. Deploy and scale your app on your own infrastructure or in the cloud by pressing a few buttons. To counter a few of the cons in this thread: * It's not reached 1.0 and it is therefor not production ready. I'd suggest writing your new applications in meteor anyway. Meteor matures quicker then any other framework out there. Is is well funded and here to stay. * It is not scalable. Maybe not easy right now to make it scalable. But it certainly will be soon, when using mongodb oplog and galaxy will make it really easy to scale your service. I run an agency in Belgium (redandivory.com) and we switched completely to meteor for all of our new projects. I think it's the framework of the near future.