I think uploading a file, editing it and downloading it back is such an uncommon operation that it makes no sense to apply any smart heuristics.

Routinely with the LLM's one uploads a file and they generate new files.

You, as a maintainer, are free to ignore any such expectations and do what you want. There are no obligations. You only risk disappointing people (or corporations), and losing Github stars. If that leads to unmaintained libraries, that probably means the open-source model doesn't work for this project. And that's fine.

Is the consensus that software will be both developed and tested by machines? Will there still be a human in the loop? I hope at least some testing or approval will still be done by people, otherwise the software we use everyday will become even worse than it is now. Unless we envision that machines will also be the only end users of the software. At that point there hopefully will be an interface that allows for immediate reporting and fixing of defects.

Intelligence has many dimensions.

Smalltalk being so malleable also makes it possible to completely disable source code inspection/execution.

And then what?

Say you made the foreground text color the same as the background text color, so you could no longer see the source code. You can no longer do anything. You can no longer save those changes. And then what?

Better, say you did that in a script file which additionally saved the image, so that image was now unusable. And then what?

The parent comment was talking about a deployed application, and making sure users can't modify the source code.

In that case, your image hopefully was built using source code from a VCS and no such changes will have been applied. This is not so different from building an app by pulling the latest version of the code from Git.

And if you did manage to commit changes that completely mess up your environment, you throw that image away, take a vanilla one and load your source code into it. Again, not so different from using Git.

So "possible to completely disable source code inspection/execution" really doesn't matter.

Plenty opportunity in many languages or systems to lock yourself out by doing something silly.

Perhaps your passport was checked on departure instead of on arrival? At least that's how it worked when taking the Eurostar train.

How do you define cryptography? Let's say my files are written in a format that only my software can read. Is it then illegal to distribute said files?

I define it as anything that even slightly inconveniences the so called "authorities".

I've seen local judges give interviews to television networks about high profile cases where they were nearly foaming at the mouth with rage over end-to-end encryption. Cryptography is whatever causes that.

A 75 year old EU judge will let you know.

Of course, it just becomes the HelperUtilService!

There's a working group dedicated to breathing new life into the standard:

https://qt4cg.org/specifications/xslt-40/Overview.html

Last updated just under a week ago!

An AI-powered editor I assume. Always having to come up with your own thoughts must be tiresome.