Just makes sense that they would put the "heavy hitters" on feature development, not backporting security patches.

command.com also has variables. Syntax not so great though.

The weird casing seems to be a minimum accepted prefix for the keywords.

Usually the desire is for some of the metadata processing to be reusable between the encrypted and non encrypted formats ("like a regular file, just this data is encrypted"). This is also why eg. Zip files are encrypted per entry, not globally.

Since the kind of data people want available may differ for each file format, here we are.

The comments and field names in the source code are all Dutch. Expected I guess given the context, just wonder if that was generated or if it was derived from the compiled code. I know Delphi has RTTI info.

The comments are AI-generated, but the original class names were all in Dutch, so I told it to make the rest of the code match :)

Ukraine used to be the USSR too.

Well they could output plan.md files that are architecture independent first. Then we can commit those, and only generate the final machine code on demand.

That's a very good way to ensure your software is not reproducible.

People don't trust other people making little changes to existing software, who will ever be ok with rebuilding it from scratch?

We could call the final phase a coLLMpiler for good measure.

Having the debits move to the new IBAN automatically had to be mandated and built. It doesn't just happen. In markets with large incumbent banks they have no incentive whatsoever to make switching easy.

They're selling whatever the "Certificate of Embodied Production" is. You can tell the article veers towards the abstract around there.