throwaway_se099

Yes they have a reputation for merciless shuttering of services, but come on.

What is ample time for a company that hired a webdev one time to build them a static website and never checks webmaster@domain emails?

That kind of outfit is much more likely to be a victim of missed renewal or a myriad other technical screwups than a Google-initiated exit of the registrar business.

I feel like Google marketing has no idea the absolute monster of a problem they've created by allowing their business to get a reputation for being extremely unreliable in the B2B space.

They can certainly count on a spate of hyperventilating HN posts whenever they announce any kind of service-related news.

More seriously, their most celebrated servicides are consumer-oriented, like Google Reader. "Extremely unreliable in the B2B space" sounds like an exaggeration to me.

I also believe you have to follow the Greek Orthodox religion to be able to visit - they might make some rare exceptions.

You need a permit (effectively, a visa) to enter the peninsula, and there is a daily quota. About a tenth of available permits can be issued to non-Orthodox visitors. They don't single out the Greek church from other Orthodox churches (AFAIK).

[I researched the entry requirements a couple of years ago out of curiosity, but never tried to actually visit. Something may have changed in the meantime, but somehow I doubt it :)]

I've never seen a moped that you could pedal like a bike even in a photo.

As an example, https://en.wikipedia.org/wiki/Puch_Maxi

The US FDA was among the first world-wide to approve (Europe was months later)

UK MHRA: Dec 2. US FDA: Dec 11. European EMA/EC: Dec 21. Months later? Hyperbole doesn't help your argument.

There is a perception that D has shot its bolt, having been around for quite some time without making a noticeable impact, either by itself or by influencing the mainstream.

This seems to be veering in the direction of the Land of Moved Goalposts and Non-Sequiturs, but I'm game for one more round, because lockdown.

It's rather unlikely that the first issue, which is an ordering problem during service shutdown, has much in common with timeouts during service startup, which you have described as your original issue.

The Stack Exchange question is a straightforward how-to for adjusting the timeouts.

5773 requests a clarification of the documentation of timeouts and signalling behavior.

3901 is a case of misplacing the timeout directive.

2047 is a sort of philosophical problem of reporting uniformity vs. consistency with manual configuration. The systemd team prefers the former, whereas I would prefer the latter for not violating the principle of least surprise, although I understand the reasons for choosing the first option.

Anyhow, I still don't see good support for your assertion of the complete lack of timeout documentation, just tangentially related distractions. A complex set of problems, and service management does qualify, will have edge cases, insufficiently clear documentation, and outright bugs, which is why software is never finished. Older init systems had all of these, but they didn't give you the tools to attempt to rectify the problems, so it was all more or less swept under the rug. Using a facile "shit, fullstop" characterization therefore tells me more about your views than the actual technical merits or documentation quality of systemd.

Nothing in the documentation hinted that this was a feature of systemd anywhere

Nothing except three paragraphs in systemd.service(5) (TimeoutStartSec=, TimeoutStopSec=, TimeoutSec=), with references to systemd-system.conf(5) where the defaults are described. I wouldn't call that undocumented. Whether it should exist by default is another question; on balance, I'm glad it does.

Cyclists in Amsterdam don't wear helmets as a rule -- YouTube is chock full of videos of Amsterdam bicycle traffic, so you can see for yourself. Therefore, it's not surprising that a texting cyclist wouldn't wear a helmet.

To be clear, texting on a bicycle is not a good idea, helmet or no helmet.

Armchair analysis based on sparse information

That's internet in a nutshell, and HN is not that different despite pretensions to the contrary. What partly redeems it is the better than even chance that in posts with technical subjects, someone informed and/or competent will appear and write something worthy. You learn to filter out the rest.

The Governor claims he never attended a meeting. Wouldn't this be an easy item to fact check by getting records of meeting attendees?

That meeting was probably never on the official schedule. There are numerous ways to arrange such things off the books. The Gov's office can certainly provide the schedule which will give him plausible deniability, after which it's he said she said, unless another witness comes forward.

(If the above strikes you as too underhanded and sleazy, well, the whole affair is such. The lure of Amazon HQ2 was in play, remember.)

Obama not just invaded other countries, he also was bold enough to accept Nobel Peace award for it.

I think your timeline is a bit scrambled. Obama got the Nobel Peace (or rather, Not-GW-Bush-Jr) prize in the first year of his presidency, before any foreign interventions that could be realistically ascribed to his policy.

Oddly, the linked keyboard doesn't appear to have a tab key but the Vi source code you found contains them? Am I missing something obvious?

Vi has the insert-mode commands for indenting (Ctrl-T) and unindenting (Ctrl-D) the current line. If you're used to them, you don't really need Tab except for aligning things within the line. Also, Tab is Ctrl-I.

"How do we close a statement.... errr. Let's spell it backwards".

That's on the original Bourne shell and its author's evident love for Algol 68. Wikipedia has a fine summary.

Sounds like UK…

Britannia Hospital?

In those cases, the switched-to architecture could emulate the previous one with acceptable performance. For the hypothetical amd64 -> aarch64 transition, I'm unaware of the existence of software, silicon or the combination of the two which could emulate the former on the latter while staying in a reasonable power envelope.

Emulation is non-optional if one wants to avoid splitting the ecosystem.

With certs that short-lived, you're just reinventing Kerberos, badly.

A lot of developers can surely get by with a QEMU RISC-V image, which exists and is known to boot at least Fedora.

Fusion has no toxic or radioactive bioproducts.

D-T fusion, which is the easiest to achieve and perhaps sustain, directly produces He nuclei (that is, alpha particles) and rather energetic neutrons at 14 MeV. Those neutrons, aside from being a form of ionizing radiation themselves, are bound to transmute some of the surrounding material into radioactive isotopes. So, I don't think that "no toxic or radioactive byproducts" is correct. However, the results are easier to handle than those of fission reactors.

C++ at least has extern "C" going for it, which disables name mangling. Rust doesn't have that

It does, it's called "#[no_mangle]", and together with an extern "C" fn declaration you get a non-mangled function directly callable from C.

Uber's system could obviously brake but not 'emergency brake'?

There are two systems in the vehicle. One is the manufacturer's, let's call it System V after Volvo, and the other is System U, for Uber.

System V provides collision detection and emergency braking. It played no part in this incident, since it's inactive if the car is under control of System U, which it was at the time.

System U can decide that the car should slow down in some situations. Let's call gradual slowdown Action U1, and emergency slowdown Action U2. The incident called for Action U2, by Uber's criteria. What Uber said is that a) they disabled automatic execution of Action U2, punting it to the driver (really, a bored passenger in driver's seat), and b) that the driver would get no indication of emergency situations from the system.

The idea is, presumably, that driver should watch the road and react in emergencies. But we also know that the driver had the duty of working with the onboard console, which must have been quite a distraction. Effectively, Uber has set themselves up for failure, and it happened.

Ah, a kindred spirit. I detest forced cheerfulness that is so frequently required from public-facing workers. Be neutral. Be professional. Don't be hostile. That's all acceptable. But that must-be-upbeat-at-all-costs straitjacket... Some people are naturally sunny, and they should be cherished. But the majority probably aren't, and please don't force them. Sometimes you can see the flash of resentment in their eyes, which probably isn't directed at you personally, but won't fail to make you feel shitty if you're attuned to it.