yhvrdeath to all ligatures
Xenotime | Science/Coding VTuber@yhvr ok ligatures in text im not a huge fan of but code ligatures are beautiful
Григорий КлюшниковXenotime, they are beautiful to look at but a torture to actually work with. As in, you have to always keep in mind that the "greater or equal" ligature is actually two characters that you don't see but that you can edit. I'm okay with code ligatures that faithfully represent the sequence of characters that comprise them though.
@yhvr @grishka I get that, I discovered these when seeing a normal not-equals sign in my text file, being confused, clicking and having my cursor in the middle and going whaaaaaaaaaaaaaaaat theeeee
But it’s the kind of thing where you only need to figure it out once and once you do it’s fine, and it’s not that hard to figure it out once
Just my opinion but maybe the confusion factor is really just if you haven’t seen them before or in ages so it’s well worth it to me
Xenotime | Science/Coding VTuber, welllll the problem is that you still have to keep in the back of your head that that "not equals" ligature actually has a ! in it that you don't see. If you want to turn it into ==, you have to do this extra mental work of imagining the characters that are there in the file but not there on the screen to replace the ! with a =.
In your example, the <> ++ and -> are fine because they don't hide anything. I only know one example of similar hiding of underlying characters in natural languages — in Arabic, there's this "la" ligature that looks like neither the "l" nor the "a". Fonts implement it as an actual ligature, it works exactly like those >= and != except RTL.