Slashdot Mirror
Thinking about Rails? Think Again
wolfeon writes "In 2005, Derek Sivers of CD Baby wanted to scrap his site and perform a rewrite in Rails. He hired Jeremy Kemper, also known as bitsweat on Freenode, to help on the project. Two years later, through blood and sweat, the project was then canceled because of limitations of Rails. Rails just wasn't meant to do everything since it is very much "canned" project. Mr. Sivers has written an entry in the O'Reilly blog: 7 reasons I switched back to PHP."
But if all my l337 friends are using a screwdriver to pound in a nail, doesn't that mean I'm obliged to follow them?
I am very tempted to use the "You must be new here"
Slashdot summaries are always written like this. I don't know if the editors/submitters do not understand the point of the article they are linking to, or if said editors/submitters are so biased that they want to prove another point, using that article.
I submit to you, my fellow slashdotters, the parent post for the most ironic post ever. Such a long, insightful post about how to do a successful software deployment, and then not clicking preview to realize that the formatting of your list is all screwed up. Only posting as an A/C saved you a year of personal shame.
...and I found the keys to a Porche at the bottom of her vagina.
Ow.
It's better to vote for what you want and not get it than to vote for what you don't want and get it.
- E. Debs
A colleague has been learning Common Lisp and is using SBCL and it has cored on him more than a few times in the past few weeks. According to him Common Lisp is great but SBCL is not production ready and there is no free Common Lisp that is, so if we are to use a Lisp it'll probably have to be something like Allegro.
;).
/dev/null) for daemons/servers because daemons aren't supposed to output stuff". While I do agree that daemons aren't normally supposed to send stuff out via STDOUT and STDERR, that is exactly why I want such output to go to syslog (or the equivalent)! Believe me it has been helpful. Even if your code has no bugs that show up that way, you could find bugs in 3rd party libs that you use ;).
I also did try learning CL, but I personally found it hard to find out how to write production code in Lisp - most of the examples on the web are all very nice for CS stuff (e.g. run this from emacs via slime) , but not real world stuff. While you're strictly in the Lisp world everything is nice and all that - 101 ways to do "fibonacci" etc, but seems like the lisp docs are written by people who are so much smarter than I am that they probably find a lot of things so obvious that they don't list them in FAQs
Example questions I asked:
How do you compile and make an SBCL program executable? (I know now, but still...).
How do you trap and handle posix/unix signals? (not sure the ways I found are best practice)
How do you redirect STDOUT and STDERR to syslog?[1]
Any examples of production style boilerplate code?
How do I write a program that listens on UDP port X on all interfaces for packet and know which interface each packet came in from?
I'm currently using Perl and it is a lot slower than sbcl but so far it hasn't cored on me for a long while. With the exception of the last item the above sort of things are also easy or not too hard to find out (just man perlipc gives a lot of real world details).
I would like to learn a _fast_ high level language AND be able to use it to write production grade code (and no, I don't regard Java as high level, even if you program your java program to do XML and reinvent lisp badly).
[1] I do this for most of my programs. I disagree with people who say "STDOUT and STDERR should be closed (or sent to
I usually try to get it prefixed by the program name and PID (or parent PID) e.g.
Sep 22 03:07:16 host progname[1312] STDOUT: <std output here>
Sep 22 03:07:17 host progname[1312] STDERR: <std err here>
Old dog. New trick.