The fact that it's such an egregious issue (85 minutes for 2000 posts?!) that has been open for 9 months doesn't give me much hope in the development speed of Lektor. This also matches my experience, as I see trivial issues and PRs open for months in Lektor's repo...
The Lektor dev (it wasn't Armin) told me on Gitter that development has stalled a bit, but will hopefully pick up in 2017. I certainly hope so, becaue it's a well-designed site generator.
maybe when community and development speed and extensibility are the main requirements it all leads back to Jekyll :/ if I would be a ruby guy it would be definitely my first choice.
Hugo is the speedy gonzales with easy deployment but lacks good extensibility when you want to go into the code level :(
sorry :D it really depends on your requirements. If Hugo in its current state covers you or if you can live with a light toolchain around Hugo go Hugo (I think many people do not need to touch the go code). There is nobody saying that you cannot write a little python code which is run before/after hugo (actually some people are doing that!). But if you want total control/extensibility with your python code in the page generator the Lektor plugin system will give you more power.
I decided to go with Lektor in the end, since it's much easier to work with and good enough for my purposes for now. Plus, since I'm a Python dev, I can extend it much more easily.
https://github.com/lektor/lektor/issues/180
The fact that it's such an egregious issue (85 minutes for 2000 posts?!) that has been open for 9 months doesn't give me much hope in the development speed of Lektor. This also matches my experience, as I see trivial issues and PRs open for months in Lektor's repo...
The Lektor dev (it wasn't Armin) told me on Gitter that development has stalled a bit, but will hopefully pick up in 2017. I certainly hope so, becaue it's a well-designed site generator.