I can make a hat, or a brooch, or a pterodactyl…

It’s too much of an open question. Like asking what can you make with steel, or stone.

The only real limits are the hardware and your imagination.

Madness

We had a similar stupid issue at my last job. Someone made an edict that all Sha-1 and md5 references in the code must be removed for security reasons.

Then why did you post here if you’re not willing to discuss it here? It seems you just want everyone to agree with you. Sorry to disappoint.

I did read it. It’s not that long.

I still don’t know what problem you are trying to resolve that doesn’t already have one or more solutions.

You listed one issue, specific to gaming and cheating, that was simple human error and miscommunication that I don’t believe would be solved by what you are proposing.

What other examples do you have? You seem to be starting with an assumption that everyone knows and agrees what the problem is without truly stating it.

The Linux kernel, and most userspace libraries already have a contract to maintain backwards compatibility. Some developers may choose to ignore this or make mistakes and break this contract. Again I do not believe that adding some new compatibility layer will fix this.

I’m sorry, but your article seems very hand wavy to me and doesn’t have enough detail on how it would work. What you are proposing seems huge. I can’t imagine enough people buying in to the idea to get it off the ground.

At least skip the Reddit link and post the source…

https://parallel-minds0.github.io/An-Open-Letter-on-Linux-Compatibility/

From a quick skim, I think the author doesn’t really know that much about how Linux and its various components and libraries actually work. Though it seems they are loosely proposing somebody new compatibility layer?

And what is this supposed NT compatibility promise?

The Linux kernel has maintained strict backwards compatibility at the user space level for ages.

Individual libraries are versioned and can be kept around for as long as anyone likes.

Package management and dependencies might be a bigger problem, but I would guess a manageable one?

I would say Computer Scientist in place of software engineer.