Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That is nice in theory but nobody really wants that. In practice I do not want to run my app on 40 different services potentially owned by different companies. If you mean that inside one company is fine than I believe ec2, s3 etc seperately already provide what you say: if you would make them simpler it would get annoying as you would have to set up yet more services (within the same portal, which is a bit better) to get stuff done. I think the theory is nice to start off but I do not think there is a real market for 'dead simple with one little useful thing'. Then again: try it, who knows.


"Then again: try it, who knows."

You know what, I think I will!

What should I call it ?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: