131–134 of 134 posts
Earlier quoted context omitted.
My custom packaging startup Packlane ( http://packlane.com ) uses Meteor. Really grateful for this update since the old Mongo version had some major issues.
Unable to connect to any application instances.
Earlier quoted context omitted.
From what I have seen the tooling is definitely great. I am not the worlds biggest fan of Ruby on Rails, but one aspect I have always liked is the scaffolding. Being able to generate the skeleton of an application from the command line without needing to glue anything together or read documentation on multiple plugins. Don't get me wrong, I love working with React.js, but it isn't a framework and aspects like dealing…
There are some guys that created a Meteor code generator: http://www.meteorkitchen.com and yes there's the NPM iron-cli.
Earlier quoted context omitted.
With no reasons as to why, this reads like either a paid comment or a fanboy/girl. Would you care to expand?
Done. I comment from a too active account to be a paid comment.. Fanboy maybe a bit :) but you can be sure I'm a very critical person.
Earlier quoted context omitted.
Absolutely, I made a comment making a similar point when they hit 1.0 The Meteor marketing team seems to want to entrench themselves in every naive tech company they can and I can't believe that there could be so many Meteor users here with enough experience to comment so stridently on it. My experience with Meteor was that my current company hired someone (who is/was literally writing a book on Meteor) to be the lea…
Sorry you had a bad experience with the developer. However, there is no such thing as the "Meteor marketing team". Meteor doesn't employ any marketing people (yet). Anyone talking enthusiastically about Meteor is just genuinely excited about it. I'm curious to hear specific examples of esoteric concepts that you had a tough time with. In my experience, Meteor is the opposite of esoteric and actually very easy to work…
DDP is an esoteric concept, the idea of mini-mongo is an esoteric concept. And the tough time I had with them was in understanding why it was important for our application and how I was supposed to accomplish certain things within the construct.
Here's another example, we had the need to allow users to upload a zipped folder of web content which would then be unzipped to a location on the file system that was acting as our "cdn" until that location was an actual CDN.
Everything about accomplishing this was an enormous headache because it had to be done the "meteor-way" and it wasn't even a dogmatic thing (like some people are about the "angular way")... we literally had to do everything the Meteor way because it's isomorphic and you can't isolate anything outside of it without tremendous pain.
Another example of Meteor problems? How about when it upgraded to 0.9 and I couldn't run `meteor --version` without it trying to automagically upgrade to 0.9, which was a version that broke all a bunch of the 3rd party meteor plugins we were dependent on. We had to essentially just pray that our production application didn't spontaneously upgrade itself and embarrass our company during a fund-raising round.
You can apologize all you want and blame whatever on this particular dev and/or a naive implementation; but the truth is that Meteor over extends itself with its blatant self promotion and cares more about getting entrenching itself in the startup/web-development zeitgeist and than it does on actually being a useful tool.