[Ocaml-biz] limits, libraries, technical markets

[Brandon J. Van Every]

Brian Hurt wrote:
> The string size limitation that got
> brought up today in the main list is an example of this-
> the guy was
> wanting to read the entire file into a string.

Let's not chase markets where this commonly needs to be done.

> It is an educational problem, I agree.  But one that can be
> overcome with a good introductory book.

Only partly.  Much experience of a language is transmitted by people who
simply tried things out on the internet, without a book.  You can't
count on everyone knowing how to get around specific warts if they're
fundamental to the language.  The 'street cred' of the language becomes
"Well, I had all this trouble!"

> > and distribute
> > whitepapers that "OCaml didn't work" because they kept
> > getting bit in
> > the ass by various limits or library learning curves.
>
> I've not seen them for any other language- most notably,
> neither Java or
> C++.  Both of which have serious warts.

I've seen them for Python, in a paper about why a group switched to
Erlang.  Different issues, but whitepapers about language failure *are*
transmitted.  The failing language gets a footnote in a whitepaper about
a successful language.  As for what you've seen about Java and C++, we'd
be so lucky to be so popular to have so much command over people's
attention that it didn't matter.


Cheers,                     www.indiegamedesign.com
Brandon Van Every           Seattle, WA

"The pioneer is the one with the arrows in his back."
                          - anonymous entrepreneur