On the other hand the reality is that divorce does happen and for people with $20 billion fortunes is different. I wonder if the Google founders have prenups in place.
Though to be fair, if you have a lavish lifestyle and go from $20bn to $10bn, I suspect it's going to hurt a lot less than having say $4m and losing half.
It's not just about money. If he has a majority share, and she ends up divorcing him and taking half of whatever she can get, it may destabilize the company. At that point, it's not just about Mark and his wife, there are jobs and people's well being's hanging in the balance.
It may not be about the money. If Prescilla has played a major role in making Facebook the $100B company then its OK. However there is no point splitting the company in half, because she was married to the founder. There is no need to demonize prenups here.
#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?
>RSpec is DOG SLOW! I can run 100s of test in a couple of seconds. Can RSpec even startup in that time?
Yes, of course it can. RSpec is not especially slow. Obviously the ruby interpreter can be slow, for any given rspec test you could write something faster in C or Java or Go or whatever. That's irrelevant.
I'm guessing you're referring to rails tests, where the whole rails stack has to be loaded with each run of the test suite, something that is notoriously slow. There are strategies to avoid this.
Also it is very easy for the naive rails developer to write tests with extremely inefficient usage of the database, which creates horrible bottlenecks.
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.
Are all modern Apple keyboards pretty much the same? I've been considering the Apple wireless keyboard for my iPad, but I wasn't sure if it would offer a superior experience to the Microsoft wireless keyboard that I already have.
To be fair, the mongo people just pulled in a driver that everyone has already been using for the past 2 years or so. christkv's driver has been in use in dozens of projects -- everything from connect to mongoose. It wouldn't make sense to drastically change the API and break all the npm packages out there.
According to the npm registry, there are just over 100 packages that all depend on christkv's library. I'm sure there are more because certain libraries like mongoosejs, simply include the library as part of their package instead of a dependency.
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.