I'm extremely novice to node.js, which for me has been an intimidating framework. But Meteor pulled me in and introduced me to Node (and MongoDB) in a way I felt was less intimidating somehow. In this way, I see Meteor as complementing Node. Though this is just my own personal experience, I'd wager to bet that my experience is not unique.
Arunoda: keep doing what you do... I follow you closely and respect your contribution. Furthermore, I learn so much from you! On Wednesday, August 14, 2013 9:11:41 AM UTC-7, Arunoda Susiripala wrote: > > Hi Issacs, > > A note on meteor. > I've played a bit with meteor and things are not so bad. > > meteor's package system is different from NPM. But it has a reason. Since > those packages need to have content/code related to both client and the > server. > > There is no official NPM like tool/service for meteor. But there is > something called meteorite <https://github.com/oortcloud/meteorite>(cmd > tool) and atmosphere <https://atmosphere.meteor.com/>(app registry) which > hosts community powered packages. It is maintained by the community. It is > quite small but growing. > > If you need to use a npm module with meteor, it is little bit hard. But > there are some good work > arounds.<http://meteorhacks.com/complete-npm-integration-for-meteor.html> > > meteor's packaging system is so powerful and allow maximum power to the > developer. I've changed meteor's realtime > engine<http://meteorhacks.com/introducing-smart-collections.html>but I never > had to fork meteor. > > Meteor is not bad a thing for node or to the community. It is something > different. > > > > On Wed, Aug 14, 2013 at 9:24 PM, Isaac Schlueter <i...@izs.me<javascript:> > > wrote: > >> > But let's be fair here. If "userland" and "fork" are the answer, why are >> > people so mad about meteor? >> > It's also a matter of culture. If the suggestion is to fork, then we >> > shouldn't berate people for doing it afterwards. >> >> Oh, I'm not mad about meteor being a fork. As far as I've seen, >> they've done nothing towards Node that is unsporting or rude. >> >> I have criticisms about how they've gone about building a community, >> of course. That is, in several ways, I think meteor is Doing It >> Wrong, but that doesn't mean that it's bad or anger-inducing, beyond >> the typical "People are wrong on the internet!" reaction. >> Specifically, their module/package system is basically the exact >> opposite of the design decisions in npm, which I believe have been >> essential to Node's ecosystem scaling to the size it is now. >> >> Meteor has (last I checked, anyway) a "single point of curation" model >> for publishing modules, which drastically limits how fast they can >> grow a community, and thus how relevant they can ever become. By not >> retaining compatibility with the huge, growing, prolific OSS Node >> community, they're leaving a lot of functionality on the table. (I'm >> sure that someone on this list will probably point out the programs >> out there that meteor-ize npm modules, and others that de-meteor-ize >> your meteor program into a standard Node program, but my point is, >> it's not compatible by default.) >> >> In the spirit of "may the best platform win", yes, I'd like to see >> someone do what meteor is doing *better*, and take advantage of the >> ways in which meteor is sub-optimal. But the team seems to be a bunch >> of really smart and dedicated people, and they are delighting users. >> So, even if they are leaving a lot of potential behind, out-meteoring >> meteor will still be a tough task. >> >> -- >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to nod...@googlegroups.com<javascript:> >> To unsubscribe from this group, send email to >> nodejs+un...@googlegroups.com <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to nodejs+un...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > -- > Arunoda Susiripala > > @arunoda <http://twitter.com/arunoda> > <http://gplus.to/arunoda>https://github.com/arunoda > http://www.linkedin.com/in/arunoda > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
