caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Chris Hecker <checker@d6.com>
To: Issac Trotts <issac@myfirstlink.net>,
	OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Caml productivity.
Date: Fri, 26 Jul 2002 22:49:06 -0700	[thread overview]
Message-ID: <4.3.2.7.2.20020726223019.02b1f700@mail.d6.com> (raw)
In-Reply-To: <20020726224119.C671@boson.den.co.bbnow.net>


>There's already strong evidence that it's possible to use a higher
>level language to produce a successful console game: Naughty Dog's Scheme 
>dialect  (GOAL) on Jak & Daxter for the PS2.  They claim to have used it 
>for most  of the game.  One thing that isn't clear is how they avoided running
>out of memory from fragmentation.  Maybe Pal-Kristian Engstad can shed
>some light on this.

My understanding is that the ND stuff is for scripting.  I was talking 
about using caml for the main language, like I mentioned before.  I would 
doubt any of the renderer, animation, physics, core AI routines, core 
object management, control stuff, etc. were written in their language, but 
I would love to be wrong.  I would assume it fits the usual template (or 
maybe goes a bit farther because it's been used at ND for a long time, so 
they've got it very well integrated) for what a scripting language is used 
for in a game, which includes things like higher level AI decisions, traps 
and triggers, win conditions, cut scenes, weapons, UI, etc.  It may be that 
"most" of the code by LOC is in the scripting language, and that's fine 
(although I'd be somewhat surprised, especially if all the VU code is 
included in the count), but my guess is it isn't the "core language".

Having this conversation about the PS2 is kind of ludicrous anyway, since 
it's such a mess, it's hard to even say what language a game is written in.

>In contrast, a game company would take a big productivity hit in the short run

My point is that 3x is simply HUGE for a commercial programming 
effort.  It's easily big enough to overcome inertia and make people switch, 
even if they had a year of downtime...heck, you could make up that year in 
4 months, and then the rest of your ship cycle would happen at 3x the 
rate!  If people could consistently get anywhere close to 3x on most 
programs then everybody would switch quickly.

Anyway, it would be nice if there was more data on this.  I'd love it if 
caml made people 3x more productive on most problems (including, hopefully, 
myself :), I just find it very hard to believe.  Sadly, it's hard to get 
rigorous controlled experiments in this area.

Chris


-------------------
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:[~2002-07-27  5:53 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15 21:22 Pal-Kristian Engstad
2002-07-20 15:16 ` William Chesters
2002-07-22 18:22   ` Pal-Kristian Engstad
2002-07-22 18:41     ` achrist
2002-07-22 19:23       ` Pal-Kristian Engstad
2002-07-22 21:13         ` [Caml-list] CamlIDL and function pointers Michael Tucker
2002-07-23  8:39           ` Xavier Leroy
2002-07-23 13:11             ` Dmitry Bely
2002-07-24 15:00             ` Michael Tucker
2002-07-25  9:36               ` Xavier Leroy
2002-07-22 21:26     ` Games (Re: [Caml-list] Caml productivity.) Oleg
2002-07-23  2:56       ` Issac Trotts
2002-07-23 11:03         ` eijiro_sumii
2002-07-23 16:17           ` Charles Martin
2002-07-29  3:36           ` Andrei de A. Formiga
2002-07-29  6:32             ` Florian Hars
2002-07-29 10:23             ` eijiro_sumii
     [not found]               ` <001901c237a7$9e685920$890bfea9@mimbi>
2002-07-30  4:52                 ` eijiro_sumii
2002-07-30 18:13                   ` Jonathan Coupe
2002-07-30  6:16                     ` eijiro_sumii
2002-08-01 15:39                     ` John Max Skaller
2002-08-01 15:59                       ` Markus Mottl
2002-08-01 16:28                       ` Jonathan Coupe
     [not found]                         ` <86vg6ta9o6.fsf@laurelin.dementia.org>
2002-08-02 12:50                           ` Jonathan Coupe
2002-08-02 14:51                         ` John Max Skaller
2002-07-25  3:19       ` Chris Hecker
2002-07-28 13:45         ` Jonathan Coupe
2002-07-29  0:57           ` Michael Vanier
2002-07-22 22:00     ` [Caml-list] Caml productivity Alexander V.Voinov
2002-07-20 15:25 ` Oleg
2002-07-22  6:41 ` Tom
2002-07-22 10:46 ` Nicolas Cannasse
2002-07-22 17:46   ` Pal-Kristian Engstad
2002-07-24  3:20     ` Travis Bemann
2002-07-24  9:45       ` Pal-Kristian Engstad
2002-07-26 21:42         ` Chris Hecker
2002-07-27  4:41           ` Issac Trotts
2002-07-27  5:49             ` Chris Hecker [this message]
2002-07-27 14:49               ` John Max Skaller
2002-07-27  9:06           ` Oleg
2002-07-27 18:18             ` Chris Hecker
2002-07-29  8:13         ` Nicolas Cannasse
2002-07-30  4:46           ` Travis Bemann
2002-07-24  8:02     ` Nicolas Cannasse
2002-07-24  8:25       ` Jérôme Marant
2002-07-24 10:00       ` Pal-Kristian Engstad
2002-07-27  9:06         ` Oleg
2002-07-23  2:08 Arturo Borquez

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=4.3.2.7.2.20020726223019.02b1f700@mail.d6.com \
    --to=checker@d6.com \
    --cc=caml-list@inria.fr \
    --cc=issac@myfirstlink.net \
    /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).