4 ms·
You can call it what you want, but for what I (and others presumably) use it for, the 24/7 uptime is essential. Sure an argument can be made for needing to pay
by arsenide 11y ago
You can call it what you want, but for what I (and others presumably) use it for, the 24/7 uptime is essential. Sure an argument can be made for needing to pay for 24/7 uptime, but it is very clearly a downgrade in such a case where such an argument even needs to be made!
- senorprogrammer 11y ago> 24/7 uptime is essential And all that for only $7/month. Seems reasonable, for an essential service.
- infecto 11y agoNo argument needs to be made. If you want 24/7 uptime, you need to pay for it. Under the old model you were just freeloading.
- arsenide 11y agoTo clarify: I'm particularly speaking about the parent's use of the term "sidegrade." I'm not disagreeing with the idea that 24/7 uptime should be paid for (because I agree), but to call the change in terms of service a "sidegrade" is a misrepresentation of what it actually is: a downgrade in services for my particular use case.
- yebyen 11y agoYou can have a web dyno and a worker dyno running side-by-side 18h/day for free in the new free tier (unless I've misunderstood something.) You can't have one web worker running 24h/day for free, not as of next January. 18+18 > 24 I understand that your (and my) particular use case are affected negatively by this, but if it wasn't totally clear what he means by sidegrade, that's about the size it. More compute hours for your $0, but less availability.
- fooey 11y agonearly all my free tier apps are worthless if they aren't up 24/7 i have a bunch of open source, public service sorts of things and I don't know what I'm going to do with them now :(