Knowingly.

Microkernel architectures still always involve doing a full context switch when moving between processes. All the registers need to be reloaded, importantly including the entire page table. The page table flush is particularly painful.

Hi. I think you are confused.

Air India crashes/fatalities:
* Air India Flight 101 CONTROLLED FLIGHT INTO TERRAIN -- https://en.wikipedia.org/wiki/...
* Air India Flight 855 PILOT ERROR -- https://en.wikipedia.org/wiki/...

What does the word perfect mean to you? Those are crashes. People died.

We can even add:
* Air India Flight 182 BOMBING -- https://en.wikipedia.org/wiki/...

Though that's also on the staff at the airport doing security screenings.

For the Irish language course the recordings of native speakers were taken offline in 2023. The AI replacements are nonsensical.

This story is about AI generated courses, not voices, but my post was still (accidentally) on-topic: when they previously used AI to increase volume of content, they were ok with quality being thrown out the window.

The AI generated courses might be low quality, and the original (English) courses might also go downhill because the type of exercises they produce may now be restricted to the type of things that their AI is able to reorganise for other languages. E.g. it might go further in the direction of vocabulary memorisation.

Isn't it that they call it "español" in Latin America, and "castellano" in Spain?

Unfortunately, the voices are really bad.

It's a pity they don't also make available the old courses, with audio from native speakers.

To be extra clear, here: titanium melts around 1,900 kelvin. The temperature of re-entry is 3,200 kelvin. Yes, 3,200 kelvin is "below" the temperature required to make titanium boil (by 300 kelvin), but you'll note that the 1,900 is 3,200 by 1,300.

Who honestly thinks titanium that's been heated to 'just below' its boiling point for half an hour, will be somehow intact once it's slow enough to not self-generate plasma due to atmospheric drag?

Ridiculous.

How does a thing that isn't water, 'water in the ocean'? What? A thing can't water. The only thing that is water, is H2O.

Also, no -- it will not survive atmospheric re-entry. The atmosphere see to that. The heat of re-entry exceeds the temperature of Venus by *THOUSANDS OF DEGREES*.... It will not survive in 1 piece. This isn't a matter of atmospheric pressure, nor is this a matter of G-shock. It's plasma; it'll be in an envelope of super-heated plasma. Why do you think they can't use the radios on the Shuttle during re-entry? High energy plasma -- at THOUSANDS OF DEGREES.... Sheesh.

'"As this is a lander that was designed to survive passage through the Venus atmosphere, it is possible that it will survive reentry through the Earth atmosphere intact, and impact intact," Langbroek wrote in a blog update"'

Uh, no.

1) High-energy plasma at 3,200 K upon re-entry. This occurs for 25 minutes or so. This is why Columbia became ... a large number of pieces of wreckage strewn across multiple US states.
2) Venera probes use drag-parachutes to reduce velocity to the point that they can survive entry into the atmosphere of Venus. But, this was built by the Soviet union -- it didn't get out of low Earth orbit. Do you think that parachute functions? It doesn't, it won't.
3) The reasons cited for it 'surviving' re-entry are ... G-forces and atmospheric pressure. None of those address the fact that, though the surface of Venus is ~= 737K ( https://en.wikipedia.org/wiki/... ), you'll notice that the surface temperature of Venus is 2,463 kelvin 'colder' than atmospheric re-entry. What material do you think the probe is made of? Unobtanium?

Ridiculous. It will not survive atmospheric re-entry. it will not be 'a single piece' when it (or most of it, the parts that weren't vaporized by high-energy plasma), gets to sea-level.

I have a slightly different view of this history. Instead of: "The history here is that this project was very popular on cloud providers (e.g. AWS calls their offering "Elasticache") and the original authors got pissy that they were being cut out of whatever money was being paid for using their free software. So they changed the license and here we are.", I would say: "... and the original investors got pissy that they were being cut out of whatever money was being paid for using the free software in which they invested, although 70% of it was written by others. So they changed the license, they disbanded the Core Team after the original developer left, and here we are."

Redis was not written by Redis Ltd (the company). It was originally written and released more than 15 years ago by Salvatore Sanfilippo (a.k.a. antirez) who was soon joined by a community of developers who loved this open source in-memory database and started contributing to it. The project was sponsored by VMWare/Pivotal for a while, but in 2015 it was bought by a company that had renamed itself Redis Labs (originally Garantia Data). Under the new ownership, Redis continued being open source but in 2018 some optional modules were converted to the proprietary SSPL license. This caused some controversy but the company promised that the core of Redis would always remain free and open source. This worked for a few years and this even survived the departure of the original developer. The Redis project continued being developed by a community led by a Core Team of developers coming from various companies (the main ones being Madelyn Olson from AWS and Zhao Zhao from Alibaba Cloud).

But last year, things changed even more. The company that had renamed itself again from Redis Labs to Redis Ltd decided to break their 2018 promise and announced that they would release the next version of Redis under a proprietary license. They also decided to disband the Core Team and take complete control over the core of Redis. The former members of the Core Team left the Redis project and moved to the fork that eventually became Valkey. According to Madelyn Olson, 70% of the Redis code was written by people outside Redis Ltd, so this story is rather different from some other projects in which the original developers wanted to stop the evil cloud hyperscalers who were profiting from their code without giving anything back. In the case of Redis, some of the core code was actually written by people paid by those could companies and only a minority of the code was written by Redis Ltd.

Perhaps they should have asked the judges if they wanted to be fed what the plaintiff feeds to dogs. The implications are horrific for any form of credibility.

That person is an idiot. They deserve what they get.

There's always "powershell.exe -command ..." to get PowerShell to download an .exe from a web server and run it.

"PC" meant "primary cassette", the main paper tray of HP printers of the time. Other paper trays connected would say other things there when out of paper. "Letter" is the paper size.

Nope. That's why I changed all my players to BlueOS.

Given that humans didn't have microplastics in the environment of the past? Their hypothesis is that you have to prove they aren't doing harm (maybe they benefit). The null hypothesis is that no microplastics is the base case; and a demonstration of safety of introducing microplastics is required. The same procedure for making a drug for human use.

This is anti-science flim-flam bullshit. See also: cigarette companies saying no link to lung cancer -- and also, smoking is actually healthy.

Don't be taken in by the same lies as earlier generations.