caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "chris.danx" <chris.danx@ntlworld.com>
To: skaller@users.sourceforge.net
Cc: "Brandon J. Van Every" <vanevery@indiegamedesign.com>,
	caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] build tools with critical mass?
Date: Mon, 06 Sep 2004 16:01:36 +0100	[thread overview]
Message-ID: <413C7BD0.8090109@ntlworld.com> (raw)
In-Reply-To: <1094462464.3352.1043.camel@pelican.wigram>

skaller wrote:
> On Mon, 2004-09-06 at 12:02, chris.danx wrote:
> 
>> Ocaml is my 
>>choice for graphics because of it provides good performance and doesn't 
>>pigeon hole the problem to an "imperative", "object orientated" or 
>>"functional" solution.
> 
> Yes but if you look at the reason you can do this, you'll
> find answers like 'sound type system', and then you can
> start to use that as a way to judge the capabilities of
> other languages.

It's almost a certainty that when someone brings up a discussion on type 
systems there will be a flame war and no consensus at the end.  This is 
one reason why I did not mention that Oz was dynamically typed.  The 
other is a language being statically or dynamically typed is not a big 
thing for me.  I understand the impact this choice has, what the 
advantages and disadvantages are and how they will affect the outcome. 
Then I choose the right tool for the job at hand.  I don't sit on one 
side of the fence screaming x typed languages are better than y typed 
ones.  Similarly for other aspects of languages.

Discussing such things is important for understanding them, but 
championing one over another with a closed mind (which IME is the case 
for a lot of people) is not imo helpful.


> in that case 'it meets my needs' isn't so much of an argument,
> since the *real* requirement isn't that it meets you needs,
> but that it meets you needs *and will continue to do so 
> in the face of change*.

This is true if you want a language for lots of problems.  So long as a 
language is appropriate for the design solution and doesn't constrain it 
in ways that make the design ugly, that language is likely to be ok for 
that problem.  So I'm perfectly happy to ditch Ocaml in favour of X when 
X allows a better design for a particular problem though will continue 
to use OCaml and Oz as general purpose languages.


> In other words to predict the true productivity benefits
> of a language you really do need to examine the mathematical
> fundamentals.

I don't see how this follows.  The fact that OCaml has or does not have 
a Milner-Hindley type system is not all that relevant to me because I 
have no clue what that is, nor do I care to learn it.  I will learn the 
practical effects of the type system by programming in Ocaml and reading 
the documentation.  Ditto other parts of the mathematical forumaltion of 
Ocaml.

They help, but I don't want to spend hours distracting myself learning 
theory from the task of developing.  In practice I learn enough theory 
to get by in practice and more theory from practice.  That works for me. 
  If the problem requires knowlege I don't have, I ask and learn it.


Chris

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      reply	other threads:[~2004-09-06 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 20:28 Brandon J. Van Every
2004-09-06  2:02 ` chris.danx
2004-09-06  4:56   ` Brian Hurt
2004-09-06  9:21   ` skaller
2004-09-06 15:01     ` chris.danx [this message]

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=413C7BD0.8090109@ntlworld.com \
    --to=chris.danx@ntlworld.com \
    --cc=caml-list@inria.fr \
    --cc=skaller@users.sourceforge.net \
    --cc=vanevery@indiegamedesign.com \
    /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;
as well as URLs for NNTP newsgroup(s).