Mean Stack (opens in new tab)

> very appealing option in a number of cases.

What cases do you have in mind?

Our relatively simple Angular app was regularly consuming 100% CPU for literal minutes and ate up 600MB of RAM until we dramatically reduced not-actually-that-crazy number of API calls we made on load (from less than 100, mostly prefetching data – to less than 15, pr-fetching sacrificed). It is mostly related to Angular’s “dirty checking” and ajax management. I have met others with the same problem. (Their solution? Use Backbone!)

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.

Exactly the discussion i had today with a colleague. Mongoose makes it incredibly easy to get started and iterate rapidly.

I have yet to experience MongoDB in a large scale production environment and the common pitfalls often cited, but let's face it - If you're Start-Up has scalability issues, it's prob a nice problem to have.

Based on my personal observations, i suspect the lack of adoption is because founders are thinking about scale prematurely - which is rather Anti Lean Startup and Anti-Pg anyway.

I saw a couple engineers from Craigslist present at a Mongo event within the last year, and they strangely acted as if Mongo were a joke—that is, they treated it like a playground, continuously talked about how and where it broke, and continuously reminded us that they didn't care about its data integrity because they were just messing around.

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 guess that makes sense but do most people who use node.js use mongo in production or just as a scaffolding tool?

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.

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?

I think very few javascript developers only know javascript. This some kind of late 90s C++ elitism or sarcasm?

is the "developers" dig really necessary? MongoDB is fine-- at least until you start seeing significant scale, and even then, it's going to run into the same issues as everything else would if you hit it too hard, too often.

Just because the query language is JSON-esq and has a javascript shell, it's therefore "Javascript" and a target of derision and scorn?

I don't feel like you addressed the parent post. It was asking why people use mongodb instead of JavaScript bindings for PostgreSQL.

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.

Some would say data-binding and logic in HTML attributes is insanity.

awesome.