Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Yotam Barnoy <yotambarnoy@gmail.com>
To: jeff tansley <jeff.tansley@btinternet.com>
Cc: brian.e.mulhall@gmail.com, Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Networking Application
Date: Mon, 22 Sep 2014 12:39:58 -0400	[thread overview]
Message-ID: <CAN6ygOm+oAaa6KbBm8psChLPSw08c3OzQ0ZWyKgxuQZENx74ow@mail.gmail.com> (raw)
In-Reply-To: <000b01cfd67e$c48cf830$4da6e890$@btinternet.com>

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

Wow. Those are some harsh words, Jeff. Honestly, I don't see where you're
coming from with these comments.

What I would tell Brian though is the following: with 6 months of
experience in ocaml, you may not have the ability to sell ocaml and its
functional paradigm to a company that has a preconceived notion of what
programming should be like. You'll encounter some difficulties - the same
as with any language - and without the experience to deal with these
hiccups, it'll be tough to convince your bosses to shift to a different way
of thinking about programming. Tough, but doable.

-Yotam

On Mon, Sep 22, 2014 at 12:03 PM, jeff tansley <jeff.tansley@btinternet.com>
wrote:

> Hi Brian,
>
> Simple real advice - forget it - unless you are trying to get yourself
> fired.
> Whatever might be said on this list you will only be adding to what I
> suspect is a bit of a software nightmare. Unless of course you have the
> management power and intellect to tidy this up first but if this were the
> case you wouldn't be mailing this list.
> Just understand the stuff that Yaron points you at and look for another
> appointment.
>
> JBT
>
> -----Original Message-----
> From: caml-list-request@inria.fr [mailto:caml-list-request@inria.fr] On
> Behalf Of brian.e.mulhall@gmail.com
> Sent: 22 September 2014 12:55
> To: caml-list@inria.fr
> Subject: [Caml-list] Networking Application
>
> Hello All,
>
> I work for a large US engineering firm and I am trying to find a way for
> our
> team to do more with less, due to budgetary cutbacks in our engineering
> center.
>
> With that being said we have an existing java application that is in dire
> need of a rewrite. I have been interested in ML and subsequently OCAML for
> about 6 months and I am now looking for a way to integrate this passion of
> mine into my work life. I see very real benefits from using this language
> at
> work and its also applicable in our use case (we have a single core machine
> with limited resources and I want us to use a cooperative threading library
> like LWT or Async).
>
> So I was wondering if people could point me in the direction of some open
> source projects hosted on github that I can read through and try to emulate
> in my proof of concept, sketch of a redesign that I show my supervisors. I
> appreciate any help and since this is a side project it can be done right,
> without any need to take hacky shortcuts.
>
> --
> 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
>
>
> --
> 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
>

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

  reply	other threads:[~2014-09-22 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 11:55 brian.e.mulhall
2014-09-22 13:19 ` Yaron Minsky
2014-09-22 13:52 ` Siraaj Khandkar
2014-09-22 16:03 ` jeff tansley
2014-09-22 16:39   ` Yotam Barnoy [this message]
2014-09-22 16:25 ` Xavier Leroy

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=CAN6ygOm+oAaa6KbBm8psChLPSw08c3OzQ0ZWyKgxuQZENx74ow@mail.gmail.com \
    --to=yotambarnoy@gmail.com \
    --cc=brian.e.mulhall@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=jeff.tansley@btinternet.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