mfp

5 ms·

1.
by mfp 17y ago
The new module organization avoids collisions with existing libraries like Extlib while allowing you to link Batteries' modules selectively, thus decreasing the size of the generated executables. For convenience, all the modules are also av
2.
by mfp 18y ago
What is needed to make something a "real" web framework? Ocsigen/Eliom does handle sessions, routing, page parameters, forms, continuation-based sites, templating and other things you'd expect from a web framework. The main thing Rails incl
3.
by mfp 18y ago
It's just that the hardware threads are slow, I think --- compiling stuff on the T2K also took forever. It also seems to me that there's seemingly little value in having 4 threads per core: it forces you to parallelize programs that ran fin
4.
by mfp 18y ago
IO was only (barely) disk-bound when you gave a full core to the reader (i.e., you have to be careful not to use HW threads on the same core). This is not a problem specific to OCaml --- I reproduced it with a standalone program written in
5.
by mfp 18y ago
"The ruby version is single threaded and the test is on a 32 core workstation (counting CPU time Python is only 4x faster and OCaml is only 17x faster)" I mentioned that on my blog. I also have an OCaml version that is 25x faster in CPU tim
6.
by mfp 19y ago
OT: According to wikipedia, the PAVE PAWS phased array operates in the 420-450 MHz UHF range, with a corresponding wavelength of 66cm; if the error margin is really 0.1*lambda, the system is built to a precision of 6cm, significantly easier
7.
by mfp 19y ago
The code has grown and become more complex in the last versions because I optimized it until directory traversal + glob matching got sensibly faster than Git's own (git-ls-files --exclude-standard doesn't do exactly the same thing as find-g
8.
by mfp 19y ago
Good find. I don't see how this keeps OCaml "from being a first choice for server-side development" while making it an acceptable language for client-side development, though. There are a several hackish polymorphic print implementations, b
9.
by mfp 19y ago
Maybe the lack of parallelism in OCaml's threads at the time he wrote that? There are now at least two solutions to obtain speedups on multi-core and multi-processor machines plus scalability by allowing seamless distributed processing: t
10.
by mfp 19y ago
" I also like the idea of an extensible grammar (and syntax too, right?)" Yes, that's what I meant (you change the grammar, resulting in new syntax). Some examples of what you can do with camlp4: http://martin.jambon.free.fr/pa_memo.ml al
11.
by mfp 19y ago
I've written between 50 and 100KLoCs of OCaml code over the last year (before that, I did mostly C and Ruby, which I've been using since 2002; touched many other languages but never did anything significant, over 5-10,000 lines with them).
12.
by mfp 19y ago
... but they use OCaml to prove that there are no run-time errors (RTE) in their code :-) http://www.astree.ens.fr/ "In Nov. 2003, ASTRÉE was able to prove completely automatically the absence of any RTE in the primary flight control sof