No. Blue Origin blew up their only launch pad last night static firing the rocket that detonated. Jeff is likely grounded for a year and this stuff isn't going to happen.

It's certainly possible to translate COBOL source into another computer language of your choice, although I'm not sure LLMs are the best tool for that job. An LLM might be able to give you more readable post-translation source code, but traditional machine translation would give you post-translation source code that works correctly, which is probably more important.

Translation: A company that has the potential to benefit from regulation by squeezing out competitors wants more regulation.

I'm not saying they're not right, just that it seems awfully convenient for a company specializing in pumps that recirculate data center water to want efficiency regulations that would push customers towards their most efficient (and thus presumably most high-margin) pumps.

Instead of having your hot water fan out in a tree, you wire it like a token ring with a return pipe, where each faucet only has a short bit of pipe between it and the ring. Then, you have a pump to circulate hot water through the ring-shaped pipe network. That way, it takes half a second to get hot water instead of half a minute or more.

The IPO is timely for many reasons. One is that falling birds have not yet become a nightly firework display. At 60 going up per week, at some point 60 are coming down per week. Some people are going to really not like that.

Sure. I'd imagine most hardware vendors will want it. I'm just saying that the wording, at least as described in the summary, is... problematic at best.

I wouldn't mind if it were a static image, but it's that Gemini ad that's constantly writing and erasing text. It's definitely cut down how long I stay on the site.

Another way to phrase that would be, "This is why C code is bad, because C programmers are expected to understand the rules about how to not leak memory, but there is no mechanism to enforce that requirement".

... and to their credit, eventually some of them do figure it out, and after that they (mostly) write good C code that doesn't leak. However, that doesn't change the fact that at any given moment there are millions of unseasoned C programmers out there who haven't reached that point yet, and who are nevertheless writing leaky code which gets put into production and causes trouble; and new C programmers appear every day. It's the Eternal September problem, applied to memory management.

So either (a) we ban C programmers from pushing to production until they've had at least 5 years of experience, or (b) we find some means to flag their errors at build-time, or (c) we live with the status quo messiness indefinitely. Linux is going with Rust as their mechanism for implementing plan (b).

If you have access to a God-tier LLM that you can rely on to find every bug, I think that could work.

However, I don't think anyone in the Linux community is ready to trust LLMs to that extent just yet. Not only are they quite fallible, they are also non-deterministic -- so if you ask your favorite LLM to find the bugs in the code, and it doesn't find any, and then you feed it the exact same prompt again, it might find some on its second attempt. So how do you know when to stop re-asking?

LLMs are currently constituted are very useful for finding bugs, but not so useful for guaranteeing that no bugs remain.

You know what improves code quality? Process improvements.

You know what doesn't improve code quality? Telling people that they suck. It's pointless and immature.

They might get a better responsie by requesting $4.99/month to remove the Meta AI slop from their Facebook interface.

Is that a serious question? Even in the late '70s when dinosaurs roamed the earth, the kids were dealing with the technology the parents didn't understand. While that is starting to be inverted (GenX and Millennials seemed to be peak tech-able), many parents still rely on the kids for that sort of thing.

Not really. It's more like requiring all vendors who sell cash registers used in restaurants to support checking photo IDs because some restaurants also serve alcohol.

There's no safe way to prove your age to a website. Any scheme requires trusting some arbitrary third party that could secretly be the government doing timing comparisons between the verification and DNS queries and stuff to unmask anonymous users. At least with operating system or browser vendors, they presumably have a strong commitment to minimizing the risk of someone publicly posting "John Doe just visited sexwithseaturtles.com" or whatever.