Cited from http://learnpythonthehardway.org/book/ex50.html : "Other Python programmers will warn you that lpthw.web is just a fork of another web framework called web.py, and that web.py has too much "magic". If they say this, point out to them that Google App Engine originally used web.py and not a single Python programmer complained that it had too much magic, because they all worked at Google. If it's good enough for Google, then it's good enough for you to get started. Then, just get back to learning to code and ignore their goal of indoctrination over education."
Hmmm... I remember times when Guido v.Rossum, Tim Peters and others were working at a company called BeOpen.com... may this shows my age.
We (my company) deliver servers to printing houses in europe, asia and even to the US. Okay: We have had some trouble with reiserfs in the early days (this was with Linux 2.2.14).
I have never experienced serious trouble with systems from 2.4.18 and up that was not caused by a hardware failure. Even than: With reiserfsck --rebuildtree volume it was sometimes possible to recover from some of the damage caused by disk read failures.
Of course I've to admit that 80% of our customers run SuSE Linux and the SuSE kernels always differed somehow from the official http://kernel.org/ kernels.
The performance gain of reiserfs compared to ext3 makes a big difference in our application area. I'm looking forward to find some time evaluating reiser4 and I like the work of Hans Reiser.
AFAIK this #!/usr/bin/env trick originated in the Python universe. May be that the python people care more about portability and thus produce clever ideas like this one.;-)
Slashdot Mirror
Cited from http://learnpythonthehardway.org/book/ex50.html :
"Other Python programmers will warn you that lpthw.web is just a fork of another web framework called web.py, and that web.py has too much "magic". If they say this, point out to them that Google App Engine originally used web.py and not a single Python programmer complained that it had too much magic, because they all worked at Google. If it's good enough for Google, then it's good enough for you to get started. Then, just get back to learning to code and ignore their goal of indoctrination over education."
Hmmm... I remember times when Guido v.Rossum, Tim Peters and others were working at a company called BeOpen.com ... may this shows my age.
If you are happen to use Debian GNU/Linux you are used to type followed by every once in a while. Works pretty nice and I only once had
a broken Firefox, which was fixed soon.
I think these volunteers Martin Schulze, Michael Stone and all the others
do a phantastic job here.
I like to say Thank you to them here in public!
We (my company) deliver servers to printing houses in europe, asia and even to the US. Okay: We have had some trouble with reiserfs in the early days (this was with Linux 2.2.14).
I have never experienced serious trouble with systems from 2.4.18 and up that was not caused by a hardware failure. Even than: With reiserfsck --rebuildtree volume it was sometimes possible to recover from some of the damage caused by disk read failures.
Of course I've to admit that 80% of our customers run SuSE Linux and the SuSE kernels always differed somehow from the official http://kernel.org/ kernels.
The performance gain of reiserfs compared to ext3 makes a big difference in our application area. I'm looking forward to find some time evaluating reiser4 and I like the work of Hans Reiser.
AFAIK this #!/usr/bin/env trick originated in the Python universe. May be that the python people care more about portability and thus produce clever ideas like this one. ;-)