Top
Best
New

Posted by WoodenChair 1/1/2026

Python numbers every programmer should know(mkennedy.codes)
429 points | 186 commentspage 6
_ZeD_ 1/1/2026|
Yeah... No. I've 10+ years of python under my belt and I might have had need for this kind of micro optimizations in like 2 times most
willseth 1/1/2026|
Sorry, you’re not allowed to discourage premature optimization or defend Python here.
ewuhic 1/1/2026||
This is AI slop.
Lockal 1/2/2026|
Sad that your comment is downvoted. But yes, for those who need clarification:

1) Measurements are faulty. List of 1,000 ints can be 4x smaller. Most time measurements depend on circumstances that are not mentioned, therefore can't be reproduced.

2) Brainrot AI style. Hashmap is not "200x faster than list!", that's not how complexity works.

3) orjson/ujson are faulty, which is one of the reasons they don't replace stdlib implementation. Expect crashes, broken jsons, anything from them

4) What actually will be used in number-crunching applications - numpy or similar libraries - is not even mentioned.

hulitu 1/7/2026|
> Add two integers 19.0 ns (52.7M ops/sec)

Your computer is slow. /s