3 ms·
That’s a false dilemma. We’ve had almost three decades to optimize CPython. It will take a while to catch up.
by klodolph 8y ago
That’s a false dilemma. We’ve had almost three decades to optimize CPython. It will take a while to catch up.
- johnisgood 8y agoIt's not, and I'm curious as to why, I even suggested a reason very similar to your answer. I guess people assumed malice. Oh well.
- hcs 8y agoThe dilemma klodoph mentions is: > [Performance] isn't [...] one of the selling points of Rust or > this [...] software has been implemented poorly It sounds like you're maligning Rust (isn't keeping promises) or RustPython (is implemented poorly), and it's easy to read "implemented poorly" as an attack on the implementers.
- johnisgood 8y agoWell, it's definitely a possibility. I am not trying to attack them, it might be the case, or it might not. I was just trying to get possible reasons, and that's what came to mind. I'm sure there are other reasons, that's why I asked. I really don't know how slow it is, I've not done benchmarks, but given that Rust is supposed to be efficient, it certainly can't be that slow, unless the implementation is really poor, I guess. I'm not saying it is because I don't know. If anyone has done benchmarks, please do share! The reason for why I got the idea that it is slow, is that I believed the parent[1], and people have repeatedly claimed that CPython is slow. [1] "to eventually get the same or better performance as CPython." I assume this means that it is slower than CPython, and CPython is already extremely slow according to some people even on this page. Sorry for the confusion. :)
- hcs 8y agoThanks for the explanation! One thing to consider is that CPython isn't slow because of the language it's written in, but because of optimizations it isn't doing (namely JIT, I think). Rust can't do the same things any faster than C can, and an early implementation of Python in Rust isn't likely to be much faster than an early implementation in C. Rust has the potential to make certain classes of optimization easier, eventually.
- jashmatthews 8y agoFor an example of the huge developer productivity multiplier Rust is for this kind of thing check out what Yorick Peterse has done in his spare time with Inko: https://gitlab.com/inko-lang/inko https://gitlab.com/inko-lang/inko
- coldtea 8y ago>We’ve had almost three decades to optimize CPython Assuming that was actively pursued. But if it was, all those other projects (Unladden Swallow, Dropbox's Python project, PyPy, etc, whose intend was exactly to make Python faster, wouldn't have been started).
- sifoobar 8y agoSome of those lessons have most definitely been used to improve the reference implementation. It's not remarkably slow as long as you compare apples to apples, that is non-jitted vm-interpreters. Jits pay a steep complexity- (and hence maintenance) price for their performance that should be taken into account when comparing. Designing a significantly faster interpreter with comparable features is non-trivial from my experience [0]. https://gitlab.com/sifoo/snigl https://gitlab.com/sifoo/snigl