I argue that complexity is good. Complicated things though, those are bad. The world is complex, and we must deal with it. But as long as we organize our work and don't let it spiral into being complicated, we'll be fine.

very hard for most developers (maybe even you) to tell the difference

"be organized" is, of course, good advice

Line 427 makes this game NSFW !

Which file? Now I'm curious :)

The second link in the comment, the devlog.

Ahhh ok I was thinking it was in the actual code. Because the devlog wouldn't be part of the game. Thinking too literally :)

This is dedicated to the people in the other thread about forbidding swearwords in code.

Take this!

The repository metadata absolutely should own the commit information.

Diff files are there to represent a delta state of the repository, a difference between a range of changes. Those may be one or more commits, or one more changes across individual files (not all SCMs manage state in terms of atomic commits). File changes, file attribute changes, SCM-specific metadata changes, and commit history information.

That delta state should be able to be applied to another tree in order to get the same end result. This is what diff files are ultimately there for.

Git diffs do this today, and they do it well (but they're pretty Git-specific). Many SCMs (and there are a lot of them) don't include a format on that level, or a format at all. Hence DiffX.

I think there's a confusion here between diffs and patches. I would call the thing you're describing a patch, not a diff, and then everything makes much more sense.

(This is not helped by the fact that diffs often come with a .patch file extension… or that the "patch" tool processes diffs…)

Or anyway the nomenclature really sucks in this field. I guess I have no clue whether I have a minority view here.

Yeah the nomenclature sucks.

When talking about the file, the two terms are often used interchangeably (and are usually a .diff or a .patch extension).

For fun, the GNU Patch manpage says:

"NAME: patch - apply a diff file to an original"

followed by:

"patch takes a patch file patchfile containing ..."

"patch tries to skip any leading garbage, apply the diff, and then ..."

In short, sometimes the AI doesn't do what you tell it to. More at 11

The only real solution to this is world-wide wealth taxing. We have enough productivity to support old age, even as said old age cohorts grow ever larger.

Is this a psyop to check how HN readers will react to this insanity ? This could be a simple script. It should be a simple script. Please update us when this fails :)

psyop is working. i am seriously considering quitting my 2 decade coding career that I very much loved before this AI insanity. We have mandate at work that all code must now be generated by AI in first iteration.

I am going to open a Montessori school in India with my wife.

No need to make it a percentage ; charge $1 and the spammers will stop extremely quickly, since none of their reports are valid.

But I do think established individual and institutes should have free access ; leave a choice between going through an identification process and paying the fee. If it's such a big problem that you REALLY need to do something ; otherwise just keep marking as spam.

This is just minesweeper ?

Ah yes, completely unfounded behavioral "science" to explain a modern thing. My favorite.

>ChatGPT’s default personality deeply affects the way you experience and trust it.

An AI company openly talking about "trusting" an LLM really gives me the ick.

How are they going to make money off of it if you don't trust it?