From: Yawar Amin <yawar.amin@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:29:45 -0500 [thread overview]
Message-ID: <605BA6C2-DB0A-4601-B0C8-7646DB98764A@gmail.com> (raw)
In-Reply-To: <CAG_8+G7aQuWf9G2X8weSEHetLaf+i3chyAme2ggQBVE8K7h_SQ@mail.gmail.com>
Hi Viet,
> On Dec 11, 2017, at 11:47, Viet Le <vietlq85@gmail.com> wrote:
> 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.
You need to have something to market. One of the things the Rust community markets is their familiar C-like syntax. Also, I think it’s a stretch to say that Mozilla has a Rust-dedicated marketing budget. Their Rust budget is most likely taken up by infrastructure and devops.
> ReasonML is not gaining because of syntax, it's because of huge marketing effort and easy to follow tutorials and examples and catchy websites.
Like I said, syntax is one of the things the Reason team is marketing heavily and it’s a big selling point. They’re not magically generating buzz just because they’re throwing a lot of blog posts out there and seeing what sticks.
I agree with you that syntax is not the only factor in a language’s popularity. But it is a significant factor. The fact that people here are discussing syntax proves that.
Regards,
Yawar
next prev parent reply other threads:[~2017-12-11 17:29 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
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 [this message]
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=605BA6C2-DB0A-4601-B0C8-7646DB98764A@gmail.com \
--to=yawar.amin@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