On a closer read of this proposal, I believe the key is in these lines: A module is a package describing a library • Interface of the library (API)

On a closer read of this proposal, I believe the key is in these lines: A module is a package describing a library • Interface of the library (API) • Implementation of the library That is, this will never replace the way you write applications. All it means is that there is an alternative way to depend on 3rd party libraries that improves compile time if that library supports it. If you're writing a library, you may choose to support it. I agree, if this was a proposal to remove #include, #define and #if, it would be doomed as a non-starter; that's simply not practical. I don't believe that it is though. Edit: Yes, I am saying that I believe this proposal is only practical for getting rid of public header files, the sort you'd find in /include/, and will have no impact on header files inside a single code base.