Even if we assume we need to cover their downtime between rides, at a conservative estimate of "we're the only call today" that's $2400 of labor at your rate (≈$400/d, 2 paramedics, 3 shifts). TFA suggests they're not paid well.
I don't think it's cowardice, is it? The graph at https://en.wikipedia.org/wiki/Leap_second seems to indicate that adding a negative leap second at this point in time would be improper. (We're ~+0.1s off, and a negative leap second would occur if the line was approaching +0.6s. I'd like one too just for the curiosity of the thing, but … the Earth isn't having it.)
All government regulation still has to be balanced against whether it intrudes or not on the rights of the People. The government can regulate vehicles, including ensuring drivers have met whatever requirements a license might require — nobody is arguing against that. But Flock cameras do not help advance any reasonable state interest in that area; their sole purpose AFAICT is for law enforcement, and in a way that intrudes on any basic expectations of privacy.
> My problem rate with Fedex or UPS is maybe 0.1% of packages. I can't remember the last time I had a delivery issue.
Well… I had a package being delivered, and it had missed its estimated arrival; it ended with me have a long discussion w/ their support that I'm sure was fed to /dev/null. FedEx was the carrier, it turned out, and they claimed they had attempted delivery. Problem was, they required a signature. I live in an apartment, & we have a dedicated package room. But FedEx's stance is that they can't deliver to the secure package room: they require a signature. But at my apartment, they come to the door with the street address on it. Weirdly, that is not the door with the buzzer — that's at a separate, more remote door. The delivery person is not going to take the time to find that door, assuming their corporate overlord's maximum dwell time even permits them to. So they can't buzz me. So they sticker an utterly arbitrary window on the building, and leave. The landlord clears the window. I am never notified.
Somewhere this kicks around in their system until I get a call from an unknown number of "hey your package is undeliverable." But the "guaranteed" delivery date was overshot, of course.
I was, of course, home the entire time. These are what spawn the "missed delivery" memes … https://xkcd.com/921/
This is a systemic problem, not just a "one time" issue: every package shipped via FedEx that requires a signature to me is undeliverable.
The shipper (my bank, in this case) was also less-than-helpful: they apparently have no idea who they ship with, let alone what tracking number they used. Worse, they refused to refund me the extra I had paid to expedite the shipment (which, as you can imagine from the above, did not arrive on time; worse, the expiditing fee was extortionary…)
… and this is modern capitalism these days. A fractal of bad service where the customer ends up having to do 90% of the support work.
When I was younger, I decided I wanted to learn how to write games. I decided I needed to start simple, though, and I thought NOTEPAD.EXE was about the simplest thing out there. (This was in Windows 3.1.) So to learn how NOTEPAD.EXE worked, I opened NOTEPAD.EXE in NOTEPAD.EXE, and spent several hours trying to decipher the symbols' meanings.
I also wanted to experiment with Linux at a young age, and so I tried booting it with LOADLIN[1]. I didn't know what I was doing, but I did successfully boot the kernel with a minimal rootfs! So minimal, it didn't have an init — which of course causes a quick kernel panic. Didn't yet have the know how to figure out what I was doing wrong. My mom asked "did you mess up the computer?" Nope, since with LOADLIN you didn't need to format.
Had to give up on that approach, but discovered Knoppix shortly afterwards, and that taught me Linux.
The Biden administration both asked nicely for actual, factually incorrect information to be corrected by sites and pressured sites. They were taken to court over both, and they prevailed on the former and lost on the latter: the administration (any administration) is permitted to ask a site for a correction, and it is then truly at the site's discretion. They are not permitted to pressure them.
They didn't rule on it because it is out of scope of the matter before the court. The lower courts first have to make a ruling that can be appealed.
From the ruling:
> The conclusion that a Fourth Amendment search occurred does not resolve this case, because the Fourth Amendment prohibits only searches that are “unreasonable.” When law enforcement officials undertake a search to discover evidence of a crime, the reasonableness standard generally requires that they seek a warrant from “a neutral and detached magistrate,” Johnson v. United States, 333 U. S. 10, 14, who may issue a warrant only when “probable cause is properly established and the scope of the authorized search is set out with particularity,” Kentucky v. King, 563 U. S. 452, 459. The warrant issued here, as described earlier, was an uncommon, multi-step one, and the parties have contested the legality of each stage of the search process it authorized. The Fourth Circuit did not address the questions that unusual warrant raises. Because this is “a court of review, not of first view,” Cutter v. Wilkinson, 544 U. S. 709, 718, n. 7, the Court leaves it up to the Court of Appeals to decide whether, at each step of the search process, the warrant satisfied the Fourth Amendment’s requirements of particularity and probable cause
> The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized.
"persons", "papers" and "effects"; just because I am in public does not give the police carte blanche to search me.
I think crates.io is essentially just the default, and you can point cargo to an alternate package repository, if you so desire.
I've worked on projects where we vendored all third-party crates, for example, so our config just pointed to that vendoring, and I think support ought to be better these days…
The Covid vaccines have saved an estimated 14 million to 20 million lives.[1]
The trust was not eroded by scientists, it was eroded by politicians pushing lies. I'm still to this day hearing lies & misinformation repeated about the vaccines.
Generally when I'm debugging these, I need/want to know what was the preflight (if applicable), and was the preflight what was expected? When I help others debug these, generally I find there is little expectation of what the preflight "should" be, and instead just a bunch of stochastic attempts to adjust the server's response headers to get the browser to capitulate — regardless of whether that makes any sense at all.
I would also say I think Firefox's network inspector is better in this area. (But I'm often having to ask others to "no, don't send the failing request, send the CORS preflight", we need to understand what happened with it.)
> Anecdotally, lots of developers I’ve talked with don’t understand well how CORS works.
Yeah, most FE devs I've worked with seem to not understand CORS.
> Is the CORS API too complex and confusing
I think it can be hard if you don't understand why the exceptions to preflights are what they are, but the moment you internalize "because the browser can already emit that request in other cases" then it becomes obvious what categories are what & why.
> by design the error messages sent to the browser are intentionally gutted
A CORS error is not "an error message sent to the browser", it is an error generated by the browser, because the browser has decided it cannot permit the request. (Though certainly a server can not understand a CORS request as such, and returned a weird response, which would then end up getting translated to a CORS failure.)
> See, AI was trained on existing data - on all that existing C code out there (sure, and also on all the papers and articles saying what was wrong with that C code). Those bugs are in the training data, and often not marked as bugs. So when AI generates C code, is it going to avoid making the mistakes that human code made? No, it's going to generate the kind of code it was trained on. How could it be otherwise?
The generalization of this is why I think all these AI companies writing blog posts where the marketing department is just jer—ranting endlessly about how AI will improve itself into the singularity is just crazy talk. They generate a random statistically likely output, and the most statistically likely output is mid. Exceptional outputs — the ones that wow us or move the needle are exactly that, unlikely. AGI is sci-fi, and LLMs will not change that.
You can see the same effect when AI emits bash, too, and especially so since most bash is terrible, and most users of bash do not put in the effort to learn bash and its foibles. So it outputs what most people write, which is not great.
> I spent 10 minutes searching for one in the article, in the RFC, in the wikipedia page, on google, to search for a .well-known example. Couldn't find one.
I don't know how that can be, since you claim to have found the RFC; the RFC straight-forwardly states,
> 5. IANA Considerations
> This specification updates the registration procedures for the "Well-Known URI" registry, first defined in [RFC5785]; see Section 3.1.
& then of course directs IANA to establish a registry. We'd expect this section, given the very nature of the RFC is that it establishes a collection of things, so that there is an IANA considerations section should be wholly unsurprising…
And there's a link to a listing of every standardized .well-known URI there is.
> What is it with technical documentations that go deep describing what it is in plenty words but refusing to give a single example?
The RFC provides an example in the form of "example", but also in the form of "robots.txt" (as a "it could have used this, had this existed", but what else could it have done?).
> If a single macOS user works on ten different projects, should all ten projects add that line,
Not only do people think that, they also think that every pet tool that every pet user might decide to use should also end up cluttering up .gitignores for every project on earth. Worse, these people have created whole templates for this, so they can start a new project with ignores for dozens of tools they don't even use. 9 out of 10 times, this includes a broken ignore for Vim swap files.
I think these people are crazy, and like you suggest, tooling that is particular to you should go in the user's ignore, and tooling particular to the project should go into the repo's ignore.
I long to work on a team who values shipping correct code over shipping anything until they're up to their eyeballs in technical debt and can't ship.