Great Presentation on MetaProgramming. Talks about pg/ycombinator/lisp/ruby. [video]
http://mwrc2008.confreaks.com/03bowkett.html
The speaker summarizes Paul Graham's theories on Lisp and startups with the following statement:"Skilled programmers can write better programmers than they can hire"
I really enjoyed watching the whole video. Very interesting stuff. Highly recommended.
(
19 comments
| 30 points
| on HN
)
Another thing. He says that Perl and Lisp have a lot of power, but nothing in the way of simplicity. I take issue with that. Whereas Perl is overcomplex, Lisp is about the simplest you can get. He seems to think that "simple" means something along the lines of "understandable by people experienced in commonly-used programming languages". To that, I says pleh, and also blub.
This is basically Greenspun's 10th Law again. There's no magic in Lisp that's computationally impossible in another language, but it might be simpler to just write a Lisp in that language first. Rubinius did something even tougher: they wrote a Ruby. The advantage of this is that it's backwards-compatible with all their existing code, while upgrading to sexps would not be.
I think the monkeypatching corresponds to only the front half of Lisp macros. The macroexpand part comes from making the monkeypatches log Ruby code, and then running the log.
I didn't realize macbooks had become so pervasive in the ruby world.
As peculiar and different as lisp is, the difficulty of learning it is highly overrated.
That being said, at first the parens bugged me a little bit, but as I got to developing more applications, the more I really grew to LOVE the parens. To me, they introduce a certain purity to the programs that I write; it's like every s-expr is a single thought and every function is a train of thinking. Beyond that, an additional benefit that I've found is that I can hold MUCH more of a program in my head when they're organized this way. I think it has to do with the chunking theory of memory - I don't have to remember the particulars of each chunk; just what each chunk did.
Anyways, it's a big enough attraction to me now that I regret not having them available in my day-to-day languages.
good talk.
but it didn't sound like that. it really sounded like it never occurred to him to just store the random seed(s) because he said when you hear a great piece in randomly-generated music, it's gone forever, even though the seed is a fundamental and controllable aspect of that
[edit]he said it would generate a log of code which would point back to the generating/generated code. i can't really tell what he was effectively storing though. to reproduce the music well, the seed would have to be in there somewhere, unless it's only in charge of choosing a few discrete items
Plus then he couldn't grep his music, which is the really cool part.