11–20 of 30 posts
The ligatures for != -> etc. are a terrible idea, imagine someone reading a programming language tutorial or a snippet and then actually trying to type stuff rather than copy-pasting.
The ligatures for != -> etc. are a terrible idea, imagine someone reading a programming language tutorial or a snippet and then actually trying to type stuff rather than copy-pasting.
This is like saying you shouldn’t render latex. I like my ligature font, it makes nicer to read code for me, not terrible at all. Your programming font is a personal choice, i guess when publishing a tutorial you need to consider which font is appropriate, but that doesn’t make anything terrible.
Earlier quoted context omitted.
I love em. Even when editing
I'm sure they're very rewarding for the author/editor - but the cost is externalized onto unversed readers, this is generally considered bad practice in other areas of programming.
Earlier quoted context omitted.
I'm sure they're very rewarding for the author/editor - but the cost is externalized onto unversed readers, this is generally considered bad practice in other areas of programming.
That's not always true. Reader may decide to not use ligatures and the code will appear as is for them. They're entirely optional.
Earlier quoted context omitted.
This is like saying you shouldn’t render latex. I like my ligature font, it makes nicer to read code for me, not terrible at all. Your programming font is a personal choice, i guess when publishing a tutorial you need to consider which font is appropriate, but that doesn’t make anything terrible.
The opposite really, it's like publishing unrendered latex and have the reader render it in their head or run it through a latex renderrer themselves
-> now needs more internal “rendering” than → does.
Same with ≡ vs ===
Georgian script is missing as always :-( It's really a pain to speak rare language.
Georgian script is missing as always :-( It's really a pain to speak rare language.
It's for programming with English based programming languages, not regular arbitrary text. I do think there should be more language specific programming languages, but since there are not, there is no reason for a programming font to support it.
Earlier quoted context omitted.
It's for programming with English based programming languages, not regular arbitrary text. I do think there should be more language specific programming languages, but since there are not, there is no reason for a programming font to support it.
It's still useful for writing localized string literals and comments.
Earlier quoted context omitted.
The opposite really, it's like publishing unrendered latex and have the reader render it in their head or run it through a latex renderrer themselves
Once I got used to ligatures, they did aid flow for me. -> now needs more internal “rendering” than → does. Same with ≡ vs ===