News for hackers. Stuff that matters.
Re:Ruby's Date/DateTime classes rewritten in C.. 20-200x per... by fauigerzigerk on Monday August 23, 2010 @01:06PM (#1627290)
Sure, and when I have chosen a good algorithm, I want to implement it in a language/runtime that is suitable for algorithmic code, not in Ruby or Python or PHP. To be able to do that is something I expect of myself and everyone I work with.
Re:Ruby's Date/DateTime classes rewritten in C.. 20-200x per... by msbarnett on Monday August 23, 2010 @01:59PM (#1627460)
Ruby and Python aren't suitable for "algorithmic code"? Is there any other kind?
Re:Ruby's Date/DateTime classes rewritten in C.. 20-200x per... by fauigerzigerk on Monday August 23, 2010 @02:19PM (#1627519)
It's obviously not a formal distinction. Algorithmic means "spends a lot of time running loops doing something interesting" as opposed to "copies data back and forth between the UI and the DB". Or CPU intensive versus IO intensive.

[Edit] And just to be completely clear and also reap all the downvotes that I can get from disgruntled web devs: Python and Ruby are indeed totally unsuitable for writing CPU intensive, complex algorithms. If you write Ruby or Python code, avoid loops! Try to be declarative so all the loops stay in the C code.