[-] spoonbill@programming.dev 1 points 3 days ago

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.

[-] spoonbill@programming.dev 1 points 4 days ago

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?

[-] spoonbill@programming.dev 1 points 6 days ago

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.

[-] spoonbill@programming.dev 2 points 1 week ago

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

[-] spoonbill@programming.dev 1 points 1 week ago

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.

[-] spoonbill@programming.dev 4 points 1 week ago

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

[-] spoonbill@programming.dev 5 points 1 week ago* (last edited 1 week ago)

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 ?

[-] spoonbill@programming.dev 3 points 1 month ago* (last edited 1 month ago)

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.

[-] spoonbill@programming.dev 2 points 1 month ago* (last edited 1 month ago)

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.

[-] spoonbill@programming.dev 3 points 1 month ago* (last edited 1 month ago)

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?

[-] spoonbill@programming.dev 12 points 1 month ago

limiting how much I can use in total is bullshit. It’s not like it can run out.

There isn't a limit because it "runs out" of data, but because of statistics, and the fact that bandwidth is limited.

Adding data caps reduces the total data volume, which in turn statistically reduces the average bandwidth used by all subscribers together (or whatever subset shares a connection).

Another approach would of course be to reduce the speed of each individual subscriber, but it may well be that subscribers prefer e.g. to be able to watch 10h of 4K video, vs 100h of 1080p video, despite the former being a lower volume of data.

Essentially it comes down to whether you want lots of data, but slowly, or less data but quickly (assuming the same price).

It seems weird to ban consumer choice here.

A related, but different, question is if the consumer truly has a choice in the US. But to me it would make more sense to solve the competition question instead of even further restrict consumer choices for those that do have a choice.

[-] spoonbill@programming.dev 5 points 1 month ago

What do you mean by "screen grab"?

view more: next ›

spoonbill

joined 1 month ago