kinks

A cloud is just a sysadmin staff with a Sufficiently Large Deployment to have ironed out all the kinks in their hardware.

The key point is that when you impose kinks and missing regions in supply&demand curves, bad things happen.

It feels so old and slow.) * All in all, a lot of potential but lots of kinks to work out.

> A cloud is just a sysadmin staff with a Sufficiently Large Deployment to have ironed out all the kinks in their hardware.

You could test the idea by signing up just two restaurants on the opposite side of town and work out any kinks.

Let someone work out the kinks, then step in and make it better...

I guess I should do a Show HN, but it just hasn't been a priority with working out the kinks.

Still, I think I'd rather deal with some implementation kinks than intentional packet mangling like NAT.

Unless you're on a really stable version of linux/BSD, it really makes sense to wait to install any OS until the kinks are worked out.

I'll optimistically assume they are beta testing with iOS users until the kinks at worked out and can release to Android.

Still working out kinks with image loading and positioning bugs.

In the short term, I just want to get users and work the kinks out of the user side of things though.

I'm a font!", and strange linear graphics with 45 degree kinks in them.