[melvinram]

Comment I left on the post:

As a potential customer, instant deployment is not what appeals to me. If I knew that 1 day after my code was done, my app would be working just perfectly, I'd be a happy camper. Instant deployment = cool but not mission critical... at least not for me. (Now, if deployment took 2 weeks, I'd be pissed.)

What appeals to me about Heroku is exactly what I like about my MacBook Pro: It just glides. I don't have to think about it. Things just work (at least in theory.) It's not the time, but the thinking about deployment that I'd like to remove.

I just click the magic deploy button (command) and tada, "It's a live." And if I hit the jackpot and land a massive client or show up on TechCrunch, things will just keep on gliding smoothly. And hopefully, I'll make more money and serve more clients.

That is the ideal I'd like to reach.

Now instant deployment might be something I fall in love with (like git) but I'm not there yet. I just want things to "just work" for now.

[jamesheroku]

Ah, bingo. Yes, "it just works" and "it glides" are exactly what we're going for. Our version of the magic deploy button is "git push". We've got some great detailed posts coming up about this.

The thing that we've discovered is that instant and "it just works" are tightly related. If something takes minutes or hours to do (even if automated), it's likely that there are many steps involved - each of which is a potential point of failure.

[ryanmahoski]

Your last sentence rings especially true. Each step is a potential point of failure. I tried to set up cap and passenger one day but got stuck on a couple of steps. Sure I could have plowed through and gotten it to work eventually, maybe switched to a different computer or whatever but time is precious. The word "easy" is thrown around too casually in tech circles. Today I've got three domains running on herokugarden and it still shocks me how short the procedure is. Thanks.