Re:What's Going On (on "Why Python, Ruby, and Javascript are...
by coldtea on Sunday April 14, 2013 @06:49AM
(#5546569)
>I think that's kinda the point; rewriting critical sections in C is pretty much Working As Intended. That's why it's a scripting language.
No, it's pretty much not "Working As Intended".
It's just "Working as we have been used to, because, well, what can you do?".
As V8, IonMonkey, Dart, Smalltalk VMs, LuaJIT, even PyPy etc have showed, nothing prevents Python from being an order of magnitude faster (and sometimes up to two), while remaining just as dynamic.
Rewriting parts of a Python program in C is not a technical necessity due to some (unsurmountable) theoretical limit. It's a technical necessity because of a non optimal interpreter implementation.
Re:What's Going On (on "Why Python, Ruby, and Javascript are...
by pekk on Sunday April 14, 2013 @10:29AM
(#5546949)
It isn't a necessity at all. It's an available option.
How would you write PyPy to be "an order of magnitude faster"?
Re:What's Going On (on "Why Python, Ruby, and Javascript are...
by fauigerzigerk on Sunday April 14, 2013 @05:29AM
(#5546439)
Do you think that most Python developers can write safe C code? I doubt it but I have no data on it either.
Re:What's Going On (on "Why Python, Ruby, and Javascript are...
by nilliams on Sunday April 14, 2013 @05:38AM
(#5546459)
A fairly moot point. Do you think most C developers can write safe C code? The 2 I've encountered in my short career basically have no idea what they're doing (which I suspect is partly why they stuck with C instead of exploring alternative languages).
Re:What's Going On (on "Why Python, Ruby, and Javascript are...
by fauigerzigerk on Sunday April 14, 2013 @06:06AM
(#5546509)
If that were the case it would make the situation even worse. It means the whole "write performance critical parts in C" argument is bogus.
Re:What's Going On (on "Why Python, Ruby, and Javascript are...
by nostrademons on Sunday April 14, 2013 @06:19AM
(#5546530)
To answer your original question - no, but there's less C code than the equivalent C-only program, so you're still better off. Or if your argument is that C is a security nightmare (which you won't find much argument from me on), replace C/CPython with Java/Jython.
I think that's kinda the point; rewriting critical sections in C is pretty much Working As Intended. That's why it's a scripting language. The point is that you didn't have to write the whole thing in C.