Python performance myths and fairy tales
1–10 of 221 posts
Re: Python performance myths and fairy tales
#2Re: Python performance myths and fairy tales
#3Re: Python performance myths and fairy tales
#4Cool article, I think a lot of those issues are not Python specific so it's a good overview of whatever others can learn from a now 30 years old language! I think we'll probably go down the JS/TS route where another compiler (Pypy or mypyc or something else) will work alongside CPython but I don't see Python4 happening.
Re: Python performance myths and fairy tales
#5Re: Python performance myths and fairy tales
#6Re: Python performance myths and fairy tales
#7Why do people think it's a good trade-off?
Re: Python performance myths and fairy tales
#8Do you still need an add-on library to use more than one core?
Re: Python performance myths and fairy tales
#9So we are paying 99% of the performance just for the 1% of cases where it's nice to code in. Why do people think it's a good trade-off?
Personally I think it is more crazy that you would optimize 99% of the time just to need it for 1% of the time.
Re: Python performance myths and fairy tales
#10So we are paying 99% of the performance just for the 1% of cases where it's nice to code in. Why do people think it's a good trade-off?