Personally, I used Jekyll for a while before switching to a simple Makefile based approach. I write everything in Markdown, which gets compiled via Pandoc, concatenated with a header and footer. I also recently started using pygments to generate colorized inline HTML to syntax highlight code blocks. If anyone is interested, I wrote up the process[1], although I have not updated the post with the pygments script yet.…
Fellow Jekyll refugee here. I also switched to the Makefile SSG approach for the much faster incremental rebuilds. Parallel speedup with make -j is also nice. My SSG is called tinysite [1] [2]. Templates are jinja2. Posts are written in markdown with Pygments highlighting for fenced code blocks. Posts also have JSON frontmatter which can #include other JSON data files, and this is where it gets Make-y: all affected p…
I am honestly surprised to find Python is so slow in terms of start up time. This made me wonder if it was generating / searching for .pyc files, but a quick test revealed this is not the case:
sh-4.3$ ls
nop.py nop.sh
sh-4.3$ hexdump -C nop.py
sh-4.3$ hexdump -C nop.sh
sh-4.3$ time python3 nop.py
real 0m0.064s
user 0m0.048s
sys 0m0.016s
sh-4.3$ time sh nop.sh
real 0m0.002s
user 0m0.002s
sys 0m0.000s
sh-4.3$ python3 -m compileall .
Listing '.'...
Compiling './nop.py'...
sh-4.3$ time python3 nop.py
real 0m0.062s
user 0m0.057s
sys 0m0.004s
sh-4.3$ python3 __pycache__/nop.cpython-35.pyc
sh-4.3$ time python3 __pycache__/nop.cpython-35.pyc
real 0m0.060s
user 0m0.048s
sys 0m0.012s
I would add that shell can be surprisingly fast for certain tasks when used correctly. It's very easy to write slow (ba)sh code though, so most shell scripts wind up being fairly non-performent.Edit: formatting.