3 ms·
Why is it that you claim limits are unworkable? If you can track or enforce it (others have been for years) then couldn't you make it an optional field or check
by ilaksh 4mo ago
Why is it that you claim limits are unworkable? If you can track or enforce it (others have been for years) then couldn't you make it an optional field or checkbox?
- tptacek 4mo agoEvery limit is a commanded outage. We can refund an unexpectedly high bill. We can't refund downtime.
- tough 4mo agoYou’re optimizing for one class of customer by denying another class a choice they explicitly want.
- tptacek 4mo agoThat's true, in the sense that it is true of every coherent business. What would not be a true statement is that we somehow profit from the discomfort of the "disfavored" cohort of customers here. If we could serve them reasonably without making terrible compromises for everybody else, we would do so, and we would profit from that.
- tough 4mo agoI guess business is all about making the right compromises
- ilaksh 4mo agoWhich implies that you cannot reasonably serve the "disfavored" cohort (self-funded startup or small business). In other words, you have admitted that I was correct in that the business model is deliberately aimed at businesses that likely can absorb surprise expenses, and it's not appropriate for others.
- tptacek 4mo agoWe probably have different definitions of "small business". At any rate: my only point here is, it's not our business model to earn a premium off surprise bills. Railway does hard billing limits! Railway's great. Use them! I'm not here to sell you on Fly.io.
- ilaksh 4mo agoSo write "WARNING: your service will go down if you exceed this limit. We cannot provide refunds for this. To avoid outages in the event of unanticipated traffic, do not enter a spend limit."
- tptacek 4mo agoA learning from the past 6 years: warnings do absolutely nothing. If your answer to a problem is a warning label, you have no answer for the problem.