It looks like the issue of typing unicode symbols was solved much sooner than any of us were predicting…
Thanks,
Jon
Swift as a language extends beyond Apple's platform and Unicode symbology.
-- E
···
On Oct 27, 2016, at 11:46 AM, Jonathan Hull via swift-evolution <swift-evolution@swift.org> wrote:
It looks like the issue of typing unicode symbols was solved much sooner than any of us were predicting…
Thanks,
Jon
True, but that doesn’t mean we have to resign ourselves the lowest common denominator. We need a way to operate with older systems, but we also want to embrace what has been made possible now. Within a few years, it is quite likely that this technology will be common both across Apple’s lineup and that of competitors.
For example, it is much more realistic to have something like the union operator in the standard library now, because those with the TouchBar can (theoretically) easily type it, and those of us without a TouchBar can continue to use the much less concise formUnion.
I also have several ideas on how to make typing these things easier sans-touchbar. There are lots of potential UI which make it not-too-difficult, we have just have to have a reason to do them.
Let’s move forward and develop something for the modern age instead of limiting ourselves to the state of the art from the 1970s (e.g. I personally find it barbaric that we have to type an arrow ‘<=' instead of ‘≤’). Sure, we have to make sure there is a bridge for those who aren’t on the bleeding edge, but that doesn’t mean we shouldn’t push forward at all.
Thanks,
Jon
···
On Oct 28, 2016, at 3:13 PM, Erica Sadun <erica@ericasadun.com> wrote:
On Oct 27, 2016, at 11:46 AM, Jonathan Hull via swift-evolution <swift-evolution@swift.org> wrote:
It looks like the issue of typing unicode symbols was solved much sooner than any of us were predicting…
Thanks,
JonSwift as a language extends beyond Apple's platform and Unicode symbology.
-- E