Guys, I have to tell you that it is neither RapidWeaver to blame for that, nor Stacks plugin. IMHO the speed decrease is based on 3 “trends” RapidWeaver users are going to follow:
- Usage of frameworks (Foundation, Foundry) in favor of old style themes, because we want to have more freedom. Usage of frameworks needs the usage of Stacks Plugin.
- Usage of very impressive and powerful (“heavy”) stacks, which can do a lot, and with this have a lot of settings the Stacks plugin has to parse each time going to preview mode.
- Having more content on each page in order to get a one page design. Less pages, more content on each page, and with this more usage of “heavy” stacks on one page.
Easily you can get over hundreds of “heavy” stacks on one page with this. Each of these stack instances contains hundreds to thousands line of code, which have to be parsed each time. If you combine that with additional pictures, which are contained in the page itself, you find the reason for the slow preview and export.
It isn’t RW to be blamed. It also doesn’t make sense to compare to other web development apps, as they have a completely different generation workflow. We have powerful tools available, but we have to use them wisely.