Comments URL: https://news.ycombinator.com/item?id=49711667

Points: 3

# Comments: 0

This is is to change the economics so that there is a cost to a business for automatically denying, just as there is a cost to the claimant when the business automatically denies.

> Home/auto insurance will often give you a black hole for claims; the adjuster won't get back to you for months at a time. But if you keep calling them enough to be annoying, they will usually eventually pay out.

Fortunately I live in a more reasonable country, where I don't have to keep chasing them; I can simply claim through the court system instead. I think the system works here - I haven't heard that to be a problem here.

I think it depends on the device. If I buy an iPhone, I have the expectation of installing apps on it after purchase, and that necessarily involves a relationship with the app store provider (ie. Apple), not the store I bought the phone from.

With a TV, I suppose it depends on whether I want to install media apps like Prime Video or Netflix on it. I understand that there will be people who don't want that, in which case I agree with you. But others want to be able to run this stuff somehow, whether it's directly on the TV or via some HDMI device like a Chromecast or a Fire Stick. At that point, they _do_ want a relationship with some hardware manufacturer so that the third party app can be delivered to run on the hardware.

How do drivers remember their daily PIN?

Do we? We only know that at most one thinking person believes they have it, and everyone else claims they have it.

A lookup table of normative specifications of CLI arguments would also be Reference.

So they are not synonymous.

To be clear, I'm not advocating for navigation that must always have this structure in cases where it's redundant. I think people should do what makes sense. But I think it is nevertheless useful to not mix the different categories.

I don't find this question difficult. Without looking anything up, a tutorial exercises a contrived example for learning purposes, whereas a how-to guide provides instructions suitable for real world execution.

This is handy for quick scripting as a natural extension of a command line interface. A counterexample might be an equivalent script using the Python subprocess module. For a simple script, the required extra quoting overhead is not worth the trouble. For something complicated it’s essential and a shell script is no longer suitable. For something in the middle, a carefully crafted shell script (eg. one that passes shellcheck) may be the most suitable solution depending on the situation.

Both cases have their place. It’s about using the right tool for the job.

I don't think this is notable. The process requires five seconders, so you're just seeing the set of people who seconded asynchronously before there were obviously enough that others didn't bother. The culture is to avoid unnecessary noise and leave it for the vote.

* drove