ricecake

Changes the torque and the application of said torque for each bolt. As in "tool head has 5° of give until in place, then in ramps torque to 5nM over half a second, and holds for 1 second and then ramps to zero over .1 seconds", and then something different for the next bolt. Then it logs that it did this for each bolt.
The tool can also be used to measure and correct the bolts as part of an inspection phase, and log the results of that inspection.
Finally, it tracks usage of the tool and can log that it needs maintenance or isn't working correctly even if it's just a subtle failure.

Oh, it's definitely interesting.
I think people here just got rubbed the wrong way because these articles often make it seem like Roman concrete is better than ours, rather than "look what they accidentally did occasionally".

We can make self healing concrete today, we just usually opt not to, because the downsides or unpredictable nature makes it unsuitable for the significant cost increase.
The phrase "the bridge is infested with bacterial spore colonies" isn't one that makes engineers happy.

We mostly know how they made theirs, and could make our own version of it, but we optimize for different things.
The Romans optimized for "that's cement and it works well", because they didn't have anything close to the level of chemical understanding we do now.
We optimize for strength and predictability. Ours can hold a higher load and will likely need repairing about when we predict.

Roman concrete can sometimes, in certain circumstances and with variable effectiveness, repair certain types of damage by chemically interacting with the environment. So maybe it crumbles in a decade or maybe it lasts a millennium.

Article basically points at some researchers who are looking to see if they can bring that healing capability to modern concrete in a predictable and more versatile fashion.

Er, selinux was released nearly a decade before Windows 7, and was integrated into mainline just a few years later, even before vista added UAC.

Big difference between "not available" and "often not enabled".

Yes, but that's the case regardless. My message going through has always depended on someone else's cell towers, all the random routers and switches in between, and the other person's device.
My server likely has worse uptime, and if I'm hosting from home it probably has more hops to transit through it.

The results were fine, but the work to get there was quite bad quite often.

UX polish is one of those things that just isn't as fun to do, and isn't as rewarding either. So pumping a bunch of money into it is going to go a long way towards making all the other hard work come out better.

This is already a thing we need to deal with, security wise. An application making use of encryption doesn't know the condition of what it views as ram, and it could very well be transferred to a durable medium due to memory pressure. Same thing with hibernation as opposed to suspension.

Depending on your application and how sensitive it is, there are different steps you can take to deal with stuff like that.

Statistically you're unlikely to have lasting issues as a result of getting them removed. It's a very common outpatient procedure.

When you go in, they'll likely give you nitrous oxide, which will make you relax a little, and they'll let you sit and breathe it for a few minutes. I'd recommend bringing headphones since some nice music will help.
Then they'll give you an IV that will make you not worry and likely barely remember what comes next. Basically a big dose of super valium.
Then they'll give you some pain killers and local anesthetic and remove the teeth.

Your memory and orientation will start to come back in about an hour, by which time hopefully the person who transported you has gotten you home. You will not be able to care for yourself during the intervening time. You will be uncoordinated and of poor judgement.

When you get home it's best to try to sleep until the meds that the dentist gave you wear off, or just watch TV. Take ibuprofen or Tylenol mostly, but an occasional opioid will help since there is some pain that the antiinflammatories don't help with as much, although they take care of most of it.
Soft foods for a few days, and no straws.

All in all, you should be back to normal within two weeks, and you'll get to feel nice and excited to eat something crunchy or chewy.

If you've had pain associated with your wisdom teeth, I'd recommend going forward as scheduled. The pain may have gone away temporarily, but it'll come back.
I let mine go too long, and one of the wisdom teeth cracked open because of pressure on it from another tooth, which also damaged that tooth which was fortunately able to be repaired.
The pain from waiting for outstripped the discomfort of the procedure.

In this case the helicopter came because they blocked a major highway.

A helicopter coordinating police movements during civil unrest is pretty standard anyplace that can afford helicopters. That's definitely not just an American thing.
Do you think France is eschewing using helicopters to coordinate police movements with their current unrest?

Is it? All I saw was a helicopter with decent optics, but nothing particularly special, and cops talking on low bandwidth radios.

Even when we get to actual behavior, we see the cops starting with the assumption that they'll be just telling people to leave and planning routes to do so, before it changes to arresting people for blocking a freeway. They make sure people are notified that they're under arrest early, and the make sure they have adequate transportation before they begin the arrest process.

Like, there's plenty of scary and shitty things cops do, but this wasn't one of them.

To me it's important to ask "what problem is it solving", and "how did we solve that problem in the past", and "what does it cost".
Crypto currency solves the problem of spending being tracked by a third party. We used to handle this by giving each other paper. The new way involves more time, and a stupendous amount of wasted electricity.
Nfts solve the problem of owning a digital asset. We used to solve this by writing down who owned it. The cost is a longer time investment, and a stupendous amount of wasted electricity.
Generative AI is solving the problem of creative content being hard to produce, and expensive. We used to solve this problem by paying people to make things for us, and not making things if you don't have money. The cost is pissing off creatives.

The first two feel like cases where the previous solution wasn't really bad, and so the cost isn't worth it.

The generative AI case feels mixed, because pissing off creatives to make more profit feels shitty, but lowering barriers to entry to creativity doesn't.

It might have none, or it might turn out to have some unexpected application way down the line.

The fun part about basic mathematics research is that sometimes it suddenly just perfectly solves some other problem hundreds of years later.

Like that time in the 1800s a guy figured out a solution to a 350 year old problem, and then in the 90s we realized that it was a description of particle physics and all the math had just been sitting there waiting.