Skip Navigation

Python @programming.dev

tyler @programming.dev

1d ago

O(no) You Didn’t

mrshiny608.github.io

O(no) You Didn’t 😱

Programming @programming.dev

tyler @programming.dev

1d ago

O(no) You Didn’t

mrshiny608.github.io /MrShiny608/optimisation/2025/04/22/OhNoYouDidnt.html

Programming Circlejerk @programming.dev

Drew @sopuli.xyz

2d ago

Python, even on a good day, is an interpreted langauge who takes strolls in the park, watches the ducks, and honours the UK Tea Alarm. 🫖

mrshiny608.github.io /MrShiny608/optimisation/2025/04/22/OhNoYouDidnt.html

Lobste.rs @lemmy.bestiver.se

RSS Bot @lemmy.bestiver.se

2d ago

O(no) You Didn’t

mrshiny608.github.io /MrShiny608/optimisation/2025/04/22/OhNoYouDidnt.html

3 comments

TL;DR, big-O ignores the constant factor. If you already know what that means you don't need to read this...
- Eh, I also enjoyed seeing the comparison between Go and Python, seeing the jumps in time because of allocations, and knowing the size of the list when the more efficient algorithm started to become faster.

It'd be interesting to see if switching to pypy made any difference. It won't beat the eventual exponential growth, but I've seen it be as fast as Rust code I've written for code like this.