In the general case, Dropbox benefits from unused (but paid for) capacity, while users want a fixed price, even if they're overpaying (compared to use). For some products, pay-as-you-use seems better and more attractive, but Dropbox wants simplicity and ubiquity, so I don't think that model would be better for them.
sorry, I meant as i new product for advanced people, dropbox should not do it, that would be stupid.
I just miss a service, where I pay for what i use, and I would then hear if hackers also wanted that? or they where just fine with dropbox two packages :)
Great way to sum it up, by that measure I'm a clear introvert. That doesn't mean shy, quiet in gatherings or even unhappy in company of others, but group time is exhausting and alone time is, as you say, recharge time.
To sum it up, clients (SPDY enabled by default in FF13 and already in Chrome) and servers (Apache, nginx, Jetty, node, Google sites) are becoming available, some niches (mobile, high latency) are bound to benefit a lot and it's a good (better?) solution for the general case.
I would guess they did and that they were probably selected. It's just that the list is still incomplete (180 orgs selected, displaying less than 100 as of right now).
Here's what I'll be reading on allocators tonight, any further suggestions (following all the links in comments is part of the deal)?
http://en.wikipedia.org/wiki/C_dynamic_memory_allocation
http://www.facebook.com/notes/facebook-engineering/scalable-...
http://locklessinc.com/benchmarks_allocator.shtml
http://blog.reverberate.org/2009/02/20/one-malloc-to-rule-th...