From: John Max Skaller <skaller@ozemail.com.au>
To: Markus Mottl <mottl@miss.wu-wien.ac.at>
Cc: "Joseph R. Kiniry" <kiniry@acm.org>, OCAML <caml-list@inria.fr>,
Mattias Waldau <mattias.waldau@abc.se>
Subject: Re: JIT-compilation for OCaml?
Date: Tue, 09 Jan 2001 18:14:53 +1100 [thread overview]
Message-ID: <3A5ABA6D.D5EFA9FD@ozemail.com.au> (raw)
In-Reply-To: <20010103195832.A30893@miss.wu-wien.ac.at>
Markus Mottl wrote:
> It's sad that it is still so difficult to attract investors to modern
> (as opposed to "new") technologies. OTOH, it is understandable that they
> are reluctant if they know that you are likely to have problems hiring
> or training staff (-> higher costs = less profit).
At least in Australia, almost all computer science courses
include functional and logic programming as topics.
Furthermore, programmers are _intelligent_ organisms:
they can learn new languages. And since Ocaml is
so much more efficient to develop with, the savings in programmers
would easily offset any extra time required to learn it. IMHO. :-)
The problem is one of hype and marketing.
> I do not really follow your concerns about Open Source: OCaml is pretty
> "free" as are most other FPLs. Or do you mean something else?
Consider the following note included in the 'wlex' README:
-----------------------------------------------------------------------
NOTE
* The lexer generator is derived from ocamllex; due to licence issues
* (this part of the OCaml system is distributed under the terms of the
* QPL), I have to distribute it as a patch. This imply you will need
* the whole OCaml source tree to build wlex. If you experience any
* problem to apply the patch, please don't hesitate to contact me.
-----------------------------------------------------------------------
Please compare to the Python licence, which is unequivocal:
Python is FREE FOR ANY USE. [Its that simple]
--
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net
next prev parent reply other threads:[~2001-01-09 9:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 16:07 Markus Mottl
2001-01-02 18:16 ` Mattias Waldau
2001-01-02 19:30 ` Markus Mottl
2001-01-03 12:15 ` Alain Frisch
2001-01-04 8:37 ` Fabrice Le Fessant
2001-01-04 9:04 ` Alain Frisch
2001-01-03 13:23 ` Mattias Waldau
2001-01-03 14:25 ` Markus Mottl
2001-01-03 14:40 ` STARYNKEVITCH Basile
2001-01-03 15:51 ` John Max Skaller
2001-01-03 17:50 ` Markus Mottl
2001-01-05 0:30 ` Michael Hicks
2001-01-08 9:59 ` Xavier Leroy
2001-01-09 6:40 ` John Max Skaller
2001-01-03 17:49 ` Joseph R. Kiniry
2001-01-03 18:19 ` Markus Mottl
2001-01-03 18:38 ` Joseph R. Kiniry
2001-01-03 18:58 ` Markus Mottl
2001-01-03 19:06 ` Joseph R. Kiniry
2001-01-04 22:32 ` Jonathan Coupe
2001-01-07 0:16 ` Chris Hecker
2001-01-05 12:52 ` Sven LUTHER
2001-01-05 20:08 ` Joseph R. Kiniry
2001-01-09 7:14 ` John Max Skaller [this message]
2001-01-09 6:50 ` John Max Skaller
2001-01-05 12:39 ` Sven LUTHER
2001-01-05 5:48 ` Vitaly Lugovsky
2001-01-03 15:24 Jerry Jackson
2001-01-04 14:12 ` Alan Schmitt
2001-01-09 17:09 Dave Berry
2001-01-11 6:38 ` John Max Skaller
2001-01-09 17:18 Dave Berry
2001-01-11 7:00 ` John Max Skaller
2001-01-11 10:01 ` Alain Frisch
2001-01-12 7:55 ` John Max Skaller
2001-01-11 12:45 Dave Berry
2001-01-12 8:23 ` John Max Skaller
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=3A5ABA6D.D5EFA9FD@ozemail.com.au \
--to=skaller@ozemail.com.au \
--cc=caml-list@inria.fr \
--cc=kiniry@acm.org \
--cc=mattias.waldau@abc.se \
--cc=mottl@miss.wu-wien.ac.at \
/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).