Sir, Please Step Away from the ASR-33 (2010)
queue.acm.org
Sir, Please Step Away from the ASR-33 (2010)
1–10 of 291 posts
Re: Sir, Please Step Away from the ASR-33 (2010)
#2"When I was a child, I used to speak like a child, think like a child, reason like a child; when I became a man, I did away with childish things.
[..]
Syntax highlighting is juvenile. When I was a child, I was taught arithmetic using colored rods. I grew up and today I use monochromatic numerals." - Rob Pike
Re: Sir, Please Step Away from the ASR-33 (2010)
#3(2010)
Re: Sir, Please Step Away from the ASR-33 (2010)
#4If I wanna use something like a ™ I have to google how to enter it, or just google and copy the character. I don't want any extra glyphs in my code until it's just as easy to enter (at close to full speed) as the glyphs I already have access to.
Re: Sir, Please Step Away from the ASR-33 (2010)
#5>>> world's second write-only programming language
I am not clever enough to comment on the meat of the article but I love that quote :-)
Re: Sir, Please Step Away from the ASR-33 (2010)
#6Go hardly looks different than BCPL from 1967.
Re: Sir, Please Step Away from the ASR-33 (2010)
#7If I wanna use something like a ™ I have to google how to enter it, or just google and copy the character. I don't want any extra glyphs in my code until it's just as easy to enter (at close to full speed) as the glyphs I already have access to.
Compose, T, M.
Re: Sir, Please Step Away from the ASR-33 (2010)
#8[deleted]
Re: Sir, Please Step Away from the ASR-33 (2010)
#9Go hardly looks different than BCPL from 1967.
This is pretty much an intentional design choice.
Fun fact: the first commit in the Go repository is from 1972. In B.
https://github.com/golang/go/commit/7d7c6a97f8
Followed by a commit from 1974 to convert it to C, and 1988 to convert it to ANSI C:
https://github.com/golang/go/commit/0bb0b61d6a
Re: Sir, Please Step Away from the ASR-33 (2010)
#10If I wanna use something like a ™ I have to google how to enter it, or just google and copy the character. I don't want any extra glyphs in my code until it's just as easy to enter (at close to full speed) as the glyphs I already have access to.
Compose, T, M. https://en.wikipedia.org/wiki/Compose_key
I use the compose key a lot; when writing docs I tend to use → instead of ->, I use – instead of -, etc. I have an extensive XCompose set up for all this, and I find it very convenient.
But it's still three keystrokes instead of one. I wouldn't really look forward to using × instead of *, ÷ instead of /, etc. all the time, even though I can type them here with relative ease the hassle increases the more you use it (I don't tend to bother with fancy “quotes” for example).
I also don't think it really matters all that much. What's wrong with *? Sure, × looks nicer, but * is clearly the pragmatic choice.*