Honestly I don’t need to know anything about it at all except that it’s a payment system designed by GNU
Then you seem to know even less then you thought? GNU supports development, but each project is independently designed and developed. Taler's roots are in academia.
Because it's not a crypto-currency it is a lot more efficient: e.g. no need for wasteful proof-of-work or staking. So it certainly does not have all the downsides of crypto.
Here is another prediction: the volume of that bet would be nowhere near where it needs to be to make the bet interesting.
Disagree? Create the bet yourself and prove me wrong.
If most people prefer pyproject.toml over requirements.txt, even if it does not support everything you need, isn't it more likely that you will have to change workflow rather than python remaining stuck with requirement.txt?
I was asking why you need to have a centralized pyproject.toml file, which is apparently why you need constraint files? Most people don't have this workflow, so are not even aware of constraint files, much less see them as a must-have.
My only use case so far has been fixing broken builds when a package has build-)ldependencies that don't actually work (e.g. a dependency of a dependency breaks stuff). Not super common, but it happens.
But pyproject.toml supports neither locking nor constraints.
How does HATEOAS deal with endpoints that take arguments? E.g. I have an endpoint that merges the currently viewed resource with another one? Does it require a new (argumentless) endpoint showing a form where one can enter the second resource? Wouldn't it be quite inefficient if you have to now do two (or more) requests instead of just one?
Data caps are on all plans.
Nonsense. There are lots of plans without caps. Maybe not where you live, but at most that means caps should be banned where you live. IMHO it makes much more sense to require offering a cappless plan, rather than banning capped.
Edit: Googling for "capless internet usa" gives as the first result https://broadbandnow.com/guides/no-data-caps, listing several providers.
Indeed two companies is not really competition. So why not focus on that, instead of reducing choice, which may lead to even less competition by making differentiation harder?
I would like to know how you figure that load of horseshit. The average customer never even hits the data cap, so it’s not like it’s just cutting people off so others can get on.
Well no, of course not. That would upset people. What it does is make people afraid of hitting the limit, which makes them concious of data use and reduces it, even if it does not actually hit the cap.
Very few places have any choice about what service they get.
Most of the country has no choice, so remove choice from those that do, to make it even? Shouldn't we rather make it even by giving everyone choice? How about instead e.g. forcing ISPs to offer capless plans, while still allowing for capped, but cheaper, plans for those that prefer it?
Yet another alternative is jsonata.org