News for hackers. Stuff that matters.
Re:The "C is Efficient" Language Fallacy by gaius on Tuesday May 05, 2009 @02:37AM (#593757)
That is a false dilemma tho'. No-one in the Python world has anything invested in a 100% Python solution to anything. Doing the compute-intensive bits in C is in fact expected and encouraged! The same is true in the Tcl camp. Maybe some HLL communities (Java?) like to be "pure" but I've not ever encountered that.
Re:The "C is Efficient" Language Fallacy by robin_reala on Tuesday May 05, 2009 @07:55AM (#593950)
No-one in the Python world has anything invested in a 100% Python solution to anything

PyPy? http://codespeak.net/pypy/dist/pypy/doc/

Re:The "C is Efficient" Language Fallacy by gaius on Wednesday May 06, 2009 @05:30AM (#595473)
That's not for production use, tho'.
Re:The "C is Efficient" Language Fallacy by wlievens on Tuesday May 05, 2009 @05:35AM (#593868)
Java communities typically favor portability (and easy deployment) over what you can gain in terms of speed. A lot of libraries/frameworks actually even advertise themselves as "100% pure java", whereas one might expect "expensive bits optimized in C" as attractive as well (but you rarely see it).
Re:The "C is Efficient" Language Fallacy by brl on Tuesday May 05, 2009 @02:33PM (#594495)
> whereas one might expect "expensive bits optimized in C"

There is no important difference in performance between C and Java according to http://shootout.alioth.debian.org/

Re:The "C is Efficient" Language Fallacy by wlievens on Wednesday May 06, 2009 @03:48AM (#595398)
That all depends on the kind of code, of course.
Re:The "C is Efficient" Language Fallacy by tptacek on Tuesday May 05, 2009 @03:01AM (#593772)
I agree. I like writing my goop in Ruby. But that's not what the article is about.