Arguing between 3 or 4 clicks doesn't change anything. There are a lot of problems with beginners and lisp, but they're far from how to get to the first implementation. As a newbee myself, googling for lisp environments was damn easy and instructive: i knew within 20 minutes that I should use linux, and if i really wanted windows (as I did at first) there was only one choice. When I finally had access to a decent linux it took me maybe another 20 to confirm that sbcl is the one I wanted. All that gave me lots of background information on the side.
Now the first brush with asdf on the other hand was a nightmare. I still don't understand why I have to become an expert in pgp (definitely not just a beginner) just to use asdf-install.
I think the main problem for beginners is the effort it takes to install a reasonable environment. I tried two versions for a web application server: ucw and weblocks. Weblocks meant installing more then 10 different packages and source code is pretty much standard documentation - but it's ok because it's understandable and officially beta anyways. UCW is the standard - after a year and a half I still couldn't produce an installation running on a port different then 8080 (I use 8080 for tomcat for all my machines).
All this effort is way disproportionate to the effects. Installing emacs and slime is may not be a breeze, but once you discover that googling "emacs configuration" brings up a bonanza it's worth it. (Also that .emacs in windows is _emacs... that's half a day I'll never have back). But so much effort just to get a server running... if you want to help beginners write a better ucw tutorial, don't just rearrange the links on the frontpage of lisp sites.
(btw, I hit ctrl-C before hitting reply, I just knew there was an "expired link" comming. And so it did.
Arguing between 3 or 4 clicks doesn't change anything.
You're wrong. And besides, the argument isn't between 3 or 4 clicks. It should be no more than 2, and preferably one.
There are a lot of problems with beginners and lisp, but
they're far from how to get to the first implementation.
As a newbee myself, googling for lisp environments was
damn easy and instructive: i knew within 20 minutes that
I should use linux, and if i really wanted windows (as I
did at first) there was only one choice.
You're still wrong. Not every newbie even knows what to google for, and even if they did, it shouldn't take them 20 minutes of web searching to figure out what they should download. And even that didn't lead you to the right place - there is more than one option for Windows (cusp, allegro, lispworks, and clisp for starters - that's not even counting scheme stuff), Linux isn't the only way, and SBCL isn't the only thing going on Linux. But a newbie either
a) has no way to figure all that out in a reasonably short amount of time
b) isn't going to try
And beyond that, you're still missing the point: he shouldn't have to.
Once you're concerned with learning emacs and slime and customizing your environment and installing weblocks and getting asdf and asdf-install to work, you're already committed. Difficulty doesn't matter nearly as much by that point. Being able to easily download and dick around in the REPL is the number one hurdle that keeps people from trying Lisp.
The rest of the post I agree with, and I don't argue that there are hurdles beyond the first one that are bigger and harder to conquer, but that's irrelevant if newbies aren't willing to jump the first one.
Right now I have a feeling most young lispers are at the intermediate stage. Thanks to lots of recent publicity, by pg and not only, people have gotten to know lisp exists. But I'm really not sure how many will go all the way. Even myself, in about a year I'll have to ditch java and if by then I'm not confident enough in my lisp... i'll probably learn ruby in a month.
As for the number of clicks... yes, as far as website design goes of course you're right. What I'm saying is 20 minutes of googling gives you more background. Half a page of text will probably just recommend clisp on windows, sbcl on linux, allegro if you want to pay and mention all the rest. Googling gives you a larger picture.
Ok, in the end of course one click would be better, I just don't think it makes much difference.
Now the first brush with asdf on the other hand was a nightmare. I still don't understand why I have to become an expert in pgp (definitely not just a beginner) just to use asdf-install.
I think the main problem for beginners is the effort it takes to install a reasonable environment. I tried two versions for a web application server: ucw and weblocks. Weblocks meant installing more then 10 different packages and source code is pretty much standard documentation - but it's ok because it's understandable and officially beta anyways. UCW is the standard - after a year and a half I still couldn't produce an installation running on a port different then 8080 (I use 8080 for tomcat for all my machines).
All this effort is way disproportionate to the effects. Installing emacs and slime is may not be a breeze, but once you discover that googling "emacs configuration" brings up a bonanza it's worth it. (Also that .emacs in windows is _emacs... that's half a day I'll never have back). But so much effort just to get a server running... if you want to help beginners write a better ucw tutorial, don't just rearrange the links on the frontpage of lisp sites.
(btw, I hit ctrl-C before hitting reply, I just knew there was an "expired link" comming. And so it did.