From: Gilles FALCON <gilles.falcon@orange-ftgroup.com>
To: Brian Hurt <bhurt@spnz.org>
Cc: Richard Jones <rich@annexia.org>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] The F#.NET Journal
Date: Thu, 19 Apr 2007 18:50:35 +0200 [thread overview]
Message-ID: <46279DDB.6020503@orange-ftgroup.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704181817460.30458@localhost>
Hello,
F# comes with a nice IDE, I think another IDE (as eclipse for ie)
could help people to come to ocaml.
Ocaml tools with Emacs are nice for strong programmer.
Just my two cents.
Gilles
Brian Hurt a écrit :
>
>
> On Wed, 18 Apr 2007, Richard Jones wrote:
>
>> On Tue, Apr 17, 2007 at 09:06:38PM +0100, Jon Harrop wrote:
>>>
>>> Flying Frog Consultancy just started the F#.NET Journal, an on-line
>>> publication composed of articles, example source code and tutorial
>>> videos
>>> aimed at beginner programmers learning the F# programming language from
>>> Microsoft Research:
>> [...]
>>
>> Does F# run on real operating systems? Does it have a full open
>> source stack?
>
> Overall, I see F# as a good thing for Ocaml. OK, it draws some of
> it's support from the Ocaml community (John Harrop here being an
> obvious example)- thus dilluting the pool of energy from Ocaml, at
> least in the short term. But any F# programmer can pick up Ocaml in
> short order, and vice versa (not unlike the C#/Java communities).
>
> But I think were F# will really draw it's people from is outside the
> community. It'll draw from the vast horde of C#/VB/C++ Windows
> programmers. Draw people from outside the community to inside the
> community. And sooner or later many of them are going to start
> looking for an F# that runs on Linux/Unix.
>
> Even if I'm wrong, even if F# is a net loss for Ocaml, I still can't
> help viewing F# as a good thing over all. Anything which helps
> programmers write code that doesn't *SUCK* is an advantage to us all-
> and every programmer coding in F# is a programmer not coding in C#,
> VB, or, God help us, C++. Making code proven free of large classes of
> bugs, and many other bugs rare indeed is a definate good. And
> bluntly, most software- free software as well as proprietary, sucks
> large rocks through very small pipettes.
>
> Just my two cents.
>
> Brian
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2007-04-19 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 20:06 Jon Harrop
2007-04-18 8:53 ` [Caml-list] " Richard Jones
2007-04-18 22:57 ` Brian Hurt
2007-04-19 0:04 ` skaller
2007-04-19 16:50 ` Gilles FALCON [this message]
2007-04-18 9:32 Robert Pickering
2007-04-18 10:11 ` Jon Harrop
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=46279DDB.6020503@orange-ftgroup.com \
--to=gilles.falcon@orange-ftgroup.com \
--cc=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/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).