1. Were the safety guards, which were optional, installed?

2. We know investigators are looking into the computer system, does this mean the computer can also set the switch settings?

If the answers are "no" and "no" respectively, it was likely an accidental bump.

If the answers are "yes" and "no", then one of the pilots lied.

If the answer to the second one is yes, then regardless of the answer to the first, I'd hope the investigation thoroughly checks whether the software can be triggered into doing so through faulty data or the existence of software defects.

I don't want to unsubscribe to this or that.

I want to give natural language filters like "I never want to see a political email again, from anyone"

Or maybe "If they make it sound urgent but it's not urgent at all, don't show it to me and remind me a week before the actual deadline if it's at all important".

As others have said, unsubscribe links often do not work and it's probably all the Gmail feature will use.

LLM crawlers are understandable these days, but who on earth is actively trying to take the FSF down?

A bunch of heathen VIM users trying to stop people from accessing EMACS? What the heck?

Let's say you actually managed to take down the FSF website. Who would even notice or care? How would that help your hacker rep in any way? You'd be a laughingstock for making the attempt.

Agree with all your points.

It's possible I might have missed these, but they're also major considerations with COVID:

1. It causes scarring of tissue, especially heart tissue. That's why COVID sufferers often had severe blood clots in their bloodstream. Scarring of the heart increases risk of heart attacks, but there's obviously not much data on by how much, from COVID. Yet.

2. It causes brain damage in all who have been infected. Again, we have very little idea of how much, but from what I've read, there may be an increased risk of strokes in later life.

3. Viral load is known to cause fossil viruses in DNA to reactivate silenced portions. This can lead to cancer. Viral load has also been linked to multiple sclerosis and chronic fatigue, but it's possible COVID was the wrong sort of virus. These things can take decades to develop.

I would expect a drop in life expectancy, sometimes in the 2040-2050 timeframe, from life-shortening damage from COVID, but the probability depends on how much damage even mild sufferers sustained and what medicine can do to mitigate it by then. The first, as far as I know, has not been looked at nearly as much as long COVID has - which is fair. The second is obviously unknowable.

I'm hoping I'm being overly anxious, my worry is that I might not be anxious enough.

Yes AI may be generating a lot of code now. But you need someone to find where what was generated was weak, or inefficient.

Over time the quality of generated stuff will improve, but since so many companies are generating a lot of code today that is a LOT of technical debt that is building up rapidly.

I especially agree that now is the time to round out your skills - as stated, study design, study platforms you connect to but do not develop on. Study AI tools, find out when they work for things you work on and know well - and when they do not.

Good luck out there everyone!

Man this Superman marketing budget must be crazy. Or possibly it's an F4 promo? But then it would be a little late.

But the super secret code names apple has been stowing away, will bring them glory! Glory and Fame! All shall bow to the might of snapchat and their secret code names for things that no one wants!

My latest vaccine shots had the 6G upgrade, to take advantage of the higher-speed web access when the networks upgrade, but if they're selling those frequencies to high-power carriers, then I won't be able to walk into any area that handles AT&T or Verizon. :P

Seriously, this will totally wreck the 6G/WiFi6 specification, utterly ruin the planned 7G/WiFi7 update, and cause no end of problems to those already using WiFi6 equipment - basically, people with working gear may well find their hardware simply no longer operates, which is really NOT what no vendor or customer wants to hear. Vendors with existing gear will need to do a recall, which won't be popular, and the replacement products simply aren't going to do even a fraction as well as the customers were promised - which, again, won't go down well. And it won't be the politicians who get the blame, despite it being the politicians who are at fault.

Given the state of the laws on Technology, we should see that come to pass where Anonymity is legally banned. While other smaller companies may be able to set up shop, or you can deploy your own VPN somehow without tracing it to yourself, any public for profits will have to comply with the law. So this is a neat tech implementation that may not end up mattering much in the near future.

Kind of funny to see how AI's improve by re-writing themselves, following immediately a story from earlier today about humans being driven into psychosis by AI's.

This claims it uses empirical evidence to judge improvement but why would an AI not be as much a cheerleader for anything it does as it is for any human?

Just another example of why having watched Star Wars is such an important aspect of lifetime mental health...

When exploring deep philosophy with an AI and ending up down rabbit holes, Yoda's warning was always there to moderate you ahead of time...

Luke: "What's in there?"
Yoda: "Only what you take with you".

Other than the SwiftUI framework, approximately everything that's in Swift was in Objective-C 5â"10 years ago.

Not the concurrency framework (GCD is not the same), SwiftUI doesn't have things like Swift structs, only supports integers enums, Generics, no guard statement. Also finer grained access control.

Mind you they have improved Objective-C over the years by bringing in some Swift features as Swift improved! Like nullability annotations.

I still do like Objective-C as a language but even with Swifts advanced areas and quirks, I still think it's more straightforward than Objective-C for newer users. And I think finally with the new beta version of Swift they have a concurrency model that is strong but also friendly enough for people to work with.

J2ME suuuuccccked. Google did the right thing to it. Meego was a nice beautiful UI on a lake of shit beneath it tied to boat anchor hardware, as hard as it is to accept. From talking with devs that created it, it was a nightmare inside created by various mixing of older distros and coding paradigms.

Geezus Krust, slashdotters love C. Leave it for lilnux kernel and your device drivers, keep it out of phone development, you'll make everything worse.

Only a fool or an expert would write a c backend to an app. And there aren't many experts...