PHP 26 Apr 2012 05:00 pm
While there is no doubt PHP is broken beyond repair, it does have a few virtues that keeps it as one of my first choices when writing certain kind of web frontends and minor tools.
There is a huge laundry list of how PHP is broken at “PHP a fractal of bad design“, which I almost entirely agree with. What I will do here is point out the few things on that list that I do not agree with, and why.
The task: Write a portable tool that takes a file name as first argument, and from that file outputs the number of lines, the longest line, the length of the longest line, and the line number of the longest line, in a binary-safe fashion (meaning, \n is the only reason a line should be delimited; embedded \0s may occur).
My sinister side goal is showing how complex the C code has to be in order to get performance near C++. It is possible to write a simpler version in C that is 20% faster for /usr/share/dict/words, but it is then 4x slower for the random files. It would also be possible to write a faster non-portable version using memory mapping, but can’t really call that simple. C++ has both readability and speed. If I missed some obvious portable optimization in the C code, let me know…
The contestants are:
|Source||Version / Flags||Source Lines||Source Bytes|
|find-longest-line.c||gcc 4.3.2 -std=c99 -O3||77 lines||2410 bytes|
|find-longest-line.cpp||g++ 4.3.2 -O3||33 lines||964 bytes|
|find-longest-line.php||PHP 5.2.9||34 lines||751 bytes|
|find-longest-line.pl||Perl 5.10.0||31 lines||658 bytes|
|find-longest-line.py||Python 2.5.2 (provided by Kniht / Roger Pate)||22 lines||515 bytes|
|find-longest-line.cs||Mono 2.2 (provided by Windcape / Claus Jørgensen)||45 lines||1155 bytes|
Continue Reading »