From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: Christophe Raffalli <christophe@raffalli.eu>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] A student feedback on OCaml
Date: Wed, 26 Jul 2017 10:36:11 +0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A175B28138E@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20170725203527.dr43f6cjmdqqiq7p@delli7.univ-savoie.fr>
Dear Christophe,
comparing Python with OCaml is like comparing a hand milling tool (a "Dreml") with a CNC milling machine. For quick tasks the manual tool is better, for complex/precision/production work the CNC machine is better. I use both Python and OCaml for different tasks. There is a certain overlap area where I discuss with colleagues what they would use for this task before I start, but there is a large area where one or the other is clearly better. And I agree that for many tasks students are confronted with, Python is the better choice. But one shouldn't conclude from this, that this is the case for all tasks, and I would expect that teachers make this point.
Best regards,
Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2017-07-26 10:36 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 ` Soegtrop, Michael [this message]
2017-07-27 16:48 ` [Caml-list] A student feedback on OCaml Michael C Vanier
2017-07-27 17:34 ` Gary Trakhman
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=0F7D3B1B3C4B894D824F5B822E3E5A175B28138E@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=caml-list@inria.fr \
--cc=christophe@raffalli.eu \
/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