5 ms·
Haven't seen this discussed on HN, and seems like huge news. Why isn't this more known? Is it moving forward? Has it been announced officially...
by coldtea 6y ago
Haven't seen this discussed on HN, and seems like huge news.
Why isn't this more known? Is it moving forward? Has it been announced officially...
- dna_polymerase 6y agoMaybe because the repo is 2 hours old, provides no actual information other than some hand waving. Also the author asks for $2 Million and doesn't seem to be a Python Core Developer. Given the repos age I'm probably answering to Mark Shannon himself. Edit: This post wasn't supposed to be an hostile attack against anybody. Just found it odd to ask why an 2 hour old repo wasn't more known. I did not know that Mark Shannon is a core dev. Certainly did not pick that up from the repos contents.
- ebg13 6y agoI think Mark Shannon is a Python core dev now. But I agree with your other reasons.
- nemetroid 6y agoMark Shannon definitely is a core developer, though I agree that it's odd to ask "why isn't this more known?" about a two hours old repo.
- coldtea 6y agoHe is a core developer (and long time core contributor), and he doesn't ask for "$2 million dollars". In fact the post says: "The PSF seems to be the obvious organization to coordinate funding". And no, I'm not Mark, somebody send me the link. Conspiracy theory much?
- antoinealb 6y agoThe repository linked mentions that each stage should cost about $500k and there are 4 stages. You can argue that he is not asking for it, but at least he is valuating it at $2M.
- coldtea 6y agoDidn't say he isn't valuating it at $2M. It's all on the post. What he doesn't do is say he should be the one to handle those (or even get those).
- XorNot 6y ago200k per year would not be the worst salary to pay a developer for this work, and I'd say he's outlined about 5 to 10 years of work. Feels like you could negotiate a package of escalating compensation contingent on delivery milestones.
- pizza234 6y agoI personally think it's a bit premature to talk [edit: for the developers to talk] about it - they're attributing 2.25x to the addition of a JIT, which generally takes a long time to develop and tweak, adds a significant complexity, and makes the performance profile complex (ie. slow start, slow first requests, etc.). I like though, to see the JIT wave across interpreted languages (see Ruby). I'm also curious to see what's going to be the implementation.
- dna_polymerase 6y agoThe problem with this and all other efforts for speed in CPython is the interop with C extensions. For JITted Python look at PyPy, sure the JIT gives you some performance, but they broke all C extensions along the way.
- heavenlyblue 6y ago> they broke all C extensions along the way. It doesn't have to be this way though?
- ploxiln 6y agoMany C extensions work with PyPy now. I have a service that uses pylibmc and pycurl, and it works with PyPy. Those extensions didn't rewrite with cffi or anything like that, PyPy added a compatibility layer, it's impressive. But, you don't get the JIT performance if you use the C extensions a lot, it's better for PyPy performance if you find a pure-python alternative for extensions used in "hot paths".
- chrisseaton 6y agoThe TruffleRuby approach is to run the C extensions in an interpreter with a JIT. This way you can change the C extension interface without changing the code, and the optimisations apply to both at the same time. https://www.youtube.com/watch?v=YLtjkP9bD_U https://www.youtube.com/watch?v=YLtjkP9bD_U
- MaxBarraclough 6y ago
- yxhuvud 6y agoBecause it is on the idea stage without funding. My guess is that it will stay that way. That said, it is probably feasible to do some parts of it, similar to the 3x3 project Ruby has. I wouldn't be surprised if numpy glue is a lot more tractable for optimization than Rails, but the interaction with C libs would pose some serious issues.