| >In fact , our visual system has been trained to instantly recognize a!=b in code Citation needed. >confusing = with == will lead to lots of errors etc This is more about NOT confusing == with = -- and several similar characters than the opposite. Sounds like you have thought of all kinds of arguments to not actually try it and see whether it's any good in practice -- which is how anything should be judged (unless it involves some huge risk). In other words, a priori rationalization. >If I get used to this font on my machine, i will have a real problem when parsing code in another terminal/editor. The above argument advices to forever stick to a lowest common denominator coding toolset, lest one has to ever try to work in other environment. How about maximizing the performance one gets from their own, and most frequently used, environment, instead of "what-ifing" for foreign systems they might have to use 1/10 of the time or less? Plus, having a tool at our disposal and getting used to it doesn't mean we can't also do without if needed. Especially if it's a small improvement, like the one proposed by the ligatures here, and not some totally different notion that we can't ever go back to how it was without it... |
So the onus is on promoter - to show benefits.
The onus is _not_ on everyone in the world to show whether the idea works or not.