Ligatures in programming fonts:
hell no https://practicaltypography.com/ligatures-in-programming-fonts-hell-no.html
@veer66 Also I wouldn't be surprised if in the future Conceal plus treesitter would allow better, semantic visual replacement of characters solving one of article author's gripes about false positives if you want the LOOK of Unicode in your editor, but need ASCII on the output end.
@veer66 Languages that have decent Unicode support in one way or another: PureScript, Haskell, Dhall, Julia
@veer66 Haskell strings are notoriously bad, like Erlang ... PureScript modernizes a lot of "issues" of Haskell, but doesn't have near the community size and package support (yet)
@veer66 in my $XDG_CONFIG_HOME/nvim/init.vim I added some extras
" commonly used in Dhall, PureScript, & Haskell
digraph ~> 8605 " ↝
digraph O+ 10753 " ⨁
digraph ^^ 10835 " ⩓
digraph // 11005 " ⫽
@veer66 I tend to find it pleasant. It's direct and unambiguous. You can use to match the math-y symbols of a paper so the two are easier to follow.
@veer66 Now if only there was Thai and Lao support... it's a shame abugidas & abjads don't play well with monospaced fonts
@toastal I'm rare because my programming is for processing Thai text. 🙄
@veer66 You can have both. No need to strictly pick. ANSI has obvious advantages in keyboard input, but I don't think it helps readability.
I believe someone new to programming would understand ∘ is a better symbol for compose than . or <<< or <<. The math textbook they had in school showed f ∘ g = f(g(x)).
This audience does matter.
@veer66 Interesting #PureScript fact: almost everything must start with a character from a character from a bicameral script (Latin, Cyrillic, Greek, Coptic, Armenian, Adlam, Warang Citi, Cherokee, Garay, and Osage) because the case determines if it's a type, variable, etc., but you can use all of these scripts.
@veer66 Whatever Haskell module they are using for the parser requires the script have both upper and lower cases