You might have a good case, but the way you present it makes it seem very disconnected from real-world development. Equating the most trivial kind of errors (w

You might have a good case, but the way you present it makes it seem very disconnected from real-world development. Equating the most trivial kind of errors (which are caught by the compiler anyway) with "all sources of bugs" ignores the kind of bugs which are actually hard to prevent and might slip into production. But these are the kind of bugs developers are actually concerned about. Preventing editors from saving a file with a typo in it is a solution to a non-problem. If you want to interest people in these ideas, you should show how it can solve real problems.