caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gary Trakhman <gary.trakhman@gmail.com>
To: Michael C Vanier <mvanier@cms.caltech.edu>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] A student feedback on OCaml
Date: Thu, 27 Jul 2017 17:34:47 +0000	[thread overview]
Message-ID: <CAJvqBXh+ADzSACqXf4Z6ijsLqJsaaOUNH06D4K_wB2FX3uksJw@mail.gmail.com> (raw)
In-Reply-To: <b4cc9b6d-31f5-09c4-bb00-a07908562787@cms.caltech.edu>

[-- Attachment #1: Type: text/plain, Size: 2681 bytes --]

Having used OCaml as a professional but not an enthusiast (I have a
clojure-depth), I am not polarized but ambivolent three months in of daily
use.  I enjoy the type system and life inside the bounds of a shared
codebase, but I'm finding a lot of the edge-system-integration (lack of 3rd
party libs) adding up.  Our company (Arena) fills in many of the gaps with
python due to its relevance as a data-science language and our problem
space, but I still think keeping everything in a JVM single process
monolith (like I have in my past) saves a lot of process-churn and
overhead.  Shelling out for _anything_ breaks abstraction boundaries and
requires complexity around build systems, etc., and we find ourselves doing
it for things like making SOAP calls, parsing XLS files, etc.  All these
prevent me from spending more time writing OCaml code.  Things like shared
infrastructure, plentiful libraries, a fast shared GC in something like the
JVM or CLR (or python or JS VM) can affect productivity more than the
language design itself.

Saying a language is 'better' depends on your use-cases, team-scale factors
and tradeoffs.  I myself can be very productive in a dynamic language, but
I'm becoming convinced that a type-system can really matter in larger
codebases, larger teams, or bitrot-prevention in code that is rarely
touched and out of mind.

Anyway, I provide these 2-cents because I think there are few people that
come to work in OCaml (or any functional language) by happen-stance and it
might be valuable feedback to someone.  Being really excited about a
language makes it easier to gloss over shortcomings.

On Thu, Jul 27, 2017 at 12:49 PM Michael C Vanier <mvanier@cms.caltech.edu>
wrote:

> It's a cute drawing.  It's hard to know more without any context.  I
> teach both Python and OCaml to undergraduates, but the students have to
> learn Python first (to get a firm grasp on basic programming).  My
> experience with OCaml (which I vastly prefer to Python) is that it's
> polarizing.  Some students absolutely love it, but others struggle with
> the language and have a hard time getting their programs to compile even
> after weeks of effort. Such students are obviously going to prefer other
> languages.
>
> Mike
>
>
> On 7/25/17 4:35 PM, Christophe Raffalli wrote:
> > Hello,
> >
> > Here is a student feedback:
> >
> > https://lama.univ-savoie.fr/~raffalli/pics/caml-versus-python.png
> >
> > Cheers,
> > Christophe
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 3511 bytes --]

  reply	other threads:[~2017-07-27 17:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 20:35 Christophe Raffalli
2017-07-25 20:49 ` Viet Le
2017-07-25 20:52   ` Oliver Bandel
2017-07-25 21:12     ` [Caml-list] Probabilistic Functional Programming Van Chan Ngo
2017-07-26  0:06       ` Francois BERENGER
2017-07-26 14:58         ` Van Chan Ngo
2017-07-28 15:47           ` Oleg
2017-07-26 10:36 ` [Caml-list] A student feedback on OCaml Soegtrop, Michael
2017-07-27 16:48 ` Michael C Vanier
2017-07-27 17:34   ` Gary Trakhman [this message]
2017-07-27 18:47   ` Damien Guichard

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=CAJvqBXh+ADzSACqXf4Z6ijsLqJsaaOUNH06D4K_wB2FX3uksJw@mail.gmail.com \
    --to=gary.trakhman@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=mvanier@cms.caltech.edu \
    /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).