How about providing a npm module(binary) as well. So we can use it like this. `mean create myapp`
actually this is the next step for us, we just started to work on it.
Mean Stack
71–80 of 97 posts
Re: Mean Stack
#72What's the deal with MongoDB and the node.js community? I don't find non relational databases that enticing and there are javascript drivers for postgres [1]. [1] https://github.com/creationix/postgres-js
MongoDB is used in almost every community. Especially for new languages. You can easily find relatively mature MongoDB drivers from the start for new languages, but don't hold your breath for PostgreSQL. See Rust.
I'm not sure that Rust is really a good example. While promising, the language itself and its standard library are still immature and subject to a huge amount of disruptive change on an ongoing basis.
I've had some experimental code I wrote in Rust become essentially unusable after only a few months due to significant language and standard library changes. I sure hope that somebody wouldn't spend time on a PostgreSQL library for it until the language itself becomes more stable. They'd be wasting a lot of time and effort if they did try to write such a library now.
Re: Mean Stack
#73Re: Mean Stack
#74Love it - except for the Angular part - can we get a MEEN stack with Ember.js?
we deeply encourage any kind of forking of this project. have fun break rebuild!
Re: Mean Stack
#75Guys as the author of this project one of the guidelines i had was to create it as modular and familiar as i can, so whenever I could I tried using a popular module(mongoose, passport etc.)
I deeply encourage anyone who wants to break, replace, remove, add any part of this project to go ahead and do so! Like any recipe this is just our serving suggestion.
I'd love to see an ember fork!
Re: Mean Stack
#76I’m not a NoSQL expert, but everyone I know who is considers Mongo a joke in production. And I would never use Angular in production apps (“painfully slow” is reason enough but I have ideological differences as well). That makes saying “no” to this stack easy.
I haven't seen any benchmarks that make it seem like Angular is "painfully slow." AFAIK, its on par or faster than ember.js and knockout.js. What would you use instead for MV* in the browser?
I haven't actually seen any decent benchmarks between those systems as a whole. Most comparisons seem to shy away from that (between some candidates it probably doesn't make sense to benchmark anyways). But if you've seen anything interesting on that front, I'd be thankful if you could post it. And, you're right, so far Angular hasn't let me down regarding speed.
Re: Mean Stack
#77Earlier quoted context omitted.
The "developers" dig seems unnecessary. @cuttooth and @PommeDeTerre, since you both are pushing the "JS is a flawed language" angle, what do you find are its greatest flaws?
The numerous flaws with JavaScript (the programming language) are well-known and well-documented. A few search engine searches should bring up ample information. As for its "greatest flaw", I think that may be the JavaScript community, and the general attitudes within it. There is, unfortunately, a very high degree of ignorance within the JavaScript community. There are far too many JavaScript programmers who only kn…
I know you feel like you just explained its flaws, but there's nothing here that couldn't also be said about any other mainstream language.
Re: Mean Stack
#78I’m not a NoSQL expert, but everyone I know who is considers Mongo a joke in production. And I would never use Angular in production apps (“painfully slow” is reason enough but I have ideological differences as well). That makes saying “no” to this stack easy.
Does "everyone you know" have recent experience running Mongo in production? Because I have, and from my perspective calling it "a joke" is borderline trolling. I'm not trying to be hostile, but you've got to understand that Mongo is most certainly not a joke, has lots of support, and is a very appealing option in a number of cases.
[deleted]
Re: Mean Stack
#79I’m not a NoSQL expert, but everyone I know who is considers Mongo a joke in production. And I would never use Angular in production apps (“painfully slow” is reason enough but I have ideological differences as well). That makes saying “no” to this stack easy.
What about asking these people: http://www.mongodb.org/about/production-deployments/ if it's a joke in production?
Re: Mean Stack
#80Earlier quoted context omitted.
> very appealing option in a number of cases. What cases do you have in mind?
Rapid iteration comes to mind (as a result of its lack of schemas). It's also great if your objects are JSON documents, and as such it's particularly suited for uses such as a backend to Backbone. Those are two areas in particular where I would first look to Mongo.
Don't lie to yourself, it has schemas. They are just implicit. Want to write JavaScript migration scripts for changing the Schema? I sure don't. But that is not even the begining to describe how broken mongodb design is. getLastError as a way to do write confirmation?