Love it - except for the Angular part - can we get a MEEN stack with Ember.js?
Was going to say the same thing.
Mean Stack
21–30 of 97 posts
Re: Mean Stack
#22Earlier quoted context omitted.
Probably because mongoose is so well written, it feels inferior to use another kind of ORM library. I'm guessing nobody has written something as good as the activerecord library in the ruby world for node.
I just found node-postgres and it looks okay. Active development and issues look like they're not major. Do you have any experience with it? https://github.com/brianc/node-postgres EDIT: Whoops, its clearly just a client and not an ORM. How about https://github.com/dresende/node-orm2 instead?
I mean you're kind of trying to say "Why not X?" The answer is X would probably work fine, but Mongoose got there first, set the standard, has lots and mindshare, and is very well written and tested.
Could most everyone use D instead of Go or Java? Yeah, probably they could. Is one significantly objectively better than the others? Probably not.
I've used Mongoose extensively and it just works. It feels really idiomatic and has a lot of love in the community. I don't have a reason to look anywhere else.
Re: Mean Stack
#23I’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.
Re: Mean Stack
#24It's pretty sweet, I cloned this project to get started and it was much harder to learn at first since there wasn't an example of the basic CRUDs; They added examples now, so the learn curve is less steep.
Re: Mean Stack
#25Earlier quoted context omitted.
It's nice to be able to get up and running and just throw documents into a database without having to specify what that data will look like up front.
I guess that makes sense but do most people who use node.js use mongo in production or just as a scaffolding tool?
Who the heck just uses mongo as a scaffolding tool? I don't know anyone who does that.
Re: Mean Stack
#26How about providing a npm module(binary) as well. So we can use it like this. `mean create myapp`
A good example is phonegap: http://npm.im/cordova
Re: Mean Stack
#27What'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
JavaScript "developers" feel the need to not use any other language than JavaScript, so they decided to shove it into as many unnecessary places as possible, even if their code more frequently ends up being an unmaintainable mess with no noticeable performance gains.
You are so right. Why try new things and test new ideas. Everything we have is perfect as it is! No need for a car, walking will get you there! We don't need moving pictures, books are fine!
Do you even know anyone that works in Javascript? I happen to like JS but pull out PHP or Python or whatever I need to get the job done when I have to. And I'm not an exception.
Re: Mean Stack
#28So much hate on HN these days. Thanks for sharing, that's definitely a very useful and productive stack that I keep going back to again and again for every projects. Will give it a try next time.
Re: Mean Stack
#29I spoke of the "MEAN" stack today - cool to see others using to a tee - with Mongoose and Passport.
Two other nice packages:
Nodemailer - for emailing - npm install nodemailer
Moment.js - for time/date formatting, and a ton more (manipulation, etc) - npm install moment
Re: Mean Stack
#30I’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 love Angular and have never found it to slow working with even quite complex directives and tons of filters. API responses take longer than Angular does to load.