From: Vincent Balat <vincent.balat@pps.jussieu.fr>
To: caml-list@yquem.inria.fr
Cc: Kuba Ober <ober.14@osu.edu>, caml-list@inria.fr
Subject: Re: [Caml-list] [announce] O'Browser : OCaml on browsers
Date: Tue, 18 Nov 2008 19:32:48 +0100 [thread overview]
Message-ID: <200811181932.48895.vincent.balat@pps.jussieu.fr> (raw)
In-Reply-To: <200811181315.30067.ober.14@osu.edu>
Hi,
On Tuesday 18 November 2008 19:15:28 Kuba Ober wrote:
> On Tuesday 18 November 2008, you wrote:
> > On Mon, 2008-11-17 at 22:43 -0500, Kuba Ober wrote:
> > > > Please note that this is an early version, in particular the DOM
> > > > interface module is neither pretty nor well typed.
> > > > However, it can already be used to create little applets or scripts
> > > > (as in the tutorial [2], the examples of the distribution [3] or my
> > > > webpage [4]) and we'll be glad to receive your comments or bug
> > > > reports.
> > >
> > > And the reason is?....
> >
> > To me, the fact that you can write portable lightweight applets sounds
> > like a good enough reason. That and the fact that I can see this being
> > used by stuff like Ocsigen to make for (even) richer client-server
> > applications.
>
> I presume that one can have some Javascript library to abstract out
> platform differences, but to have a whole new language? Well, of course
> what works works, the question is if the performance is any good.
Our final goal is of course to write the whole Web application in OCaml (both
server and client sides). And thus to get the same static guarantees for the
code beeing executed on the browser as we have on server side with Ocsigen
(for example valid xhtml, etc).
To run OCaml on a browser, there are several solutions:
For example you can use a compiler to js (see for example ocamljs), or a
plugin. O'Browser is an alternative. It seems to be efficient enough for most
uses. For tasks requiring very high efficiency, the only solution is a plugin
_and_ a very efficient xhtml/css rendering engine.
Cheers,
Vincent Balat
next prev parent reply other threads:[~2008-11-18 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 16:20 Benjamin Canou
2008-11-18 3:43 ` [Caml-list] " Kuba Ober
2008-11-18 7:33 ` David Teller
2008-11-18 18:15 ` Kuba Ober
2008-11-18 18:32 ` Vincent Balat [this message]
2008-11-18 20:01 ` David Thomas
2008-11-21 15:27 ` Benjamin Canou
2008-11-30 12:09 ` William Le Ferrand
2008-11-18 8:18 ` Jon Harrop
2008-11-18 18:18 ` Kuba Ober
2008-11-18 8:33 ` Florian Hars
2008-11-18 9:12 ` Paolo Donadeo
2008-11-18 9:14 ` Burgisser Francois
2008-11-18 9:40 ` Gabriel Kerneis
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=200811181932.48895.vincent.balat@pps.jussieu.fr \
--to=vincent.balat@pps.jussieu.fr \
--cc=caml-list@inria.fr \
--cc=caml-list@yquem.inria.fr \
--cc=ober.14@osu.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