Java puts strict naming standards on your files to pull that off, although to be fair they are standards you should normally be following anyway. IMO the fast

Java puts strict naming standards on your files to pull that off, although to be fair they are standards you should normally be following anyway. IMO the fast performing code is best in the IDE's compiler, since that is even faster than a build in most cases. Overall I think the .NET whole assembly building is at very least an interesting industry level example of something different that the common per-file build model used.