From: wester@ilt.fhg.de
To: caml-list@inria.fr
Subject: Re: [Caml-list] Why People Aren't Using OCAML? (was Haskell)
Date: Tue, 27 Mar 2001 10:57:26 +0200 [thread overview]
Message-ID: <200103270857.KAA24323@ilt.fhg.de> (raw)
In-Reply-To: <4.3.2.7.2.20010326172152.02986a60@shell16.ba.best.com>
>
> I just gave a talk at the Game Developers Conference (www.gdconf.com) on "modern" language features, most of which are associated with functional programming (although the misnomer "modern" is a little odd, since they're almost all in Lisp, and ML's 20 ye
> ars old :). I don't have the feedback forms on the talk yet, so I don't know how useful people found it, but it filled up completely and they were turning people away, which for a 9am talk at a game conference strongly implies people are interested in al
> ternative languages!
>
> I'll put the slides up on my website soon, although I doubt anybody on this list will learn anything from them. OCaml has all the features I talked about except 1) introspection/reflection and 2) template-style generics (as opposed to polymorphism-style
> generics).
>
Don't you hope that at least occasionally there will be an OCaml/funtional language
beginner on this list, somebody like me?
The original question was:
Why People Aren't Using OCaml?
I think one reason is that almost all programmers have to deal with C in one way
or the other. That means that C is one of the first languages everybody has to
learn. There has been a campain promoting object oriented programming over
the last decade. The message was: If you want to write good, maintainable
software use an object oriented language. The "natural" choice for C programmers
is then C++ and Java. I guess most programmers don't even have an idea
what functional programming is. And for a programmer who has experience
with C++, Java and say Python there must be some really good reasons to
use any other language than these main stream languages (consider libraries,
IDE's, colleagues etc.).
What I missed when I started to look for alternatives to C++
(I still make silly mistakes that take a lot of time to eliminate),
Java (which I find cumbersome to use, all these cast's) and Python (to slow
for some applications) was a sound comparison of languages that not only
claimed that one can implement programs 10 times faster when using for
example OCaml (or Lisp or Haskell) compared to Java but that also gave
simple examples which a C++, Java programmer is able to comprehend without
having the need to learn OCaml and become experienced in using it.
One reason for me to learn Java and Python have been their huge libraries.
OCaml also has a good library (and a good documentation of it) but there
are quite a lot of things missing compared to Java and Python (please
don't understand this as critique).
Onother problem that I as a OCaml beginner had (and still have) is where
to use ";" and where not and some other problems with the syntax
(why not "if then else endif" instead of having to use "begin end"?). I think
that the hints in the OCaml documentation concerning this problems
could be more extensive to help beginners.
I just began to use OCaml for some small programs. I especially like the
toplevel which together with Emacs and Tuareg makes rapid prototyping
quite easy. But probably I still didn't grasp what the real advantages of
OCaml compared to C++, Java etc. are. So give me and other OCaml
beginners some more help to better understand what makes OCaml
superior compared to these main stream languages.
Rolf
-------------------------------------
Rolf Wester
wester@ilt.fhg.de
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-03-27 8:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-24 3:17 Arturo Borquez
2001-03-24 8:03 ` Vijay Chakravarthy
2001-03-24 18:38 ` Brian Rogoff
2001-03-24 21:55 ` Vijay Chakravarthy
2001-03-26 0:29 ` Dennis Gang Chen
2001-03-26 3:03 ` Brian Rogoff
2001-03-26 9:34 ` BDD and Ocaml (was: Re: [Caml-list] Why People Aren't Using OCAML?) David Mentre
2001-03-26 15:44 ` Brian Rogoff
2001-03-30 14:37 ` [Caml-list] OCaml binding to cmuBDD David Mentre
2001-03-26 14:10 ` [Caml-list] Why not article in journal ? (was Why People Aren't Using OCAML?) Christophe Raffalli
2001-03-26 12:43 ` Xavier Leroy
2001-03-26 13:25 ` [Caml-list] Why People Aren't Using OCAML? (was Haskell) FabienFleutot
2001-03-28 8:23 ` [Caml-list] [ora book] Why a horse? David Mentre
2001-03-29 13:48 ` [Caml-list] Why People Aren't Using OCAML? (was Haskell) Xavier Leroy
2001-03-29 14:05 ` Daniel de Rauglaudre
2001-03-29 14:14 ` Xavier Urbain
2001-03-29 14:38 ` Jean-Francois Monin
2001-03-29 16:19 ` Brian Rogoff
2001-03-27 23:43 ` John Max Skaller
2001-03-28 4:37 ` Brian Rogoff
2001-03-28 14:24 ` Joshua D. Guttman
2001-03-28 19:32 ` William Chesters
2001-03-27 3:43 ` Chris Hecker
2001-03-27 8:57 ` wester [this message]
2001-03-30 18:59 ` John Max Skaller
2001-03-28 22:00 ` Joseph R. Kiniry
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 14:26 Toby Moth
2001-03-23 18:04 [Caml-list] recursive modules redux, & interface files Brian Rogoff
2001-03-23 20:35 ` [Caml-list] Why People Aren't Using OCAML? (was Haskell) Mattias Waldau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200103270857.KAA24323@ilt.fhg.de \
--to=wester@ilt.fhg.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox