Hacker News Reader

Comment by kzhahou | Hacker News Reader

Truth is, this service never quite delivered on their promise. When my last two startups closed shop, it took shutdownify over 3 days to process the first one, and the second was still a full two days to get up and running. At that point I could have just put together a page myself.

It didn't help that they rewrote their tech stack from Ruby to Node even as they were trying to find customers. In the end, the user doesn't care what it's built with.

View on HN

It really is a company that is destined to fail: only during a bubble would such an idea get VC funding, but it's only after the bubble bursts that they'd have a hockey stick growth. It's an enigma wrapped up in a paradox

They got VC funding‽

craziness… I don't believe it.

"It's the Web 2.0 version of fuckedcompany.com!"

My experience was quite different. Good content, fast delivery, 10/10 would shutdown again!

I too am let down over their broken promises. After $30 Million in seed funding you'd think they'd get their act together.

> In the end, the user doesn't care what it's built with.

Let alone the user who is facing a shutdown of their business.

This turn of events is quite surprising. After they secured the .com of their company name, I thought they'd made it as an industry standard.

They had to transition to Node. The UI was really counter intuitive in Ruby.

This is one of those posts for which poe's law was written. (notsure)

Challenge accepted!!!! (Possibly missing the point)

     setOfAllPossibleStatesOfWorld.every(s => s.app.isRewrittenInNode) && app.rubyVersion.hasReallyUnintuitiveUI

I think they could have served their shutdown notices off of nginx and then they could have held up under reddit hugs, or at least with cloudflare. Ultimately, a static page cannot be optimally served off of Node.

Reply on news.ycombinator.com