http://projectfortress.sun.com/Projects/Community/wiki/MathS... http://projectfortress.sun.com/Projects/Community/wiki/Fortr...
I did that on a Mac using the option key and a few custom key bindings.
The real question is how do you READ it. The problem is that unless you are very selective about your fonts and which characters you use, it can become impossible to read because many unicode characters are visually indistinguishable.
But that's not the actual point. Learning a new language is a challenge. Learning a new language when you haven't already learned 10 is an even bigger challenge. Learning your first language is very difficult, which most of us have probably forgotten. Now, to the list of things you have to learn to do so, we want to add learning several dozen brand new keystrokes that nobody knows offhand? It may not seem like much compared to everything else one has to learn to program, but having to learn a lot of stuff is annoying; having to fight your input devices is like being rendered mute. Try switching your keyboard map for a few days to see how you like it. This is not a level of frustration worth pursuing.
Capslock::F15I'm prepared to be corrected but ..
Greek capital sigma is the mathematical "sum" symbol just as capital pi is the product symbol.
Added - they did; here is an older version (3.0) of the standard online http://www.unicode.org/book/u2.html
The exceptions to this policy are usually writing systems that didn't have standardized encodings at the time they were incorporated into Unicode. Also, the rather notorious CJK unification project resulted in several new overlapping layouts as Unicode policy changed over time with respect to Chinese characters.
Another reason this makes no sense is, that programming languages are actually little about syntax and much about paradigms (proc, func, oop, etc.) with technical details, like garbage collection and runtime features like interpretation. That's the important part, not the character set.
Yes, I'm one of the geeks that use Dvorak, vim and just got me a mechanical keyboard with tactile feedback. I care a lot about my typing, and I sure as hell don't want to type in unicode.
Really, I actually live in Germany, and have the extra 3 umlauts on my secondary layout, and that's already a royal pain in the ass. I also did some CJK text input (Japanese is a hobby of mine). well, don't get me started.
No, more than the ASCII character set is defiantly the very last thing you might want, eclipsed only by syntax highlighted critical path display. He could at least have taken the time to imagine what the result of that would have been, or make a mockup, then he would not post this crap!
Right now, I'm learning APL using it; it's pretty comfortable for that. An important point, though, is that APL has a finite number of extra keys. Every symbol you insert in a source file is a symbol other developers have to have a way of typing—so, while this system can work for APL or arbitrary-symbol-lang-with-a-keyboard-conf-file-in-the-installer, it won't let you just define whatever symbols you please on a file-by-file basis.[1]
[1] ...for now. I'm thinking about writing an IDE hook that scans your project for symbols your keyboard can't type given your board-set, then dumps them into a temporary "project keyboard palette", that you get to by swiping to the left/right. This would let you go beyond Unicode to use arbitrary pictorial symbols (i.e. SVG images) as characters. If you could drag keys off your palette and onto your personal boards, keyboard symbology would then become a memetic process, spreading from project to project when the symbol is useful to the reader, much like words spread in conversation.
Practically, having to regularly deal with Japanese encoding, a big issue is interoperability. Granted, a lot of issues are caused by not using unicode (unix vs windows encodings which sadly are still pervasive), and those could be mitigated by enforcing unicode.
I am not so much concerned about readability: mathematics go away with tons and tons of symbols, and it is not really ambiguous - certainly less so than most programming language syntaxes I know.
Meaning?
But that's not very interesting, because that's not really how we program, at least not anymore: you write something to be read by other people more than something to be understood by computer, and two equivalent programs are often not equivalent at all in readability. So maybe my choice of words was not optimal, and I should have chosen readability instead of ambiguity.
I think the focus on being executable by the computer is the wrong one. That's the trivial part.
Soft keyboards and composing-entry are the future.
Yes, if only developers could devise some way of remapping keyboard keys, affixing new labels or even creating entirely new alternative layouts and devices. But that sort of rocket science is at least, what, three decades out?
Second, what "productivity benefits"? Are you such an astonishing programmer than your primary bottleneck is typing your symbols? It's too slow to type -> instead of Alt-Gr->, or whatever? Or maybe the agony of having to read -> instead of →? I find it hard to believe that's much more than a rounding error.
I guess that mathematical notation is often easier to read and comprehend. I'd rather see something like this http://upload.wikimedia.org/math/9/6/9/9695855b7c5869aad99fa... than something like
sum [ for x in s -> f(x) ]
on the other hand, without an IDE that's capable of translating between both notations, editing would be rather painful
How do I type it?
How do I type it?
That's the fundamental question worth repeating three times. Numerous languages support Unicode in the syntax and it doesn't matter because nobody can use them because who wants to use a language where the 'or' operator is a textual copy and paste operation for a new user?
You can incrementally stuff more symbols onto a keyboard but I'd want to see some science that shows that people are able and willing to deal with a keyboard that contains a their local language, a full suite of mathematical symbols including Greek, Hebrew, and the various mangled Latin characters that mathematics uses, plus logic, set notation, plus the useful not-necessarily-mathematical operators that language designers either want or in some cases already use/permit such as arrows, boxes, and all the other things. And we still need our full editor keyboard shortcuts and if you're a power user (and we're talking programmers...) our keyboard shortcuts for the window manager.
So, you want to predicate learning your language on me learning all that? I'm the kind of fruitcake that learned Haskell but I still laugh at the idea of learning something like that. No sale. (And I don't use the Unicode Haskell permits because while I'm actually very comfortable remapping my own keyboard, for instance I actually have interrobang bound to a key because I found myself using it so much, why would I do that to anybody else who ever tries to read or use my code‽)