Syntax highlighting happens on the client side currently. This means that if we add too many different languages, the size of the distributable gets very large and can make the site slower to load. While any one language might be a good addition, we get enough language requests that if we added them all, we'd have a long list and a big problem.

I've talked with Ben Kelly, one of our Stacks team developers and, while he really hopes to eventually support nearly all languages that highlight.js supports, it'll require some big changes to how we process syntax highlighting and we don't know when we'll be able to get this work scheduled.

In the nearer term, we're actively planning how we can expand support for really popular, newer languages that we're not currently offering syntax highlighting for.

For these reasons, I'm marking this post status-deferred and we'll update the answer should anything change in the future.

Syntax highlighting happens on the client side currently. This means that if we add too many different languages, the size of the distributable gets very large and can make the site slower to load. While any one language might be a good addition, we get enough language requests that if we added them all, we'd have a long list and a big problem.

I've talked with Ben Kelly, one of our Stacks team developers and, while he really hopes to eventually support nearly all languages that highlight.js supports, it'll require some big changes to how we process syntax highlighting and we don't know when we'll be able to get this work scheduled.

In the nearer term, we're actively planning how we can expand support for really popular, newer languages that we're not currently offering syntax highlighting for.

For these reasons, I'm marking this post status-deferred and we'll update the answer should anything change in the future.