caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mikhail Fedotov <mikhail@kittown.com>
To: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
Cc: caml <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml growing pains
Date: Thu, 12 Aug 2004 18:58:13 +0400	[thread overview]
Message-ID: <411B8585.7000507@kittown.com> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDOEFJHGAB.vanevery@indiegamedesign.com>

Hi,

Brandon J. Van Every wrote:

>Xavier Leroy wrote:
>  
>
>>Some of your recent Usenet
>>postings left me shaking my head in disbelief, not knowing whether to
>>laugh or cry.
>>    
>>
>
>I was going to reply privately, taking this comment of yours in stride.
>I was composing my reply inline, dealing with some industrial growth
>issues.  When I got farther down in your post, I realized how nasty your
>response actually was, and how disinterested you are in some things I'm
>interested in.  I don't take public nastiness sitting down, so here's my
>reply.
>
>  
>
Good points below, but it seems you are loosing a major one: you *never* 
can promote/advance
the langauge while going *against* its authors. (You can fork if of 
course, but then you'll be on
your own.)

When you are going against authors and mainters of some tool, it takes 
time. Your time. Their time.
The net result is the flame; good ideas are usually expressed in the 
beginning of discussion but
rarely developed any further.

That's one bad side, but there is another one which is even worse. While 
spending all time on
sorting out offences and stuff, you are not only loosing any chance to 
do anything good, but you
even do not know if you are actually able to help (read: develop trivial 
ideas like "community
should grow" into something implementable and implement them *without* 
going against tool
authors and maintainers, choose proper style and attitude for messages 
in *tech* list etc).

In addition, when all feedback from major players that you are receiving 
is negative, it means
that you are going in the wrong direction and for some reason fail to 
change it into the right one.

The net result may be that you become an expert at offences (and 
excuses) but can not do
anything when you have noone to battle with (i.e. when the real work 
starts). Been there myself,
lost a lot of time.

>- people visit Seattle from other cities and move there
>- people need motives to come to meetings, i.e. location, parking, beer
>- establishing critical mass in tech hubs is important to language
>growth
>- when other cities finally want to do it, they know who to contact
>- repetition is the key to all learning
>- announces every 3 weeks aren't anything out of anyone's life
>- those that don't care can skip it upon reading the subject line
>
>This is called getting things done.  Where's your index of local user
>groups?  Where are the announces?  There is nothing at
>http://caml.inria.fr at all.  What transmission vehicle if not
>caml-list?
>
>  
>

The most obvious is http://www.ocaml.org - it does not seem to be 
maintened anymore ( no mention
of 3.08 release), so *maybe* you have the chance to become the 
maintainer if you ask the
right people. Then you'll be able to show that you can do. :)

>// return an array of 100 packed tuples, just in case
>temps
>  int $[tvar0][2*100]; // what the c function needs
>  value $[tvar1]; // one int
>  value $[tvar2]; // one tuple
>  int $[tvar3] // loop control var
>oncePre
>eachPre
>  $[cvar0]=&($[tvar0][0]);
>eachPost
>  $[lvar0] = alloc(2*100, 0 /*NB: zero-tagged block*/ );
>  for(int $[tvar3]=0;$[tvar3]<100;$[tvar3]++) {
>    $[tvar2] = alloc_tuple(2);
>    $[tvar1] = Val_int($[cvar0][0+2*$[tvar3]]);
>    Store_field($[tvar2],0,$[tvar1]);
>    $[tvar1] = Val_int($[cvar0][1]);
>    Store_field($[tvar2],1,$[tvar1+2*$[tvar3]]);
>    Array_store($[lvar0],$[tvar3],$[tvar0]);
>  }
>oncePost
>  
>

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-08-12 14:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11  4:45 [Caml-list] Who controls INRIA mailserv filters? Brandon J. Van Every
2004-08-11  6:53 ` Diego Olivier Fernandez Pons
2004-08-11 20:29   ` Brandon J. Van Every
2004-08-11 21:22     ` don groves
2004-08-11 21:26       ` don groves
2004-08-12  7:36         ` Brandon J. Van Every
2004-08-12  7:50           ` Sven Luther
2004-08-12  8:28     ` Diego Olivier Fernandez Pons
2004-08-12  9:22       ` Brandon J. Van Every
2004-08-12  9:28 ` Xavier Leroy
2004-08-12 12:59   ` [Caml-list] OCaml growing pains Brandon J. Van Every
2004-08-12 14:58     ` Mikhail Fedotov [this message]
2004-08-12 21:30       ` Brandon J. Van Every
2004-08-13  6:05         ` skaller
2004-08-13  7:07           ` Brandon J. Van Every
2004-08-13  8:52         ` Mikhail Fedotov
     [not found] <20040812141309.GA19858@quick.recoil.org>
2004-08-12 20:48 ` Brandon J. Van Every
2004-08-12 23:46   ` Anil Madhavapeddy
2004-08-13  5:43     ` Brandon J. Van Every

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=411B8585.7000507@kittown.com \
    --to=mikhail@kittown.com \
    --cc=caml-list@inria.fr \
    --cc=vanevery@indiegamedesign.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).