From: Yawar Amin <yawar.amin@gmail.com>
To: Robert Muller <robert.muller2@gmail.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] ReasonML concrete syntax
Date: Sun, 17 Dec 2017 21:14:44 -0500 [thread overview]
Message-ID: <CAJbYVJKYUu_EvFfbB0W+4yxiyk5uwdttrZH714yLXb9a90zZig@mail.gmail.com> (raw)
In-Reply-To: <CAKmYinkgd=uz56oCEOxBGaKVNsNw8iDWt4aavD8R25p7=QCE2g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
On Sun, Dec 17, 2017 at 3:49 PM, Robert Muller <robert.muller2@gmail.com>
wrote:
> [...]
> Exactly! Reason may be great, but OCaml is effectively being expropriated
> by a huge, powerful organization.
>
Also, sorry, but this is pure hyperbole.
The Reason team has a select few people who have to, like any other tools
team, make the case to every potential internal client about why to use
their tool. They don't automatically get full Facebook backing just because
they exist. In fact, they have to compete against the much more well-known
Flow project for JavaScript type annotations. Their biggest win so far as
is they're migrating the Facebook Messenger webapp to Reason and are about
halfway there.
In fact they are tossing around the idea of building tools that
automatically display your OCaml code to you in your favourite syntax, so
you don't have to care about what others are using.
So it's far from a foregone conclusion that Reason syntax will take over
the OCaml ecosystem.
Regards,
Yawar
[-- Attachment #2: Type: text/html, Size: 1585 bytes --]
next prev parent reply other threads:[~2017-12-18 2:15 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 [this message]
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
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=CAJbYVJKYUu_EvFfbB0W+4yxiyk5uwdttrZH714yLXb9a90zZig@mail.gmail.com \
--to=yawar.amin@gmail.com \
--cc=caml-list@inria.fr \
--cc=robert.muller2@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