Well, looking at perl/python/PHP (as in LAMP), I would say the trick is
to pick
an application area and make it extreemely easy to use the language in
that area,
as well as trivial to install and maintain the language support.
Of course the fact that perl/python/php all picked web-services (active
web pages)
just as the internet took off may have helped.
So as is usual in computing - use your crystal ball to find out what the
next big
thing is, then make sure Haskell has a cool domain-specific-embedded
language
that is easy to use for that application domain ready, and then make sure
everyone knows about it.
Keean.
Gour wrote:
>azrael at demonlords.net (azrael at demonlords.net) wrote:
>>>>>>However if there is a desire to make Haskell more accessible to the majority
>>of programmers then the first impressions that I, and those like me have is
>>important.
>>>>>>Sure. I'm also pretty new to Haskell & ghc concerned to see Haskell used by
>more programmers.
>>Applications like darcs are very important enabling newcomers to see some
>concrete & succesful non-academia-open-source project.
>>Besides that, seeing the progress of projects working on the binding for
>gui-libraries (wxhaskell & gtk2hs) are VERY encouraging giving me hope that
>my investment in learning Haskell can be worthwile i.e. one is able to put
>together 'full-blown' application with gui interface.
>>However, these projects are mostly done by few individuals working hard and
>there is also "A Bus Hits Simon Peyton Jones" problem referred during the
>CUFP workshop.
>>Any idea how to make a (more organize) community effort to bring Haskell out?
>>Sincerely,
>Gour
>>>