not producing precisely what the content creator wanted, so it favors people who don’t really have an opinion on the specifics

That's an interesting point that I haven't run into elsewhere!

All C code can be compiled with the C++ compiler, though there's some nuance (if you don't mark the C code as C, it behaves slightly differently which could mean it doesn't work).

C++ adds a bunch of language features (object-oriented programming and templates are two massive ones). This can make it easier to describe a concept in C++ than in C. But it also enables a lot of unneeded complexity (if C++ wasn't the best fit, or if the programmers aren't excellent) and the compiler is slower because of all the extra stuff. And the resulting binaries are much bigger. And it's harder to port the C++ compiler to other platforms. There's still plenty of situations where it makes more sense to use C over C++.

2d->3d -- bigger number

c -> c++ -- two extra plusses (and plus already means extra!)

games -> epic games -- it's got "epic" in the name

You don't have to be a genus to see these are all better!

I really appreciated your explanation; it was clear and I think you're correct. It's disappointing that Linus is either unaware of it or doesn't care about deterministic results.

Is that what Linus is talking about in the OP? I was sure this was about code-generation. If he's talking about images and recording the metadata then I agree with you.

You make a good point about capability. However, I'm trying to say that in practical capability, I do know exactly what compiler flags were enabled (it's whatever the Makefile passed, which is whatever configure determined, the whole thing is checked in as source code), but the exact model+seed isn't being recorded for this Linux changes.

To make the compiler analogy, we should be saving model, seed, prompt, etc and then the LLM output becomes the equivalent of the compiled code. I think that's an extremely defensible argument, while "bet you can't write assembly!" is not.

I'm kind of gobsmacked by this. I've heard younger developers compare LLM with compiler and chalked it up to ignorance, but I don't get what this is.

Can I write code in assembly? Yes. Of course. It's true that I never do it, but if there was a rule that you needed to write some assembly now and then to certify as a kernel developer I don't see how it would be any kind of impediment.

Comparing more directly: if you hand me a compiled binary and the source code and ask "why is the bit at address 0xXXXXXXXXX a 0?" I can, with 100% certainty, answer that. Probably in less than a day of effort. If I ask "why did the LLM output "for" as the XXXXth word of its utterance, can Linus say why?

And "can you write a good commit message without an editor?" Uhhh? At least when I was in school, this was something people did for fun/messing around. I still do cat > somefile when I need to put some quick text together. In fact, Claude will sometimes write a Git commit by cat-ing into a file--which it's doing because there's so many online examples of this. Fucking weird things for Linus to pick. Makes me think his brain's rotted.

Here's a starting-point: https://en.wikipedia.org/wiki/Large_language_model

Endless Sky is excellent. It captures all the enjoyment of the EV games, and its free for everyone.

Your controller looks great. Just the kind of thing an independent ES pilot would be flying with!

Pretty neat that the advertisement has "or buy our materials and make them yourself!" in two different places.

to say that he was executed for breaching UN resolutions is simply factually false

Yeah, this part is nonsense.

I do think it's fair to say "the US executed him" as a shorthand for "the US hunted him, caught him, turned him over to people who said they would execute him, and then those people executed him".

Yup. I've been in academia and in private business. Academia pays terribly and expects a fuck-ton more work. I'm sure there's places where you can just sleaze by without doing much, but I never saw them. (Which isn't to say that all academic work is good work. I saw people who got far doing poor research, but they were also working very hard at it.)