196 karma · joined January 22, 2010
Whether this means that they should be is another matter, of course.
1. Competition. If you provide N gigabytes of storage/bandwidth, another provider will offer N * 2, and they instantly look more competitive, even if they aren't even actually capable of providing that. So, back when we provided limited plans, we were constantly being forced to increase our resource promises to unrealistic levels just to avoid looking stingy.
2. Expectations. If you provide N gigabytes of whatever, customers will expect (and demand!) that their site be able to use up all of their provided resources. This is both on a policy level ("what do you mean I saturated the interface?") and on a technical level ("why can't I serve 100 gigabytes of dynamic HTML a month?") This becomes an increasing issue as competition drives the provides up, and the actual resources you're supposed to provide are absurdly high. (Consider for instance 100tb.com, which was mentioned earlier in this thread - good luck actually pushing 300+ MBit constantly.)
In practice, the policy we've got now actually works better in some ways for customers because they don't have to care whether they're exceeding resource limits, either subjective OR objective. So long as they're running a site which complies with our Terms of Service, we'll do our best to keep it going, even if it gets big.
* Don't use enough resources that you make it hard for us to provide good service to other customers. (Saturating the network / filling the filesystem = bad.)
* If you're legitimately using lots of resources, we'll move you around if you start getting near the limits on the hardware you're on, but we won't install new hardware just for you.
And, of course, you're also required to stay within the ToS, which exclude most of the really obvious ways of burning through lots of resources. (Public upload / mirror sites aren't permitted, pirated media is obviously a no-go, and you aren't allowed to use your "unlimited" disk space for content that isn't part of your site.) We've got some $10/month customers who are using insane amounts of resources; so long as they don't expand beyond what we can handle without building new infrastructure just for them, we're happy to keep them on.
http://developer.apple.com/library/mac/#documentation/UserEx...
And I suppose the author was also "bleary-eyed" when she plagiarized all the other articles which were identified as having been taken from other cooking magazines?
a= x >> 32
return (a + x)^a
Careful; right-shifting by >= the size of the type is an undefined operation, and might not do what you expect in all cases. (For instance, it might do nothing at all on x86, as integer shifts/rotations in ia32 are all performed modulo 32.)Perl has real arrays as well as hashes, though. PHP only has one object which acts as both.
> PHP has both lambda's
create_function() isn't really a lambda: the created function isn't bound to the local variable namespace that it was defined in.
apt-get install cpuburniOS, on the other hand, is designed to run on a few specific devices. The iPad required some work from developers for full support — and that was for a device which still closely resembled the existing iPhone and iPod Touch.
It may be telling that www.qingting.biz is hosted off of a Taiwanese DSL IP...