This issue alone has impacted the Bootstrap base theme the most. A huge effort was put in to help organize and optimize the Bootstrap base theme.
The file structure has been completely re-organized. While the base theme may now contain a lot of extra files (seemingly unnecessary at first), it was done in an effort to leverage Drupal's theme system architecture.
By leveraging Drupal's ability to include files only when a specific theme hook is implemented, we have reduced the PHP memory footprint of the Bootstrap base theme. Another advantage to implementing this automated file structure is: organization. We are now organizing [pre]process functions, theme function and template implementations in an easy to find folder structure. How that file structure is determined depends on module they originated from.
Over time this base theme has grown exponentially and this type of change will help ensure it's future growth, without sacrificing performance.
Sub-themes, you can rest assured that you inherit this performance enhancement automatically. There is no need to structure your sub-theme this way, so feel free to continue using your existing workflow :)
Last updated: October 1, 2013 - 00:11
Official release from tag: