Not to mention things like the iPad where the keyboard can directly show the symbols based on context. We already have playgrounds on iOS, and I for one will be programming on my iPad often once that becomes a possibility.
Also, there are UI things that can be added to Xcode to easily type emoji’s and other symbols. If I could type ‘``dog`’ or something like that and get the dog emoji, why shouldn’t I use it? That was, after all, one of the initial promises of Swift.
> On Oct 19, 2016, at 12:29 PM, Jonathan S. Shapiro via swift-evolution <swift-evolution at swift.org <https://lists.swift.org/mailman/listinfo/swift-evolution>> wrote:
> On Wed, Oct 19, 2016 at 6:41 AM, Matthew Johnson via swift-evolution <swift-evolution at swift.org <https://lists.swift.org/mailman/listinfo/swift-evolution> <mailto:swift-evolution at swift.org <https://lists.swift.org/mailman/listinfo/swift-evolution>>> wrote:
> IMO, the best argument against using unicode symbols for operators defined by mathematics is that they are currently difficult to type.
> And there is no realistic hope of that changing. This issue is so compelling that C and C++ introduced standardized text-ascii alternatives for the punctuation operators to relieve stress on non-english keyboard users.
Wait, what? They’re only hard to type because people don’t seem to realize they can make their own keyboard layouts to use while they’re waiting for the USB Consortium to notice that it’s not the '80s anymore and update the class driver spec to allow keyboards to directly type unicode characters.
For macOS, I use Ukelele (http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=ukelele <http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=ukelele>). I don’t know what tools there are for Windows or Linux, but I’d be *shocked* if they didn’t exist.