News for hackers. Stuff that matters.

A comment on Pyston v2: Faster Python. Parent comment

Re:Pyston v2: Faster Python by omginternets on Wednesday October 28, 2020 @05:47PM (#24924497)
A fragmented ecosystem, incompatibilities, etc.

And more importantly, your original question isn't asking about forks, specifically. It was asking why someone might oppose performance work.

[ Parent | on HN ]
Re:Pyston v2: Faster Python by chrisseaton on Wednesday October 28, 2020 @06:14PM (#24924713)
> incompatibilities, etc

But it's compatible. It's a drop-in replacement.

[ Parent | on HN ]
Re:Pyston v2: Faster Python by omginternets on Wednesday October 28, 2020 @07:11PM (#24925230)
Serious question: do you have experience with “drop in replacements” for reference implementations? They’re rarely 100% compatible. Especially when the reference implementation isn’t formally specified.

Moreover, you continue to cherry pick, neglecting the other arguments you’ve been presented. It sounds like you’ve already made up your mind about this.

[ Parent | on HN ]
Re:Pyston v2: Faster Python by chrisseaton on Wednesday October 28, 2020 @08:46PM (#24925873)
Other arguments are ‘it’s not worth it’ or ‘it’s not likely to succeed’ but nobody is making you do the work!
[ Parent | on HN ]
Re:Pyston v2: Faster Python by omginternets on Wednesday October 28, 2020 @09:05PM (#24925986)
Hmm no, they’re really not. I’ll leave you to reread the tread.
[ Parent | on HN ]