there are different philosophies on when to kill a project... and imho, this was way too quick. By way of personal example, it took us 2 years to build BizRate.com into something that could even get funded, another 5 years before it started making money as Shopzilla, and 9 years total before we had our "overnight success" -- Many points along the way we could easily have pulled the plug. Persistence / sticking to your vision is something that is sorely lacking these days. (Another more obvious example: How long did it take for Apple's design+hardware+software philosophy to strike a mainstream cord?)<p>Timing aside, this method of "putting a bullet in its head" (which is not even a good expression to use colloquially), was a terribly callous way to treat their current users too... Especially given the fact that for a few thousand dollars a month (max) they could have kept the system rolling in the cloud indefinitely, without investing any time in it. They then could have put out feelers to find it's users / content a new home... (For example, our new start-up chee.rs would gladly have welcomed oink users -- in fact we're working on a quick oink importer as I write this. :)<p>Or, even if they weren't interested in transitioning users to someone else, they could have kept things running at least until their next big idea came along to announce to their users: "Hey we've got this new great thing, come on over and now that we have it, we've decided to finally and reluctantly shutter Oink, because we hadn't seen it gain much traction. Sorry about letting you down... blah blah blah."<p>Much better for PR than "We put a bullet in your head and moved on... But, we hope you'll join us again for another round as soon as your headache subsides."