nLeyten: Recent Comments

Comment on Nleyten@1400: Netplexing

2009-09-06T18:57:38Z

Concerning Lwt, do you have any idea of how to incorporate code built upon ocamlnet's equeues and unixqueues into an eliom module?

Can it be done?

Comment on Ocsigen by example, Part 1: basic setup

2009-05-11T14:22:11Z

Is there way to develop applications without rebooting ocsigen at every change in code?

Comment on Ocsigen by example, Part 4: suffix parameters

2009-05-06T13:55:25Z

Very interesting blog entry! I did not know that it was possible to use typed parameters with suffixes.

Yours,
d.

Comment on Ocsigen by example, Part 5: GET forms

2009-03-23T14:03:59Z

Many thanks for these posts.

Comment on Nleyten@1500,1600: Lambdoc takes shape

2008-09-24T03:31:13Z

> capitalism is inherently flawed

Yes, but less flawed than any other economic system humans have ever come up with.

Europe is also capitialist but seem quite good at controlling the excesses of capitalism that the US seems to be unwilling to control.

with nothing to back

Comment on Use Ocaml, save the world

2008-08-09T21:21:48Z

Hi, Well, when performance matters, simply use native code! As you noted, with Ocaml 3.10, it is not possible to dynamically load libraries when using native code. However, version 3.11 fixes this, so there's nothing holding you back...

Comment on Simple benchmarks on the Ocsigen server

2008-08-09T21:11:46Z

Hi Ben,

You can use either bytecode or native-code, but whichever your choice, all components must be using the same mode, because you cannot mix bytecode and native code.

Comment on Simple benchmarks on the Ocsigen server

2008-08-07T14:36:52Z

This is 100% completely usefull information. As newbie I still have some questions. When you talk of bytecode vs native compiled do you mean
- the ocsigen environment?
- the eliom framework?
- your application?

Comment on Use Ocaml, save the world

2008-08-07T14:30:00Z

interesting article. One question though: I think when you speak on Ocamls performance you always mean native compiled programs right? Isn't there a problem regarding bigger applications because there you often have to load libraries? For example mod_caml or the ocsigen webserver isn't this bytecode compiled? In the shout out example you refering to, Ocaml comes after ruby if compiled to bytecode! http://shootout.alioth.debian.org/debian/benchmark.php?test=all&lang=all&calc=Calculate&xfullcpu=1&xmem=0&xloc=5&binarytrees=1&chameneosredux=1&fannkuch=1&fasta=1&knucleotide=1&mandelbrot=1&nbody=1&nsieve=1&nsievebits=1&partialsums=1&pidigits=1&recursive=1®exdna=1&revcomp=1&spectralnorm=1&hello=0&sumcol=1&threadring=1

Comment on Use Ocaml, save the world

2008-05-24T09:29:54Z

You should also take into consideration "how much the language is able to be understood and processed by a computer". In other word, how much lines of the written program can be reprocessed by a computer to produced a more energy efficient version for example.

This is a general "legacy code" problem. For example, COBOL is not a regular language and there is at least 10 to 20% of written COBOL code that need to be reprocessed by hand to migrate the code from a mainframe to a UNIX, for example. The cost of this migration is directly proportional to the time spent to write the initial program. For 10% of lines not understood in the initial program, you will spent ~15% of the initial time to rewrite your program.

This parameters should be taken into account using "computer tersness" of the language, ability to find efficient programmers and number of bugs left in the code.

"computer tersness" defines how much a computer reading your code will understand your aim...

Sylvain Le Gall
(not so tongue in cheek)