caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Raoul Duke <raould@gmail.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] whither portability?
Date: Sat, 26 Sep 2015 05:48:16 -0700	[thread overview]
Message-ID: <CAJ7XQb6pcWOzcLgt9U7UpFf0fV4MHhWLtMdmR=wszzwi-3zy5Q@mail.gmail.com> (raw)
In-Reply-To: <1443259698.4442.12.camel@e130.lan.sumadev.de>

Exciting to hear! Thank you and your contributors for this work. I
know there are ways people can be parochial, but I have never been
able to fathom how the core OCaml team can ignore mobile so actively,
it seems. It is to sigh, oy veh.

Throwing out random ideas as a potential some-day user of such a thing:

* Getting anything working as simply as possible would be a nice first
step, even if it isn't the most performant. I.e. bytecode. It seems
Apple has loosened up on that a bit over the years? And I wonder if
LLVM bytecode would be no problem with them now.

* FFI will be essential. It is one thing to have 2+2 working on
mobile, it is another to be able to get any real app work done. (In
the past I have had some negative experiences with OCaml and FFI for
OpenGL so I am always a little worried about trying to reignite my
relationship with OCaml.)

* Ideally it has to integrate well with the platform toolchains,
including the preferred IDEs. E.g. if there's no good installer, if I
have to do a lot of work to build things, etc., then I'm way less
likely to even try to use it. I know that is work most people do not
like to do. I say that empirically.

* If you can find some commerical users and support, that could help
drive some of the above issues further faster (although of course the
vector along which they proceed is subjective).

  reply	other threads:[~2015-09-26 12:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 21:13 Raoul Duke
2015-09-26  9:28 ` Gerd Stolpmann
2015-09-26 12:48   ` Raoul Duke [this message]
2015-09-26 15:59     ` whitequark
2015-09-26 16:21       ` Gerd Stolpmann
2015-09-26 23:29       ` Raoul Duke
2015-09-27  0:47         ` Spiros Eliopoulos
2015-09-27  0:51           ` Raoul Duke
2015-09-27  0:20       ` Oliver Bandel
2015-09-27  0:27         ` Yotam Barnoy
2015-09-27 14:10           ` Oliver Bandel
2015-09-27  0:55       ` Raoul Duke
2015-09-27 14:33         ` whitequark
2015-09-27 17:19           ` Raoul Duke
2015-09-27 17:41             ` whitequark
2015-09-26 17:10     ` Gerd Stolpmann

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='CAJ7XQb6pcWOzcLgt9U7UpFf0fV4MHhWLtMdmR=wszzwi-3zy5Q@mail.gmail.com' \
    --to=raould@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    /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).