The Bipolar Lisp Programmer
lambdassociates.org
lambdassociates.org
I used to think 'publish or perish' was a bad thing for academia. Now I don't. Everyone needs external social pressure.
Quoted for truth. Plus with a big enough problem, there will always be neighboring issues you can look at when you get bored of the sub-sub-problem that you are focusing on at the moment.
He's even further off when he says that the reason Lisp isn't more popular is because of the mysterious quality that attracts such people. It's unpopular for more mundane reasons: the syntax looks odd, and there's no good, standard implementation with lots of libraries.
I think his point was that there's no good, standard implementation with lots of libraries because many of the people drawn to Lisp have big ideas but are bad at finishing things.
Language designers who have what it takes are quite rare: Matz, Guido van Rossum, Larry Wall. It just happens none of them chose to create a Lisp dialect. But the problem is not the brilliant failures who are drawn to Lisp, but that e.g. Matz wasn't (quite).
[0] A stupid question would be anything you can find out by searching google, reading the manual or possibly digging through a few thousand lines of source code.
[1] http://groups.google.com/group/comp.lang.lisp/msg/4c95766a8b...
"And here we are rushing to put in a mee too comment. I have known this about me for sometime. I had this thing about people. What ever you admit, you admit it because you are proud of it. Like for eg. I am always busy - yeah, you are proud of being busy. Or to bring the point out, one of my friends admitted to me that he suddenly realised that he was arrogant ( a BBM himself ), subconsciously he is proud of being arrogant.
My simple question: Does it have to be like this ? I mean, being Brilliant and a failure. C'mon guys, failure sucks. Big time. If you don't feel that, you don't have a problem. But if you do, consider this. Lets turn this inside itself in the true spirit of Lisp. Being BBMs we can come up with brilliant solutions to 'cope up with brilliance' while avoiding failure. Can't we ? Stop being proud. That's the point where it Starts. Post any coping mechanisms you have discovered over the years as reply to this thread. Thanx."
http://news.ycombinator.com/item?id=84655
Net result: kids praised for their intelligence tend to look for things that are easy or to appear smart. Challenges and mistakes often de-motiviate these kids. "Smart"-oriented kids tend to have an attitude where intelligence is a fixed, natural attribute and being able to accomplish something easily is a sign of natural intelligence. "Growth"-oriented kids tend to have an attitude that intelligence can grow and that challenges and mistakes are opportunities to learn. These kids tend to relish challenges, often getting even more excited over difficult problems.
I think that sums up LISP and C with regards to the brilliantly unaccomplished.
Being able to trivially do something in LISP that is difficult in C is good ... yet for someone who relishes a challenge, what does that mean to find a really hard problem in LISP that is nearly impossible in C?
(Hack, the only way to search YC at YC I know of: try to google for the old link and submit it to YC again, and it will detect the duplicate and lead you to the thread )
(Front page snapshots from Sep 29, 2007. (wouldn't have helped you in this case))
I never thought I was bipolar.
Fortunately, the extreme ups-and-downs seem to be lessening as I get older.
Like Unix?
Oops. Bullshit detected.
LOL. Two.
ADDENDUM: Oh, and his "point" is pointless. One person, two people, N people are meaningless distinctions. Besides, most Lisp projects that have any real success are group efforts as well, I'm sure. The REAL point is always the same: What are those projects? Where are they? How successful are they, really? I'll point it out as often as this article gets re-posted: When you compare C/C++ with Lisp based upon the only thing that matters, results, then Lisp is a near-complete failure. The applications that really matter, that people really use, that have real performance, that solve real problems, are written in C/C++/Blub, or some scripting language.
...and that list is woefully abbreviated.
Which bridge do you think we should take?
Neither before also knowing how many people attempted to cross each bridge, so I know the success ratio for each.
But if i want to hack something together for my own purposes I dont have the time to do it in C.