Good stuff! This is more appealing than that fire whatever it was database. Agree with other posters, if we could get an implementation for localStorage this would be beyond awesome. I might attempt to tackle that as I had wanted to build something like this.
FYI, there is a backbone model adapter for it as well :)
Unless you have an overclocked, ultra graphics machine running distributed apps or playing games most of the day, a desktop does not cost that much more to run. Just because your power supply says 500W doesn't actually mean you are using that much. I did the calculations on my mac mini vs my i2500K win7, which is much faster, and I was surprised the difference was about $60 a year.
I don't get what's so innovative about Meteor. You can basically do the same thing with socket.io and a thin facade layer to expose services so they have the same API on the client.
#4 If you need a new event loop then write the tests in another module, then simply run your test utility. `mocha` will run all tests in test/*test.js.
RSpec is DOG SLOW! I can run 100s of test in a couple of seconds. Can RSpec even startup in that time?
Being one of those idiots who went all in with MongoDB with our startup, I can relate. NoSQL should really be called NoDB. There will come a point where you ask, "Dude, where is my database?"
Riak looks interesting but its overkill. They recommend at least three nodes. We went back to PostgreSQL.
Sorry, I have to disagree about chiclet keyboards and I consider myself a keyboard Connoisseur and a touch typist. I own a couple of vintage IBM Model M keyboards, a Northgate, a Filco ... I've grown fond of the Apple Keyboards and my better halves and those who work around me thank me for it. Vim + Apple keyboard is coding heaven.
I do agree the ThinkPad keyboards were the best in its class.
Sorry, I have to disagree about chiclet keyboards and I consider myself a keyboard Connoisseur and a touch typist. I own a couple of vintage IBM Model M keyboards, a Northgate, a Filco ... I've grown fond of the Apple Keyboards and my better halves and those who work around me thank me for it. Vim + Apple keyboard is coding heaven.
I do agree the ThinkPad keyboards were the best in its class.
And I have used it in a previous project. I'm not questioning the quality of the driver.
My point is the inconsistency of the driver API vs the syntax used in the `mongo` utility. I don't know how many times I've looked at the MongoDB docs and then have to figure how to do the same thing with this driver.
Let's not forget about unit tests. I can run well over 100 test cases in just over ONE second! Rails is PAINFULLY slow at this.
I've done enough Rails to know how productive it is, and there are many things I miss. I'll argue though I'm more productive with node.js since we do most GUI with Backbone on the client. I can share code between client and server, for example validations.
Setting unicode, changing backspace, setting xterm-256 as the TERM variable, etc ... PuTTy configuration is unintuitive when you first try to configure it. There's a well known page dedicated to configuring PuTTy properly on Windows.
Windows! I spend most of my time coding in PuTTy + Vim when I'm on windows. In my limited testing this works as I expect with xterm-256, tmux, and Vim on my Ubuntu 12.04 Server without having to configure anything. PuTTy is a pain to configure on a new box.