I shouldn't have to ask it to avoid leaking memory. If I do, it's insufficiently "intelligent" to be trusted with any responsibility.

Whenever I meet a new chatbot, I ask it to "Sort a linked list in C".

If the resulting code leaks memory, I don't trust the bot to write code.

So far, none have earned my trust.

Oh yeah, I remember that scene in "Spaceballs" where they fast-forwarded to 1989 so they could watch "When Harry Met Sally" two years before it actually came out. It was weird.

At that point, the surface of the sun will be beyond Earth's current orbit, and this planet will just be a contaminant in the Sun's composition.

When I look at all the new "apps" I've installed on my phone in the last year, there is only one: the Android port of Balatro.

I suppose AI could give me a fake Balatro, complete with animations and whatnot, but that sounds a lot more resource-intensive than just running reasonably well-written software.

Not really. They're making a co-op squad shooter and calling it "Marathon", because it's the newest trademark Bungie still owned when Sony bought 'em up.

Microsoft/Activision owns Destiny.
Microsoft/343Industries owns Halo.
TakeTwo owns Myth and Oni.

A new Marathon game would resemble Marathon. Halo ODST is the closest thing I've seen to a "new Marathon game" since Marathon Infinity, and I doubt Sony/Bungie's new Marathon will be any closer.

THIS. WSL was designed for surveillance and tracking for marketing purposes. Remember what Monkey Boy said? Developers developers developers!

LoB

And yet none of those were called "Windows Subsystem for _____"
The naming was designed to get hits and to confuse management. Developers were showing management what could be done with Linux for very little cost and getting approval for Linux systems to develop on. Windows Subsystem for Linux makes it sound like they can run Linux and still have access to Windows when it was bass ackwards. IMHO

LoB

hmm, I thought it was because so many Windows devs were installing Linux on the hardware and writing their enterprise apps that way and therefore nothing was traceable. Even running Linux in a virtual machine eliminated Microsoft tracking except for how many times or how long the VM was run. WSL is a whole complete tracking system since it goes into kernel space. Not sure how much tracking WSL2 gives but it's gotta be far more than VMs or directly on the iron.

BTW, I've seen it personally where people will jump through hoops to get a project working within WSL rather than boot a full Linux system on the hardware.
I've also seen many give up and either install another SSD or partition to dual boot.
LoB

It appears that the assets included the existing service contracts with customers, which included these "lifetime" agreements.

The buyer is telling the customers they failed to do due diligence and didn't know what they were buying. At the same time, they're telling investors they *did* do due diligence, and analyzed the business's last few years of financials. These can't both be true.

Screw em, just make VS Code forks act like what the extension needs.

They still want their cake and to eat it too.
LoB

The company is the product. The investors are the customers. Users are fuel.

When creating the Torment Nexus, you gotta' start somewhere.

Even that 2 seater is only going to get a few miles of added range after many hours of sitting in the sun so it's just not worth the effort.
They had to curve the panels to the body shape, wire them in and get that wired into the battery to put charge into it. The weight alone probably negates the added range.

They really need to get off the gimmick train and start showing how they produce those in quantity and at a profit. And to heck with the 400 mile range goal, get something together with 300+ miles of range and get it on the road in numbers. It's already a pretty small battery so it should charge rather quickly.

LoB

Iceweasel was renamed back as Firefox about maybe 10 years ago? When Mozilla decided that finally, Debian was not infringing its trademark by shipping a patched version of Firefox, with patches not prepared by Mozilla.

Also, yes, Firefox in Debian is patched to use the "ca-certificates" package CA store. The funny bit is that this ca-certificate is built using the certificates from ... Firefox ! Though I have no idea if the ca-certificate package is affected by this CA expiration. Anyways, if this is the case, the ca-certificate (not Firefox) will be updated, I guess.