caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yawar Amin <yawar.amin@gmail.com>
To: Sven SAULEAU <sven.sauleau@xtuc.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ReasonML concrete syntax
Date: Mon, 11 Dec 2017 10:51:57 -0500	[thread overview]
Message-ID: <CAJbYVJKC18D-LBS1CU+H6OS0JnMLG_e5vN0dyN+ZwH87o+wqSw@mail.gmail.com> (raw)
In-Reply-To: <e395579f-bd3f-124e-5aa3-2c7c430c7411@xtuc.fr>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

Hi Sven,

On Mon, Dec 11, 2017 at 1:50 AM, Sven SAULEAU <sven.sauleau@xtuc.fr> wrote:

> [...]
> I'm afraid it probably won't, if they are used to the JavaScript syntax.
> Reasonml is also meant to be used in the web more than used through OCaml.
>

ReasonML adoption automatically means OCaml adoption, because ReasonML _is_
OCaml. People will be learning about and using HM type inference, modules
and functors, polymorphic variants, and all the good stuff. Don't let the
syntax fool you ;-)

Also, ReasonML itself is meant to target all platforms that OCaml itself
targets. Right now the Reason team is focusing on the JavaScript + React
use case to prove out the technology and appeal to a wide base. But they
also use jbuilder and opam to target bytecode and native. There are no
restrictions.

By the way, to the people calling the syntax ugly and its users idiots,
please tone yourselves down and think about why OCaml has been around in a
niche for 20 years but Rust took off in less than five.

Thanks,

Yawar

[-- Attachment #2: Type: text/html, Size: 1503 bytes --]

  parent reply	other threads:[~2017-12-11 15:52 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 18:12 Robert Muller
2017-12-11  0:09 ` Yawar Amin
2017-12-11  5:50   ` Viet Le
2017-12-11  6:45     ` Ian Zimmerman
2017-12-11  6:53       ` Sven SAULEAU
2017-12-11  6:50     ` Sven SAULEAU
2017-12-11  6:54       ` Evgeny Khramtsov
2017-12-11  7:22         ` =?gb18030?B?Qm9i?=
2017-12-11  7:16           ` Evgeny Khramtsov
2017-12-17 15:02         ` Paolo Donadeo
2017-12-17 16:01           ` Guillaume Huysmans
2017-12-17 16:55             ` Paolo Donadeo
2017-12-17 20:13               ` Ian Zimmerman
2017-12-17 20:49                 ` Robert Muller
2017-12-18  1:34                   ` Yawar Amin
2017-12-18 16:36                     ` Evgeny Khramtsov
2017-12-18 17:00                       ` Jesper Louis Andersen
2017-12-18 17:27                         ` Gary Trakhman
2017-12-18 17:53                         ` Evgeny Khramtsov
2017-12-18  2:14                   ` Yawar Amin
2017-12-11 15:51       ` Yawar Amin [this message]
2017-12-11 16:07         ` Sven SAULEAU
2017-12-11 17:11         ` David Brown
2017-12-12  3:49         ` Louis Roché
2017-12-12  4:18           ` Yawar Amin
2017-12-12  5:52           ` Oliver Bandel
2017-12-11 14:40 ` Gerd Stolpmann
2017-12-11 16:10   ` Ian Zimmerman
2017-12-11 16:47     ` Viet Le
2017-12-11 17:10       ` Yotam Barnoy
2017-12-11 18:56         ` Robert Muller
2017-12-11 19:23           ` Yawar Amin
2017-12-11 21:10         ` Marshall
2017-12-11 17:29       ` Yawar Amin
2017-12-11 17:59       ` Ian Zimmerman
2017-12-11 18:30     ` Gerd Stolpmann
2017-12-13  8:22       ` Sebastien Ferre
2017-12-13  9:26         ` Evgeny Khramtsov
2017-12-13 10:37           ` David Allsopp
2017-12-13 16:38             ` Marshall
2017-12-13 16:44               ` Yawar Amin
2017-12-13 17:20                 ` David Allsopp
2017-12-13 17:51                   ` Yawar Amin
2017-12-13 17:39         ` Hendrik Boom
2017-12-13 17:55           ` Robert Muller
2017-12-13 18:19             ` Viet Le
2017-12-13 19:29             ` Yawar Amin
2017-12-13  8:55 ` Nicolas Boulay

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=CAJbYVJKC18D-LBS1CU+H6OS0JnMLG_e5vN0dyN+ZwH87o+wqSw@mail.gmail.com \
    --to=yawar.amin@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=sven.sauleau@xtuc.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;
as well as URLs for NNTP newsgroup(s).