From: Goswin von Brederlow <goswin-v-b@web.de>
To: Yotam Barnoy <yotambarnoy@gmail.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Flambda/compiler walkthrough + modularity
Date: Mon, 14 Mar 2016 11:36:08 +0100 [thread overview]
Message-ID: <20160314103608.GB21595@frosties> (raw)
In-Reply-To: <CAN6ygOn162G1rV7bv=UvgyCAt8VxhzRNoVKubWd1_Ws8cCLOLw@mail.gmail.com>
On Fri, Mar 11, 2016 at 12:04:17PM -0500, Yotam Barnoy wrote:
> While thinking about the best way to learn the new Flambda code in the
> minimal amount of time, I thought to myself, "wouldn't it be amazing to
> have Pierre Chambart and Mark Shinwell just do a video walkthrough of their
> code". And then I thought about the rest of the codebase, about Jacques
> Garrigue doing a walkthrough of the typechecker code, and each expert(s)
> talking about the parts they know really well, and about how amazing it
> would be if we had this resource on youtube. It would be the ultimate form
> of documentation by the foremost experts on aspects OCaml, welcoming
> programmers to contribute to the OCaml compiler in the easiest way possible.
>
> A step further would be if this was done on Twitch or some similar live
> broadcasting platform, so people could actually ask live questions as the
> session took place. The resulting video would be posted to youtube.
>
> What do you guys think?
>
> -Yotam
I would watch that.
MfG
Goswin
next prev parent reply other threads:[~2016-03-14 10:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 17:04 Yotam Barnoy
2016-03-14 7:27 ` Mark Shinwell
2016-03-14 10:36 ` Goswin von Brederlow [this message]
2016-03-14 12:30 ` Gabriel Scherer
2016-03-14 13:51 ` Yotam Barnoy
2016-03-14 20:31 ` Hendrik Boom
2016-03-14 21:00 ` Yotam Barnoy
2016-03-14 21:05 ` Junsong Li
2016-03-15 1:02 ` Gabriel Scherer
2016-03-16 2:12 ` Junsong Li
2016-03-18 15:15 ` [Caml-list] <DKIM> " Pierre Chambart
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=20160314103608.GB21595@frosties \
--to=goswin-v-b@web.de \
--cc=caml-list@inria.fr \
--cc=yotambarnoy@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).