|
Just yesterday I had a thought about the link between Paul and Lisp. I came to the conclusion that since Paul was a published author of Lisp books at the time, and saw an opportunity to use it in production (maybe to gain experience and write another book about it to share his findings with others) but ended up learning about startups, dot coms, investors, and users as well, he instead wrote essays on paulgraham.com and used some of them in his Hackers and Painters book. I dare say his essays are about starting up in general, and there is no secret plan to convert users into using Lisp. Every week on YCombinator Startup News, somebody asks about learning Lisp to do a web app, when there are way more other things to worry about than the language. Use something you want to use every day, not just in theory because someone else did. I'd learn an unknown language if I was at a startup that used it every day, but otherwise, I would default to using a web framework that I have already used in the past. My conclusion is that if you're creating a web application using a web framework in any language you find interesting at the moment, go for it. Because that's exactly what Paul did. It just happened to be Lisp that he was an expert at, but it could have been any other exciting technology. Whether Paul would use Lisp today or not on a new project is irrelevant as far as your plate is concerned. He could use Lisp, but it wouldn't mean that there aren't other good alternatives. And if he did use a language other than Lisp, maybe it would be so because he would want to learn web framework since he wouldn't be writing Lisp books any more, but Lisp may still be something he would normally use more often. I think this is a great question. |
A piano concert's quality depends much more on the pianist than the piano, but you'll notice the pros don't give concerts on uprights.
If you have a choice of several languages, it is, all other things being equal, a mistake to program in anything but the most powerful one.