You only need experienced it once for a day, if you want to. Do you restart your emulator every time you compile/build your app? You don't have to. Once the emulator run, you can build and run your application into emulator within no time.

The problem with that is it is still a pretty big resource hog. It's fine when I'm on my iMac, but on my MBA/2GB/1.4Ghz it just brings my system to a crawl.

Forget about the emulator, I wouldnt want to run Eclipse on anything with 2GB of RAM

"Think back to when Rails first came out. There was no iPhone. There was no Android. People still owned Nokias and actually bought stock in the damn company. Windows XP was still massively popular and we were fighting to get a decent version of IE (but that will never end). There was no such thing as a mobile web. No one was thinking about tablets. How old is the iPad? Not very old".

OK, no iPhone and the iPad is not very old. Wikipedia should change their contents, especially on the dates when the iPhone and iPad were launched.

If the community is the problem, I think he should focus on the community itself rather than discussing on what Nodejs is incapable of.

It's always nice to have another point of view within a subject. Would like to know more.

It's hard to cover many aspects of it when we talked about getting our feet wet. I try to include as few terms as possible that potentially confused people to start coding Nodejs-MongoDB. It's probably a big problem when you try to get your feet wet on the first day you learn about swimming just by jumping all over the pool. But then, hopefully, we learn.

Thanks for your opinion :)

I'm not sure that both Node.js and MongoDB appeal beginners.

These 2 tools are reserved for people who exactly know what they want out of their tools, not for someone who just jumped in to "web development" and wanted to use buzzword compliant tools.

Sorry for being such a snippy on Monday morning but I'm hoping people around me would become better at fundamental as opposed to combining tools w/o knowing what they're good for.

Why is MongoDB unsuitable for beginners? If beginners have a handle on Javascript it saves them from having to learn SQL and know any MySQL admin.

... and this is a good thing? as opposed to learn proper RDBMS first and learn the lingo of NoSQL (document vs key-value vs column-oriented)?

But I digress, people have different experience. I've seen projects got burned many times by beginners who have lacked of understanding of RDBMS and you may have entirely different experience where your project shines because of MongoDB.

I've pointed it in the first three paragraphs. No worries for being snippy. In fact, you aren't :)

Using event instead of callback to sequentially get the results with asynchronous way it's a potentially good idea. I also haven't learn much about another Nodejs-MongoDB libraries except the one what I have mentioned there. Please share if you have a follow-up on this technique.