I think many of the issues were discussed with great clarity on slashdot.
If we get the relevant critical mass of functional programmers, you will
definitely be hearing from us. Off the top of my head here are some
Haskell specific things that we need:
* HSP pages (like ASP or JSP or PHP)
* in memory Haskell server analogous to JServ that talks to apache
* Haskell access to a pool of database connections
* Haskell access to Java classes
* Encapsulation of Haskell as Java classe
And all of this has to be relatively zipless and compatible with an
existing JServ/JSP/Apache installation.
I am leaning towards python because it has curry, map, filter, lambda
expressions and a Java interpreter.
-Alex-
___________________________________________________________________
S. Alexander Jacobson Shop.Com
1-212-420-7700 voice The Easiest Way To Shop (sm)
On Sun, 16 Jul 2000, Manuel M. T. Chakravarty wrote:
> "S. Alexander Jacobson" <[EMAIL PROTECTED]> wrote,
>
> > I am President of Shop.com and know and love Haskell (and FP in general).
> > Nonetheless, the issue with using Haskell commercially is that:
> > * we cannot afford the training costs associated with getting new
> > programmers up to speed and finding programmers at all (much less Haskell
> > programmers) is fairly difficult.
> > * Haskell interfaces with databases and existing Java libraries are not
> > all that complete/clean
>
> Could you maybe tell us what it is that you need with
> respect to database interfaces and Java libraries (and where
> appropriate where deficiencies are in existing solutions)?
> I think, many people here would be happy to help plugging
> holes if that makes Haskell more usable, but it is sometimes
> a bit difficult for us to see which holes bite users most.
>
> Thanks,
> Manuel
>
