If you're a maintainer, then I suspect whatever you maintain fucking sucks.

I clearly explained the problem- that the quality of LLM-produced output is a function of the money spent to produce it (generally).
This means that the flood of slop PRs are produced by free-to-cheap models. This is only natural.
People who have no idea what they're doing aren't spending $300 for a large commit. They couldn't be bothered to invest the time in learning to code, they sure as fuck aren't going to invest in this.

Meanwhile, over here in real-life, dealing with real problems on maintained things that don't suck, I've got people making quality commits with LLMs on the daily. But they're part of the team, and they're paying real money for those commits.

In short, I think you're probably just full of shit. If you're not, I feel for whatever the fuck it is you maintain. You can't even apply basic logic to a problem.

As someone who is dealing with this problem, it's not that simple.

The problem with your assessment, is that there is no "the LLM".
LLMs come in a fucking vast spectrum of capabilities.
Put pretty simply, very expensive models do very good.
After very expensive, you get a spectrum from "pretty damn alright", to "outright terrible."

There is no "the LLM."
I can tell from your comment that you're talking out of your ass, and not actually dealing with this problem.

Most humans do. It can be difficult to find it though ;)

Then I hope yours won't be hurt by this little factoid- you're a fucking moron.

As someone who has had several 5-minutes-of-fame CVEs attributed to me, I can assure you that all programmers suck, particularly those wielding C. You're no exception. Neither am I. Despite 20 years of experience, and many hundreds of thousands of lines of C to my name doing work right now around the world.

I'm far from a Rust fanboi- I find the syntax revolting. I know a lot of that is personal taste, and that I'm old, and that's not going to change.
All that being said, it's simply undeniable that all code is going to have bugs, and a language that makes certain classes of bugs impossible is going to have less.

Remember, what matters are facts- not feelings.

Code proofs?
I assume you're referring to formal verification of a particular program.

You can't prove all software. That's literally saying the halting problem is solvable.
Formal verification of all software written would drop the world's aggregate code output to a few lines per day.

Of course programmers should avoid bugs. However, unlike whether any arbitrary program will halt, your statement that any programmer that doesn't isn't is provably false.

Every single thing in this post is wrong.
Well done, sir.

Rust can't save you from bad logic. In fact, in some cases, it may even encourage it with some of its difficult semantics.
That being said, LinuxBugs - CMemBugs + RustBugs < LinuxBugs.

But you can only answer in lisp

small overall difference? complete fucking horse shit.

Opus 4.7 is vastly better than DeepSeek 4.
That being said, DeepSeek 4 is cheaper, and it's open.
Not giving money to Dario is a great reason to burn a little more time using DS.

DS is dumber... like a lot dumber. It'll look at something and tell you, "the problem is X", when it's obviously not X. But if you keep throwing tokens at the problem, it will eventually figure it out.

No.
In one case you have an effective API between the two separate address spaces.
They are not comparable.

I'm not familiar with the exact implementations, but it's actually not hard to imagine a scenario where 1 is needlessly vulnerable, and 1 is not.

For the "secure" model,
What immediately comes to mind is a multi-process design (which I know that Chrome does use, but not to what extent).
The ability to read/decrypt passwords would be kept in a separate process from whatever handled rendering the website and runnings its javascript (since that's the most exposed to security challenges).
The head process would only feed passwords to worker processes when they had a reason to have them.

For the insecure model- single process. Done.
Any compromise (or even the ability to leak locally mapped memory) of the renderer or javascript engine means easy access to all passwords.

Hah, I'd definitely agree it's probably recommended practice by any legitimate (my definition, not the DEAs) practitioner.

The normal rules require an in-person visit, but the post-COVID rules (extended again this year) allow for telehealth "visits", even to receive scheduled drugs- at least that's what I've been led to believe.

That's been my overall take of the situation with the guys I know.

I have no doubt there's a legitimate practice in there for people with legitimate problems. Ketamine is serious shit. You can really fuck yourself up with it, permanently, if you misuse it. Actual doctor supervision seems like a good idea if you give a fuck about your life.

Ya, absolutely. IVs are almost guaranteed to be administered by a physician.

Home care (for us normies) are tabs and lozenges. I have several friends doing it completely legally (Telehealth is still a wild concept to me- who'd have thought you could ship Schedule 3 drugs to some guys house legally). It's all the rage, currently.
I've even heard tell of nasal sprays becoming a thing for it.

What I said was entirely accurate based upon my reading of the ambiguity.
Any "authoritative sound" you gleaned from my words is a psychological dysfunction of yours, not a problem with my words.

An assertion was made, it was interpreted, and it was responded to- correctly- in kind.
They meant something else, which invalidated the response. It's that simple.

So yes, you are the fucking stupid one.