Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Łukasz Mikołajczak
2,654 PointsWhat do you think about Meteor.js?
As in question...what do you think about it? Is it worth to learn? Currently I'm working with python/flask but I want to try something new. Is meteor good choice or is it just framework which no one use in real-webapps?
Thanks in advance for your answers!
1 Answer
Chris Shaffer
12,030 PointsAbsolutely.
The myth about Meteor is that it's some magical new framework, when it's actually a compilation of many of the best parts of other frameworks. (They actually say this on their site).
In a way, Meteor is actually a package manager for another package manager, NPM.
I'm in no way dogging Meteor. Actually, it's my favorite way to develop an app right now.
I bring this up because most of the pushback I hear is surrounding, "oh no, not another JS framework ", when the reality is you're probably already using most of the JS that's in Meteor, and not doing it as well.
I think Meteor is a great place to start for those new to NodeJS and stands well as a long term app framework.
I love the MEAN stack for all of the things it makes possible, but I love doing those things in Meteor because of how seamless it is.
A good example is templates. If you've fooled around with Web Components or Polymer, you know templates rock. Meteor builds on the ease of just naming a template and then calling that template, no linking to the file needed.
It's also smart enough to review dependencies for JS calls you've made and simply load things in the correct order. This means no more screwing with, "jquery is undefined" or trying to decide if your script tag should go in the head or at the body bottom.
Try out the tutorial app. Try loading it on two different devices on two different networks (Meteor lets you deploy to your own subdomain in their servers). It will blow your mind when you see the real-time response.