caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Viet Le <vietlq85@gmail.com>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] ReasonML concrete syntax
Date: Mon, 11 Dec 2017 12:10:28 -0500	[thread overview]
Message-ID: <CAN6ygOkovdthruEUZKjg8vi=B7BXyzUvWQT+PtBskHpNNi8HpA@mail.gmail.com> (raw)
In-Reply-To: <CAG_8+G7aQuWf9G2X8weSEHetLaf+i3chyAme2ggQBVE8K7h_SQ@mail.gmail.com>

Rust ditched its syntax before release in favor of a syntax more
geared towards the kind of programmers they wanted to attract. This
wasn't a bad decision.

Many people on this mailing list seem to be unaware of the fact that
Reason is really catching on. It's simply a human reality that we like
to try things that are close to what we already know. Bringing OCaml's
syntax close to a language like Javascript, which has countless
developers nowadays, means that a much higher percentage of those
people will want to try out OCaml/Reason. And ultimately, a language
is only as good as its ecosystem -- having the best-designed language
in the world is meaningless if only a few people are using it.

I'm not one of those people who enjoys Reason's syntax (aside from the
issues they fixed in OCaml's syntax), but I appreciate what the Reason
people have done, and I expect Reason to soon eclipse OCaml in terms
of number of users. I don't see this as a bad thing -- Reason's
creators seem to really love OCaml and want to contribute back to the
community.

On Mon, Dec 11, 2017 at 11:47 AM, Viet Le <vietlq85@gmail.com> wrote:
> Yawar, crediting the popularity of Rust because of syntax is misleading.
> Mozilla has marketing budget and people behind Rust have build very active
> community with weekly newsletter and know how to market. OCaml is mostly
> used by academia and some industry players, and marketing is not being
> emphasized.
>
> ReasonML is not gaining because of syntax, it's because of huge marketing
> effort and easy to follow tutorials and examples and catchy websites. OCaml
> documentation is as plain as plain can get. Rust has a few catchy websites,
> tutorials and free books as well.
>
> Viet.
>
> On 11 December 2017 at 16:10, Ian Zimmerman <itz@very.loosely.org> wrote:
>>
>> On 2017-12-11 15:40, Gerd Stolpmann wrote:
>>
>> > although, with currified functions this is only an illusion
>>
>> As they say, "this".  The alternative syntax will lead to people never
>> learning about partial application.
>>
>> Does your own language curry multiple arguments by default like Ocaml
>> does?  If yes, then (IMO) your choice is a mistake, in spite of the
>> (good) arguments you give for it.
>>
>> I would be more tolerant about such syntax in a SML-like language where
>> multiple arguments are modelled with tuples in most cases.
>>
>> --
>> Please don't Cc: me privately on mailing lists and Usenet,
>> if you also post the followup to the list or newsgroup.
>> To reply privately _only_ on Usenet, fetch the TXT record for the domain.
>>
>> --
>> Caml-list mailing list.  Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
>
>
> --
> Kind regards,
> Viet

  reply	other threads:[~2017-12-11 17:10 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
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 [this message]
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='CAN6ygOkovdthruEUZKjg8vi=B7BXyzUvWQT+PtBskHpNNi8HpA@mail.gmail.com' \
    --to=yotambarnoy@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=vietlq85@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).