Browse thread
[Caml-list] GC and file descriptors
-
Dustin Sallings
- David Fox
- Nicolas George
- Mikael Brockman
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2003-11-17 (23:03) |
From: | John J Lee <jjl@p...> |
Subject: | Re: [Caml-list] GC and file descriptors |
On Mon, 17 Nov 2003, Brian Hurt wrote: [...] > The O'Reilly book will be a great benefit. Let me know when it comes out, It's coming out in print? Great! > I want a copy. But I don't know how close to mainstream it is. Perl, > Python, and Ruby are scripting languages, still mainly used for short, > single-person, throw-away projects. The fact that they're often *used* in that way doesn't preclude their use as applications languages -- far from it: they shine in that department (though I put Perl in a different category, not for any fundamental reason, but simply because it's so outrageously, unjustifiedly complicated). Perhaps O'Caml has even *more* to offer there, but dismissing Ruby & Python as "scripting" languages seems silly to me. People who write good unit tests (and even, which amazes me, people who don't) report very significant productivity improvements for applications of 10k or more when compared with Java and C++. They certainly don't even begin to have scaling problems at that point that aren't also present in Java and C++ (especially when you consider that lines of code are fewer in these languages than in poor-static-typing languages like Java). > And they aren't that far from "conventional" languages (think Perl and > Shell, Python/Ruby and Java). True in some ways. That certainly doesn't mean there isn't a very significant difference in productivity between the two groups, though ("traditional" and Python / Ruby -- with the caveat that I've never used Ruby, so can't comment on it). > Ocaml is more of an applications language- it's benefits start to really > shine when you're looking at tens of thousands (or more) lines of code. > C++ succeed (and Objective-C and Smalltalk didn't) because you could write > C in it. Java succeeded because IBM, Sun, Oracle, and a number of other > huge companies got behind it. [...] John ------------------- 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