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
The monospace code stack currently uses Cascadia Code on modern Windows, which includes somewhat controversial ligatures for sequences like != and !== that don't directly represent the underlying characters. Some people like them but I'm wary of forcing them on all readers of a website regardless of their preference. AFAICT it's also the only font in the stack which features coding ligatures, making it inconsistent with the rest.
Windows also includes Cascadia Mono, which is the same font but without ligatures. Might it be worth making Mono the default, with a footnote pointing out the alternative Code, or vice versa?
The text was updated successfully, but these errors were encountered:
The monospace code stack currently uses Cascadia Code on modern Windows, which includes somewhat controversial ligatures for sequences like
!=
and!==
that don't directly represent the underlying characters. Some people like them but I'm wary of forcing them on all readers of a website regardless of their preference. AFAICT it's also the only font in the stack which features coding ligatures, making it inconsistent with the rest.Windows also includes Cascadia Mono, which is the same font but without ligatures. Might it be worth making Mono the default, with a footnote pointing out the alternative Code, or vice versa?
The text was updated successfully, but these errors were encountered: