Great progress, but the last 10% often takes 50% of the time. In this case, there may be little value to the last bits, but people are going to wait to use the

Great progress, but the last 10% often takes 50% of the time. In this case, there may be little value to the last bits, but people are going to wait to use these until that last bit is done, for fear of what might happen. Which triggers ranting... Q: Why exactly are we stuck targeting cross-platform compatibility for every possible option in every possible tool? A: Because there is no good way to check the impact of removing options or tools, or for migrating clients. By this mechanism, "OS" and "core" features grow forever, and the convention-bound C ABI is, well, as close to forever as we get. Rewriting in Rust does not help that one bit (nor is it supposed to). Has no one written literate ABI interfaces that support static validation and backwards compatibility via shims and automatic migrations? Must scripting be such a drag on progress? We do automatic migrations in databases all the time; we should be able to do it in code.