caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: oliver <oliver@first.in-berlin.de>
To: David MENTRE <dmentre@linux-france.org>
Cc: Esther Baruk <esther.baruk@gmail.com>,
	"caml-list@inria.fr users" <caml-list@inria.fr>
Subject: Re: [Caml-list] French study on security and functional languages
Date: Sat, 25 May 2013 01:13:45 +0200	[thread overview]
Message-ID: <20130524231345.GA1923@siouxsie> (raw)
In-Reply-To: <CAC3Lx=a9zCzBvD0eHRg8SS8D49+dH4hweBsfNwuOKBWf_ETYMA@mail.gmail.com>

On Fri, May 24, 2013 at 05:18:53PM +0200, David MENTRE wrote:
[...]
> Nonetheless I find interesting and refreshing[1] the fact that ANSSI
> is at least seriously considering OCaml for writing security related
> programs.
[...]

Is this really especially for OCaml?
or also Haskell and the other languages?

I ask, because when looking at the comparison table
from page 55, then there are other languages that also
have good results.

Looks like the type system is the main distinction between
the well and the bad languages.

And there are OCaml, F#, Scala, Haskell, which have good rates
in the table.

It would have been nice, if non-functional languages would have been
rated also. I think they all would be on the bad side.

This would then be a good argument pro Functional languages.
But all the languages that were in the table were functional
languages.
The typical average decider in a company, who does have influence
to decide for the one or the other language would not know all the other
languages.

So, this comparison might be good for certain "insiders",
but the mainstream is using C, C++, Java, Perl, Python, Ruby and so on.
If these languages would be checked also (and I assuem they would be
a bad choice), then this paper would be really a good argument
for deciders of many companies.

In most cases I'm the only person in a project who at all knows
languages like OCaml... and also uses it.
And most often it's not allowed to use it because of this reason...
...but sometimes, some personal tools are allowed to write in any language.
But most often not even that... and mainstream languages have to be used...


Ciao,
   Oliver

  parent reply	other threads:[~2013-05-24 23:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  7:02 David MENTRE
2013-05-24  7:55 ` Francois Berenger
2013-05-24 12:35   ` rixed
2013-05-24 14:43     ` oliver
2013-05-24 15:15       ` rixed
2013-05-27  1:18         ` Francois Berenger
2013-05-24 14:35   ` oliver
2013-05-24 14:59     ` Esther Baruk
2013-05-24 15:05       ` oliver
2013-05-24 15:18       ` David MENTRE
2013-05-24 15:36         ` Esther Baruk
2013-05-24 23:13         ` oliver [this message]
2013-05-26 14:14           ` Marek Kubica
2013-05-24 17:44     ` Pierre-Etienne Meunier
2013-05-27  8:55       ` Fabrice Le Fessant
2013-05-24 14:47   ` oliver
2013-05-24 15:02     ` Johan Grande
2013-05-24 12:41 ` Olivier Levillain
2013-05-24 12:46   ` Anil Madhavapeddy
2013-05-25  8:53     ` Olivier Levillain

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=20130524231345.GA1923@siouxsie \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@inria.fr \
    --cc=dmentre@linux-france.org \
    --cc=esther.baruk@gmail.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).