It's a conscious decision. After all, why would you reinvent static content serving when Apache, lighttpd, and nginx all have solved this problem extremely well

It's a conscious decision. After all, why would you reinvent static content serving when Apache, lighttpd, and nginx all have solved this problem extremely well? It's much lower overhead to just let the purpose-built native-code server do this instead of bolting it into your web framework.