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.

From what I gather, the licence is still in the spirit of open source

It’s not though. It’s wildly against it. The spirit of open source is that anyone can take open source code and use and modify it. This isn’t the case here.

Windows 7 does not receive security updates anymore, so its use should definitely be discouraged even if it “works”.

For software devs, they almost certainly don’t want to support an obsolete OS with a small number of users, as that requires time and effort on their side (e.g. if a user has problems on Windows 7 what should they do?). And if they want to refactor some code, do they really want to test on ancient OSs and add needed workarounds / compatibility fixes?

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.

Why do you need to have a centralized pyproject.toml?

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.

Constraints are useful for restricting build dependencies of your dependencies, especially if they follow PEP-518.

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?

I really struggle to see where HATEOAS can be used. Obviously not for machine to machine uses as others have pointed out. But even for humans it would lead to terrible interfaces.

If the state of the resource changes such that the allowable actions available on that resource change (for example, if the account goes into overdraft) then the HTML response would change to show the new set of actions available.

So if I’m in overdraft, some actions are not available? Which means they are not shown at all? How can a user easily know that there are things they could do, it it wasn’t for the fact that they are in a specific state? Instead of having disabled buttons and menus, with help text explaining why they are not usable, we just hide them? That can’t be right, can it? So how do we actually deliver a useable UX using HATEOAS?

Or is it just meant for “exploration”, and real clients would not rely on the returned links? But how is that better than actual docs telling you the same but much more clearly ?

I’m taking a broad approach? The article is literally about the FCC. You know, the Federal Communications Commission. That applies to the entire country.

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?

If there is no reason for caps, why wouldn’t one of these companies simply remove them, giving them a competitive advantage, and making them more money? Why would one company reject making more?

Maybe capless actually costs them more due to bad infrastructure, and they don’t see consumer demand for it? Forcing them to go capless would in that case result in higher prices.

Maybe they form a cartel and have collectively decided to keep caps. But why, if it doesn’t actually cost them more to remove the caps? And if it does, then prices would again rise if forced to go capless.

Comcast would be quite unhappy with me as I’m arguing against monopolies, and for consumer choice.

Consider two companies, A and B.

A offers capless at e.g. $50/mo, and B offers capped at $40/mo.

Now B can no longer offer capped, and they have to raise prices to $55 to invest in better networking. A is cheaper, and pushes B out of the market. Now A is alone, and due to it’s monopoly position raises prices to $60.

End result: Your capless connection now costs $10/mo more, and some people even end up paying $20/mo more for internet.

Yay?

Reducing competition helps the ISPs, not consumers, yet somehow I’m the shill?

I reiterate what I’ve written elsewhere: protect consumers by forcing companies to add choice, instead of forcing them to remove it.

The solution to lack of choice is even less choice?

Fight monopolies by adding choice, not just accepting that monopolies/cartels are natural and just the way things have to be.

I’m curious, where can I find an ISP capable of delivering 100Gbps networking to a residential building for a reasonable price. I’m serious. Has the technolgy truly reached the level that we can guarantee 1Gbps connection to each appartment in a 100 unit building?