The general problem the average user has with a metered instead of provisioned billing model for computer services is you can’t easily control for cost overruns. From the old days customers getting stung for hosting costs when slashdotted or DOSed, to last decades microservice shock horror of the CI retry loop that burns money overnight to today’s AI that you basically have no idea how efficient the AI will be while it ponders your question, you are just setting yourself up for disappointment and cost overruns and a feeling that you’re not getting the value for money you got last week etc.

▲

gruez 2 days ago | parent | next [-]

>The general problem the average user has with a metered instead of provisioned billing model for computer services is you can’t easily control for cost overruns.

Is this an actual issue aside from people letting their autonomous agents run overnight?

	▲	wood_spirit 2 days ago \| parent [-]
		I can speak of myself. Sometimes my session starts out well and I get the AI to cruise to 80%. But then gains after that seem impossible and what was built steadily unravels and then I get the compacting conversation message and realise that I’ve just spent a lot of money on nothing.

▲

2 days ago | parent | prev [-]

[deleted]