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
It's absolutely wasteful to use highlight.js in it's current incantation.
users with JavaScript disabled for security/privacy don't get syntax highlighting or rendered LaTeX (or using a TUI/minimal browser because of system requirements)
user data plans and network lag are introduced to get the required tools
CPU time and battery are expended to do all this parsing and repainting
All of these phases slow down the render performance
Why should all users be executing the exact same parsers that produce the same markup at runtime when this should be done statically at build time so nobody has to worry about security, their data plans, or their battery life.
The text was updated successfully, but these errors were encountered:
It's absolutely wasteful to use
highlight.js
in it's current incantation.Why should all users be executing the exact same parsers that produce the same markup at runtime when this should be done statically at build time so nobody has to worry about security, their data plans, or their battery life.
The text was updated successfully, but these errors were encountered: