Point #2 in the article is all about having your code become too dependent on a particular architecture that was popular at the time, but later goes out of favo

Point #2 in the article is all about having your code become too dependent on a particular architecture that was popular at the time, but later goes out of favor. This has to do with shipping an executable in native code vs shipping something that isn't directly executable, because it's in an intermediate language instead of native code.