ehthere

'Just one more layer of abstraction and I can rule the world!'

In Australia I can get on domestic flights without ever showing anyone my ID.

If you added a column and you want to revert back, you just drop the column again! What's so hard about that? No 'migration' needed.

In BASIC you can 'declare' a variable by simply using it. The compiler will not warn you if you use an undeclared variable. That's the analogous situation here.

You don't need to do any 'migration thing', you just add the column to the DB and choose a sensible default value? I don't see what you gain by having both 'undefined' and 'null'.

The 'odd sense of freedom' is not always a good thing either. It's like BASIC allowing you to use a new variable without declaring it. It may be convenient but nobody calls it a good idea.

'I don't need to think much about retrofitting the data for all instances of that model. I just add an attribute where its needed for the new use case, ensure I have basic checking in my ruby model object and my system keeps incrementally improving.'

That's exactly the same as adding a new column to your DB with NULL as the default value.

Piracy is already illegal.

Cruise ships already face these issues successfully.

The new 'dwarf planet' designation was a stroke of genius. It's not a planet but it ends in 'planet' so everyone is happy!

Bing?

It will depend on the type of workload. Some types will be faster, some will be slower. You'd have to run your own tests to see.

Where did you get 10GB per day from? They boasted about PETABYTES of data they've collected.

"Carrier IQ, which in the second quarter of 2011 passed the petabyte milestone in processed analytics data"

-- http://www.carrieriq.com/company/PR.LarryLenhartCEO.pdf

How does this work on a touch interface?

Carrier IQ openly boasted about this feature, and they admitted that they can 'probably' read your text messages if they wanted to.

It's like having a phone number. You'll survive without it but you're making it more inconvenient for others to communicate with you.

Every major RDBMS has both command-line and GUI interfaces to create and change schemas. What exactly is missing in the dev-friendlyness department?

You can do exactly the same document store with indexes on any RDBMS.

What about all the time you'll waste debugging your app because you can't make good assumptions about the structure of your data?