Phyllis Fox, saving Lisp history
HAIGH: So you say that you wrote the first LISP manual?
FOX: Now, this was not because I was a great LISP programmer, but they never documented or wrote down anything, especially McCarthy. Nobody in that group ever wrote down anything. McCarthy was furious that they didn’t document the code, but he wouldn’t do it, either. So I learned enough LISP that I could write it and ask them questions and write some more. One of the people in the group was a student named Jim Slagel, who was blind. He learned LISP sort of from me, because I would read him what I had written and he would tell me about LISP and I would write some more. His mind was incredible. He could give lectures. Have you ever seen a blind person lecture?
FOX: They write on a black (or white) board, and then they put a finger on the board at the point they have stopped to keep the place. Then they talk some more and then they go on writing. His mind was remarkable. He was very helpful to me. But I wrote those manuals. I would ask questions from Minsky or McCarthy, and I got it done. I think it was helpful for people to have it. I guess, essentially I’m a documenter. If you’re looking for it, that’s what I am.
Phyllis Fox did a lot more than that, but as a Lisp enthusiast, thank you to Dr. Fox for preserving our programming knowledge!If you'd like to see that documentation: http://history.siam.org/sup/Fox_1960_LISP.pdf and there is P Fox on the front cover. (This document is probably in the public domain due to the lack of copyright notice, which was a requirement of U.S. copyright law at that time, so yay to it also being Free.)
git annex metadata gui
I always wanted this to exist. So awesome that someone (not me) has gone and built it.
git-annex's metadata facilities have been somewhat of a hidden feature for power users. It will be interesting if that gets wider use. The metadata is synced as part of the git repo, and automatically merged.
Claes Wallin (韋嘉誠) shared this.
hole in one
\o/ git-annex get over tor worked the first time I tried it
(After 2+ weeks developing the feature)
the dreams of the 90 are alive in my xmonad
- wikipedia via telnet
- metafilter via gopher
- olduse.net via nntp with special NSA appearance
"Until we can be confident that these strings will never be used as a weapon, their presence probably needs to become a Debian policy violation." -- phil hands http://joeyh.name/blog/entry/trademark_nonsense/#comment-5ebe49ce6d9df9703a9ef54502b3dc04
"whenever you are in a situation like that when people have given so much to you, one of the first instincts is like what can I do for you, what can I give back?"
Ian, you helped so many of us find our answers to that question.
The Internet of Code
If you don't know haskell or lambda calculus, skip 19:30 for the start of the payoff.
Gergely Nagy likes this.
Saw this talk & was dying to see the source. http://files.luite.com/hs15/ .. which is this haskell: https://raw.githubusercontent.com/luite/hs15-talk/master/hs15.markdown
Using lists as fake value boxes in python because python doesn't know how to lexical scope
Gergely Nagy likes this.Show all 6 repliesPython 3 has the 'nonlocal' keyword that does exactly what you want (if you inserted "nonlocal x" as the first line of _func(), it would do the right thing)... but, well, you don't get it unless you switch to Python 3.
- A fantastic little Emacs Lisp poem by RMS:
In days long ago,
When clocks were so slow,
These basic keystrokes
Took too long for folks,
Unless they were writ
In C code to flit.
Today that's not so,
In Lisp they can go.
- Basic git hygiene at this point probably includes only merging git commits from others that are gpg signed (as well as gpg signing as many commits yourself as you can without going mad at the password prompts).
Unfortunately, tooling doesn't make this easy, and some things like git format-patch are actively unhelpful by not preserving gpg signatures.Also, note that signed git tags are only a signature of the sha1, so cannot be used to detect a collision attack.
Checking git commit signatures can detect a collision attack. Of course, that checking is also not enabled by default, and there's not yet a config to change that.
- Unacceptable excuses for bad behaviour in free software development:
Show all 5 replies> because that's what got them where they are so far.
- Linus and other kernel developers do it.
- You have self-diagnosed as having Asperger's.
- You value code quality over other people's feelings.
- You get angry a lot.
- You think other people are just wrong about everything.
- You thought of a funny insult.
- You're uneasy having people in the project who're unlike you.
They could have gotten where they are so far in spite of (rather than because of) the behaviors. There's always the chance that several people saying "I'm not going to take this anymore" around the same time will shift momentum away from a previously-successful project or organization.@lnxwalt That's true, the person with the bad behaviour has typically proved they can make the grade, give the company what they want, work hard, demonstrate their talents. At this point they use their value as a kind of credit system to get away with behaviour that others don't seem to get away with.
Claes Wallin (韋嘉誠) likes this.
haskell with a sailboat chaser
then and now http://joeyh.name/blog/entry/then_and_now/
On extensibility of Microformats
Once again, Amy Guy (member of the W3C Social Working Group and probably the person with sharpest analytical eye in the group) has done a fantastic breakdown of a SocialWG-related topic. This one is on the extensibility of Microformats. This is a topic of much back and forth, particularly between "Linked Data" people and "Microformats" people, and maybe Amy's post can reduce a lot of unnecessary cycling. Particularly this point is insightful:
Example debate 4
- LD: Microformats is not extensible (meaning: I can't just add my own terms and have everyone know how to use them).
- MF: Microformats is extensible (meaning: parsers are vocabulary agnostic).
... LD is talking about the vocabulary (semantics). MF is replying about the syntax. I think that's why this debate goes round in circles. I hope that clarifies something for both sides.
Way to go, Amy!