It would be nice to see the concept of Runtime Packages taken to the next level. Currently, as mentioned here https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-creating-runtime-packages#create-a-new-extension-version-and-runtime-package, you need a runtime package for each Cumulative Update version and localisation if you don't want to include your source code. These runtime packages may or may not work on newer Business Central Version. For example, these runtime packages usually don't work with the next major and minor pipelines when you try to publish them to the docker container (sometimes you can't publish. Sometimes you can, but you get a runtime error in the tests).

Instead of producing C# intermediate code or the compiled assemblies - I'm not sure how this works internally - how about ether encrypting the code with a key that only Business Central knows, or obfuscating the code. For all I care, as an opt-in in resourceExposurePolicy. I would nag the ISVs where I need this new version.

The aim should be to make the runtime packages work for newer versions, if no breaking changes prevent this. It would also be nice to also remove the step of creating a docker container to create a runtime package. It takes a lot of time and resources to build a runtime package for each cumulative update version and localisation. Without Docker containers, this would be even better.