My worst close-calls were a result of ABS engaging at very low speed. In all cases, I reduced the speed to 2-3 MPH approaching a snowy intersection, but the car refused to let the wheels lock and "sink" in the snow.

Instead, it's all too happy to drift into oncoming traffic at a glacial pace. It could be specific to the various Toyotas I have owned...

Technology is defined as that thing which almost works correctly.

Sorry to hear you had that experience! I've lived places where the "sink into the snow" was the right thing, but where I live now, there's very likely ice under the snow, so it's not clear if that would help.

In my experience, having to explain a software's design in plain English often reveals that some aspects were poorly thought-out in the first place.

...which in turn triggers defensiveness in some people, making a bad situation worse.

To provide some context for this release announcement, the LTTng documentation has a nice intro to tracing and an explanation of how LTTng relates to other Linux tracers.

https://lttng.org/docs/v2.13/#doc-nuts-and-bolts

That's not true.

For example, the microphone of the X1 Carbon 7th generation still doesn't work out of the box. You need to blacklist a handful of kernel modules and edit your PulseAudio configuration to force the loading of an ALSA source hooked to the correct device ID.

The Arch wiki has an article cataloguing issues and workarounds (with various degrees of success) for every generation of the X1.

I would guess memory map the whole file, then do the equivalent of:

memmove(beginning_of_file, beginning_of_file + 300_m_line_offset, file_size - 300_m_line_offset);

We have very different experiences; I hear baladodiffusion (or balado) very often in Montreal.

I'm from Montreal. It's not "chambre-a-montrer", it's "salle de montre". Also "coussin-a-gonfler" is "coussin glonflable".

As for computer-science related words, I think the OQLF (French Language Office) does a great job overall. "Courriel" (e-mail) is one of their best contributions and is used regularly.

It's very ugly, but at least it doesn't seem to limit you to 15 characters like on Linux (prctl/pthread_set_name_np).

That limit makes it pretty hard to provide meaningful identifiers in a non-trivial application.

Funny thing, windbg apparently uses a fixed-size buffer to store the old-style thread names and it must use strncpy to copy them in because if your thread names are long enough then windbg displays the first ~15 characters and then shows garbage, because strncpy doesn't guarantee null-termination.

Harmless I think, but sloppy.

Yes, and they will also move the goal posts when you explain why their solution doesn't work.

I feel there is something missing in this whole discussion and that's the question of unsolicited advice. I don't think anyone will feel insulted if the j-word comes out after they have asked for help on a problem.

On the other hand, It's hard not to feel like that question is condescending when it is unsolicited.

k8s feels much more like an effort to commoditize this space through standardization. It's a pretty common business strategy [1].

[1] https://www.gwern.net/Complement