caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: hmf@inescporto.pt
To: caml-list@inria.fr
Subject: Re: [Caml-list] New Ocaml Plug-in for NetBeans
Date: Sat, 26 Jul 2008 13:44:25 +0100	[thread overview]
Message-ID: <1217076265.488b1c2947728@webmail.inescporto.pt> (raw)


Erik de Castro Lopo wrote:
> hmf@inescporto.pt wrote:
>
>
>> What I say here also goes for Richard. I am aware that a lot of time
>> has gone into learning these tools (20 years!). I am just saying that to
>> use IDEs also requires effort.
>
> I spent 35+ hours/week for 6 months on VS2005. Is that not enough
> time to learn it?
>

I guess it is.

>> Granted. But I am defending lowering the barrier for Ocaml use.
>
> If you are advocating IDE use for the purposes of making Ocaml
> easier for newcomers then you are in a bit of a bind. The
> people who need the IDE are the newcomers who are not capable
> of writing one and the ones with sufficient experience to write
> an Ocaml IDE are happy with what they have and are therefore
> not interested in writing one

Exactly! This is the reason why I sent the e-mail to this list in the
first place. No IDE will be useful unless seasoned users are prepared to
contribute to it.

 > (with the possible exception of
 > Jon Harrop).
 >

Because he also thinks that such IDEs makes his life easier.
I guess if the IDE was written in OCaml he would be an active
contributor. :-)






             reply	other threads:[~2008-07-26 12:45 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26 12:44 hmf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-26 12:01 hmf
2008-07-26 12:25 ` Erik de Castro Lopo
2008-07-26 15:37   ` Jon Harrop
2008-07-26  9:18 hmf
2008-07-26  9:22 ` Richard Jones
2008-07-26  9:02 hmf
2008-07-26  9:19 ` Richard Jones
2008-07-28  9:58   ` Florian Hars
2008-07-26 10:03 ` Erik de Castro Lopo
2008-07-26 11:40   ` Jon Harrop
2008-07-26 12:07     ` Erik de Castro Lopo
2008-07-26 15:22       ` Jon Harrop
2008-07-29 14:16         ` Damien Doligez
2008-07-29 14:30           ` Lukasz Stafiniak
2008-07-29 18:01             ` Jean-Christophe Filliâtre
2008-09-07 21:39     ` Nathaniel Gray
2008-07-26 11:42 ` Jon Harrop
2008-07-26  8:46 hmf
2008-08-20  6:29 ` Maxence Guesdon
2008-08-20 14:38   ` Richard Jones
2008-08-22  6:34     ` Maxence Guesdon
2008-08-20 16:32   ` Jon Harrop
2008-08-22  6:41     ` Maxence Guesdon
2008-09-07 23:31     ` Nathaniel Gray
2008-09-08  1:10       ` Jon Harrop
2008-09-09  5:31         ` Nathaniel Gray
2008-09-09  7:43           ` Jon Harrop
2008-09-09  7:50             ` Nathaniel Gray
2008-08-27 20:24   ` kirillkh
2008-09-02  6:49     ` Maxence Guesdon
2008-07-22 11:14 adonis28850
2008-07-23  8:42 ` hmf
2008-07-23  8:50   ` adonis28850
2008-07-25 23:56     ` Jon Harrop
2008-07-26  0:24       ` Erik de Castro Lopo
2008-07-26  2:57         ` Jon Harrop
2008-07-26 12:25           ` Romain Beauxis
2008-07-26  9:09       ` Richard Jones
2008-07-28 17:25         ` Pal-Kristian Engstad
2008-07-28 19:25           ` Jon Harrop
2008-07-26 18:12 ` adonis28850

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=1217076265.488b1c2947728@webmail.inescporto.pt \
    --to=hmf@inescporto.pt \
    --cc=caml-list@inria.fr \
    /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).