News for hackers. Stuff that matters.
Re:Libcurl remote code execution by jlarocco on Friday February 08, 2013 @02:00AM (#5186672)
That's a silly thing to say.

All the networking code for Python, Ruby, Perl, Haskell, Java, Scala, Clojure, Erlang, and just about every other language in existence eventually makes calls to the sockets API, which is written entirely in C.

Where were the "Ruby is unfit for networking code" comments for all the recent Rails remote code execution exploits?

Lazy developers will write unsafe code in any language.

Re:Libcurl remote code execution by porlw on Friday February 08, 2013 @03:53AM (#5186949)
So the language should by default be safe, with extra effort required to perform unsafe operations. Then lazy programmers will write safe code!
Re:Libcurl remote code execution by stcredzero on Friday February 08, 2013 @01:07PM (#5189208)
We'll still have to deal with industrious but stupid ones.