From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml for Industry
Date: Mon, 8 Aug 2005 18:20:09 +0100 [thread overview]
Message-ID: <200508081820.09595.jon@ffconsultancy.com> (raw)
In-Reply-To: <013d01c59c3c$a93375e0$0100a8c0@warp>
On Monday 08 August 2005 18:14, Nicolas Cannasse wrote:
> That's bad news that nobody answered to this interesting topic within one
> week.
Yes. Back to the drawing board. :-)
> As for buying a report, it might be nice to freely provide some results and
> trends and then sell the "full report" if it's what you want to do.
Rather than writing a whole report (seeing as there's no interest in it),
perhaps it would be better to have a news letter that people can subscribe
to? That would be cheaper for customers and would require less initial
investment on our part.
> My company is using OCaml is a lot of our projects, mainly for development
> tools (compilers, level generators, resources builders... ). It's perfectly
> suitable in the case where you need to manipulate a lot of data structures
> and apply algorithms to them.
Yes, that is exactly what we are finding. There is also a market for
OCaml-generated C code, IMHO.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2005-08-08 17:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 17:26 Jon Harrop
2005-08-08 17:14 ` [Caml-list] " Nicolas Cannasse
2005-08-08 17:20 ` Jon Harrop [this message]
2005-08-08 17:58 ` skaller
2005-08-08 18:35 ` Jon Harrop
2005-08-08 23:05 ` Chris Campbell
2005-08-08 23:32 ` Erik de Castro Lopo
2005-08-09 1:49 ` skaller
2005-08-09 3:18 ` Erik de Castro Lopo
2005-08-09 4:17 ` skaller
2005-08-09 5:39 ` Nicolas Cannasse
2005-08-08 20:30 ` Yaron Minsky
2005-08-08 21:10 ` Jeremy O'Donoghue
2005-08-09 15:34 ` Eric Stokes
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=200508081820.09595.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--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