Different hobbyists have different reasons for doing their hobby. Some just want to learn new tech, any tech, and for them, learning how to deploy on a VPS is a good use of time. But others would rather focus on frontend dev - it's a hobby, after all, the point is to do what's fun - or solving problems for their friends, or learning about a market. It makes no sense for these people to worry about sysadmin stuff or deployment.
Well... More concisely, what I'm trying to say here is that often time we don't consider all the costs, just the monetary ones, which leave us in situations like the poster's current one.
He considered the monetary costs, but didn't think through what other costs are associated (time/stress/performance/etc) and has come out "on bottom."
It does make sense if you do a proper cost benefit analysis, to yourself, in this situation. Otherwise, he'd pay Heroku what they're "worth" and never have written this blog post.
It didn't sound like he has come out "on bottom". Rather, it sounds like he's evaluated all the costs and decided that Linode fits his needs better.
The blog post, presumably, is because there are still things that he misses about Heroku, and so even though Linode has come out on top, he wishes that there were some sort of hybrid solution. That, and there may be other people in his situation that haven't yet made the cost/benefit analysis themselves and aren't aware of alternatives.
Comments
Different hobbyists have different reasons for doing their hobby. Some just want to learn new tech, any tech, and for them, learning how to deploy on a VPS is a good use of time. But others would rather focus on frontend dev - it's a hobby, after all, the point is to do what's fun - or solving problems for their friends, or learning about a market. It makes no sense for these people to worry about sysadmin stuff or deployment.
Well... More concisely, what I'm trying to say here is that often time we don't consider all the costs, just the monetary ones, which leave us in situations like the poster's current one.
He considered the monetary costs, but didn't think through what other costs are associated (time/stress/performance/etc) and has come out "on bottom."
It does make sense if you do a proper cost benefit analysis, to yourself, in this situation. Otherwise, he'd pay Heroku what they're "worth" and never have written this blog post.
It didn't sound like he has come out "on bottom". Rather, it sounds like he's evaluated all the costs and decided that Linode fits his needs better.
The blog post, presumably, is because there are still things that he misses about Heroku, and so even though Linode has come out on top, he wishes that there were some sort of hybrid solution. That, and there may be other people in his situation that haven't yet made the cost/benefit analysis themselves and aren't aware of alternatives.