- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
JavaScript fits too
Javascript’s still arriving to the meeting
It had to download 300 of it’s buddies first
nodejs hasnt started yet
It’s waiting for the “light weight” node development server to start as well.
After that it’s waiting for the call to open a browser to go through.
Then it’s waiting for Google telemetry to finish phoning home before the page can load.
I know people joke around about this a lot. But I was blown away by a recent switch to I did from using cv2 with python to using cv2 with C++.
I had literally hundreds of thousands of images to analyze for a dataset. My python script would have taken 12 hours.
I ported it to C++ and it literally destroyed it in 20 minutes.
I’m sure I was doing something that really wasn’t optimized well for python. I know somewhere in the backend it probably was using a completely different library with multi thread optimization. Or maybe turbojpg is just garbage in python. I’m still not even sure what the bottleneck was. I don’t know enough to really explain why.
But holy shit. I never had that much of a performance difference in such a simple task.
Was very impressed.
Exactly what this comic is saying. C++ can handle in 20 minutes what takes python 12 hours, but something gets destroyed.
If you had let me write the C++ code, I could have literally destroyed your dataset in a couple of seconds.





