You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.
Right now we’re highlighting Dev.Opera code using Highlight.js. There’s an idea to switch to highlighter marking up code during build process using Pygments.
One thing I noticed when switching from pygments to highlight.js is the significant improvement in processing the blog. When running jekyll, what used to take half a minute to a minute now takes a couple of seconds to run. It looks like pygments is the bottleneck.
My feeling is that we should stick to highlight.js — it makes sense to do this in JS in my opinion, rather than overloading the build process with yet another step.
Right now we’re highlighting Dev.Opera code using Highlight.js. There’s an idea to switch to highlighter marking up code during build process using Pygments.
Switching from pygments to highlight.js
Completely unfair comparison of Javascript syntax highlighters
The text was updated successfully, but these errors were encountered: