Richard Conroy
2/12/2007 7:00:00 PM
On 2/12/07, David Morton <mortonda@dgrmm.net> wrote:
> > That's really good. Thanks for sharing. I followed the link. I
> > think the article is well worth reading.
>
> I have to disagree with the paper a bit. It seems that the author is
> evaluating languages in a vacuum without practical considerations...
> typical for academia.
>
> If he likes OCAML so much, is there a mod_ocaml for apache? are
> there MIME, SMTP, IMAP libraries available? Is there a a nice
> framework like Rails to build with? (just picking on it because the
> author likes it so much. I've never used OCAML)
OCaml gets a lot of attention mostly as a source of ideas for
language designers, who are designing other languages, not
OCaml.
It has some fantastic features at the language
design level. We are talking drool-worthy. And absolutely no library
to speak of. The most sophisticated thing you can do with the
standard distro is read a file.
It *does* have a way of binding to C code. If it exists in C, you can
use it and that's its hand-wavey excuse for not having any APIs.
> The pragmatic side of me says I don't have time to look at a language
> that can't get the job done. (even if you add "yet" to that).
If anything is going to happen with OCaml, it will happen at the
heavy-duty OSS level (like kernel writers). Its getting a lot of attention from
the traditionally C-only crew.
Its feature set is extremely impressive though, if you are comfortable at
working in C, it would probably be an interesting language to learn.
Currently its use in practical concerns is almost zero without it though.